If you have a
Google Account (and if you don't, you should consider getting one), you probably know that Google offers its users the opportunity to create sites (called
Google Sites), for free, using its server space and web design tools.
Before I launch into my explanation about how much I learned about myself during the design process, as well as a description of my experience with Google Sites, I should really give some background information on why I designed the site the way I did.
I started out by taking
this quiz on learning styles. The quiz assesses you on four scales: active vs. reflective, sensing vs. intuitive, visual vs. verbal, and sequential vs. global. Try taking the quiz and seeing what kind of results you get.
Here are my results:
My results make sense to me, especially when I consider them in combination with my Myers-Briggs type (
INFP). Perhaps I'll explore the connection between learning styles and Myers-Briggs types another time.
Based on my results, a person familiar with the scoring system (or someone who, at least, read
this overview of the learning styles) would correctly say that I:
-- prefer to work alone, and I also like to take time to think about any topics presented and to process them sufficiently before taking action.
-- enjoy discovering connections between concepts and thinking about possibilities rather than merely learning facts. I deal well with abstractions and appreciate innovation, and I don't like repetition or going through routine steps or calculations.
-- don't have any strong preference for visual presentations (videos, charts, illustrations, etc.) or verbal instruction (written or spoken words). I appreciate both types of communication.
-- work best when I can see the "big picture" with regard to the topic at hand. Then, I'm better able to understand the details and what those finer points do to "complete the picture."
Put it all together, and what does it spell?
I'm a very conceptual thinker who may not always pay attention to or appreciate the finer points of the topics presented. I like to have time to absorb the material at hand before acting on it, and I also enjoy connecting concepts across disciplines and having the opportunity to structure my own "learning path." Being exposed to the "big picture" before delving into a topic can be helpful, as well.
True, true.
So after I processed both the details and the overview of my learning style, I tried to figure out how a website designed specifically for someone like me would look. I'd like to think that I did a pretty good job of not only coming up with a list of factors to consider, but also addressing those factors in the design of my new website,
Before You Tweet…
Here's how I went about it. Appropriately enough, I've included a screenshot illustrating each of these nine design factors.
-- To address my impatience with details, I put some quizzes on my site to compel the viewer to take some extra time to look over the finer points of the material covered on each quiz's reference page.
-- Reminders to attend to certain details, like saving one's changes on their Twitter Settings page, are also offered. I find that I also benefit from receiving similar reminders in real life (more on that later).
-- I put important terms and main ideas in bold, allowing a global learner like me to quickly scan a page and get an overview of the major points covered on that particular page. Bolding these items may also help the viewer to remember them, whether they be main ideas or details.
-- Because I have almost-equal preferences for visual and verbal presentations of information, I tried to include both in my site. Illustrations are offered, along with written descriptions, for the step-by-step instructions, and videos are shown, where appropriate, as they can offer both visual and verbal representations of information. Even if the video does not actually illustrate ideas through pictures, the audio portion of it does satisfy the word-related requirements of verbal learners.
-- Since global learners benefit from having the freedom to construct their own "learning path," I wanted to make sure that all subpages of the site were easily accessible from any page. Thus, I put links to these pages in the left-hand sidebar of every page.
-- Global learners may also find it helpful to look at an overview of what they can expect to learn in a particular section. Therefore, I made sure to include such overviews at the beginning of sections including multiple pages. An overview of the entire site's contents is provided on the site's homepage.
-- To address the needs of reflective learners, I wanted to ensure that viewers did not feel rushed through the tutorial. I encouraged them, at certain points, to take some time to play around/test out the featured aspects of Twitter before moving on. At the same time, I tried to get viewers to see the benefits of looking at other sections, as well. I also recognized that reflective learners prefer to "lurk before they leap" in online settings, since they like to think about things before speaking up or taking action. Because of this, I reminded the audience that they can use Twitter as a strictly information-getting, rather than information-giving, resource.
-- On the "About This Site" page, I encouraged viewers to take notes, which help can help reflective learners to retain information by putting it in their own words. In this way, they can take "ownership" of the material.
-- A right-hand sidebar, containing "Related Resources," is included on certain pages to address intuitive learners' need to imagine possibilities and discover relationships. This sidebar can also be helpful for global learners, who appreciate seeing topics from different perspectives and discovering how they relate to things they are already familiar with.
To accommodate the thinking style of intuitive learners, I planned on having information about the theories behind a topic be linked to that topic's page but appear in a separate window. That way, the supplemental information would be optional reading rather than part of the lesson, itself. However, I decided not to implement this design factor in my site, since I thought that having extra information in both a sidebar and an extra window might result in "information overload" and, possibly, viewer confusion. Furthermore, I felt that such an approach would be more appropriate for a site covering a broader topic, like social networking as a whole.
I also wanted to give users the opportunity to take notes directly on the site and save them in a private account, but Google Sites doesn't support this functionality.
While I was designing and creating the site, I, by necessity, had the results of my learning-style quiz very much in mind. As I mentioned before, my results definitely made sense to me, and I related to the provided descriptions of my four scores. However, these traits were never at the forefront of my thoughts, and I didn't have specific names for the ways in which I think, work, and learn. As I reflect on my experience with discovering my learning style and designing my Google Site, I was reminded of the idea of "you have to name it to claim it," which basically means that once you have a name for some aspect of yourself or your life, you're in a better position to address it.
As I worked on my site, I became more aware of how much my learning style affects how I complete tasks. For example:
-- I took some time to really think about what I wanted to accomplish and how I was going to accomplish it, which is typical of a reflective learner. I also made notes about possible layouts and things to include, which helped me to map everything out before taking action.
-- I really enjoyed the process of looking for content for the "Related Resources" sidebars. As I was adding those links to the site, I thought to myself, "I *would* actually like a site designed like this."
-- I had some frustrating experiences with retaining the changes I made on the "Manage site" page. Why weren't the edits I made being reflected on my site? Thankfully, it didn't take me too long to figure out that it was because I wasn't saving my changes before navigating away from each editing page. I don't know what gave me the idea that I would just have to hit "Save changes" once before clicking "Return to site." (Maybe it's because I'm a conceptual/global rather than detail-oriented thinker?)
-- I was also reminded of how helpful I've always found it to read the "In this section" overviews in my textbooks. I just took it for granted that everyone benefited from such previews, but it's probably more accurate to say that some people find them more helpful than others.
Now that I have a greater awareness of my own personal way of going about things, I can do more to make greater use of my assets and compensate, where necessary. I'll keep you posted on how these revelations affect how I go about doing the rest of my work.
I'm afraid Google Sites provided a few bumps in this road of self-discovery:
-- Finding an appropriate gadget for my site was harder than it should have been. There are *so* many Twitter gadgets, and yet only a small percentage of them had any real practical use or relevance. Does there really need to be a gadget for every celebrity (or "celebrity," as the case may be) with a Twitter account? And every time I pulled the scroll bar down in hopes of revealing a useful gadget, the bar crept upward a little bit, indicating that there were still more gadgets to evaluate. Google could have at least provided a count of how many gadgets matched my search criteria. I know they can: they can count up how many millions of hits things get when someone does a search on Google's main page.
-- I had problems viewing my customized background image when I was logged in as the site's owner. It's not that I couldn't see it: it's that I couldn't see it the way that I visitor would see it. After I had finalized and uploaded my background, I panicked when I couldn't see the cute little birdie that was supposed to appear at the top of the page. It turns out that the header that appears on the Editing pages encroaches on the background image, thus covering up the bird. Much to my relief, when I selected "Preview page as user," the bird reappeared.
-- I had another problem with my background image. When I tried to upload it, the "Custom" option for the background image was grayed out, making me think that I couldn't upload my own image when using the particular theme I had selected. I then went through most of the other themes to see if the "Custom" option was available on them. It wasn't. I then went back to my original theme and hit the "Browse..." button. It turns out that I could upload a background image under my original theme, after all. Why would Google imply that that particular option wasn't available when it really was?
-- While creating quizzes was easier than I thought it would be in many ways, the
directions for how to create one could have been more clearly written. For instance, they should have covered the issue of permissions (i.e., how to allow or restrict access to the quiz), and they could have given the reader a more complete idea of what a "Form" is on a Google Spreadsheet. I was left to figure out those details on my own.
-- I also didn't like how I couldn't change the font of the page header. I could change the color and the header background, but not the lettering appearing in it. Why?
I don't mean to trash Google Sites. It's just that there are some frustrating aspects of using it. But when I navigated through all the features and ways you can edit them, I thought it was pretty incredible that Google allows you to do all that without knowing any code whatsoever, and the WYSIWYG interface is incredibly helpful, as well. I guess they do have to make some site features off-limits, since giving users any more power may compromise the security of Google's servers.
A few things that I particularly liked:
-- Editing the navigation sidebar was very simple. I could indicate that a page was a subpage merely by pressing a few arrows on the "Configure Navigation" screen.
-- Google Sites has a special feature that makes it very easy to display YouTube videos on your site. All you need is the code that appears next to the video.
-- Typing content on the pages was very easy, thanks to the word-processor-like interface.
-- Creating a new page for your site takes less than a minute, although I'm not quite sure why attachments and comments are enabled by default.
So that's my Google Sites story. Be sure to check out
the site and let me know what you think. Or you can even
Twitter about it.