Below is the overview we\u2019re going to try to stick with tonight:<\/p>\n
Although learning to develop algorithms to display data is beyond the scope of this class, Meirelles provides us with good concepts about design that are (close to) universal. Remember, no theorist can give you THE appropriate design element or strategy for ALL designs. Designers must consider audience and purpose* in order to choose the most effective element or strategy.
\n*Other factors such as ability, time frame, resources, etc. will also guide you choices.<\/p>\n
Below are some key vocabulary terms to consider:<\/p>\n
Visual Perception and Cognition–(Why is this an ineffective heading?)<\/p>\n
Time permitting (you’ll hear that line all semester), we’re going to get into group discussions on analyzing assumptions. Remember, one of the main goals of this semester is for you to be able to articulate WHY you make certain design choices. Although it happens sometimes, rarely do you do something “just because.”<\/p>\n
I want us to consider more familiar assumptions first, but the goal is to get you to think about your preconceived biases in order to do this level of critical thinking about your assignments specifically and information design in general. Let’s hop on over to the Prejudice and Rhetoric page if we need any reminders<\/a><\/strong>.<\/p>\n Let’s take a look at (very) brief InDesign tutorial<\/a><\/strong> from last week.<\/p>\n Remember, I expect you to work the entire time. If you’re “finished,” let me know…I’ll fix that. (BTW–how are those webpages coming along). Please have others look at your designs. I don’t have a formal workshop system, but, if our workshops aren’t productive, I’ll institute a formal structure. Your participation grade can go negative, so use your time wisely.<\/p>\n At a minimum, I want you to have a perfect, final product to turn in at the end of the evening…that was a joke.<\/p>\n Remember, your assignments must have memos. The format below will suffice:<\/p>\n Please do not copy and paste this. Take the time to type it out.<\/strong><\/p>\n Audience & Purpose<\/strong><\/p>\n My audience is… Distribution<\/strong><\/p>\n Ideally, I would most likely display my documents…<\/p>\n Dominant Element in the Documents<\/strong><\/p>\n What is the dominant element of your documents? This isn’t just the biggest design element. Consider what draws readers’ attention in your document. Maybe it’s an image, logo, text, color, etc. that is a focal point (see Williams, “Create a Focal Point,” p. 124). Whatever it is, describe it and explain why you think it is appropriate for your document.<\/p>\n Rhetorical Analysis<\/strong><\/p>\n Why do your design choices convey the message you intend? First, state your intended message. Then, explain how you convey a particular ethos<\/em> (professionalism, artistic, academic, etc.) with your design choices. You will have logos<\/em>, but you most likely won’t have any pathos<\/em> appeals. Focus on ethos<\/em> for your first documents (business card and letterhead). You’ll discuss logos<\/em> and pathos<\/em> (in addition to ethos) for Documents #1 & #2.<\/p>\n If you don’t use the word “ethos,” you’re doing something VERY wrong on this assignment. We will discuss ethos in class.<\/p>\n Estimated Cost<\/strong><\/p>\n I expect 200 business cards will cost $$$.$$ and 1000 sheets of letterhead to cost $$$.$$.<\/p>\n Style<\/strong><\/p>\n Make sure you identify the following for each document:<\/p>\n Software Used<\/strong><\/p>\n My creation came to life through the following computer tools…. [Make sure you tell me what area or section or component was created by which computer tool, assuming you used more than one]<\/p>\n References\/Citations\/Sources<\/strong><\/p>\n You must reference where you found images or other information used in your design(s) that you did not personally create from “scratch.”<\/p>\n Remember, you must also reflect on changes you’ll make after I look at your work (in the portfolio), so the entire list on the Assignments Page<\/strong> will not apply to your memos for this draft. The above sections should be included in your memos for this draft. Any questions?<\/p>\n Time permitting…<\/p>\n As your Assignments Page states, you’ll have some software requirements. Today I’m going to try my best to show you how to make a floating, glossy, or fireball-ish effect using Photoshop. I’ve got a page here that will help, but this tutorial comes from a YouTube video–Web 2.0 Logo Design Tutorial<\/a><\/strong>–and it’s specific to CS3 (Mac version).<\/p>\n So follow along with me, go at your own pace, but please don’t distract others. Hold your questions for our pauses during the tutorial.<\/p>\nWorkshop: Business Cards and Letterheads<\/h2>\n
\n
\nMy purpose is…<\/p>\n\n
\nPhotoshop Fancy Logo Tutorial<\/h2>\n
![Lorem Ipsum<\/a><\/strong> or Greeked text<\/a><\/strong><\/li>\nLet me know if your Web page is up<\/li>\n<\/ul>\nDesign for Information<\/em> Ch. 1 “Hierarchical Structures: Trees”<\/h2>\nAlthough learning to develop algorithms to display data is beyond the scope of this class, Meirelles provides us with good concepts about design that are (close to) universal. Remember, no theorist can give you THE appropriate design element or strategy for ALL designs. Designers must consider audience and purpose* in order to choose the most effective element or strategy.\n*Other factors such as ability, time frame, resources, etc. will also guide you choices.<\/p>\nBelow are some key vocabulary terms to consider:<\/p>\n\np. 17: For some reason, humans see the world in hierarchies. What are some examples?<\/li>\np. 19: Visual Hierarchy or Contrast: the “emphasis and attention” we give to our design elements to guide users.\n\nNotice the rows and columns when discussing proximity…<\/li>\n<\/ul>\n<\/li>\np. 20: Organization charts<\/strong> have graphical proximity correspond to conceptual proximity. “Graphical space…[maps] the source domain of power and not physical space.”\n\nHowever, where are the offices located for the individuals in the CLAS Hierarchy<\/a><\/strong>?<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nVisual Perception and Cognition–(Why is this an ineffective heading?)<\/p>\n\nWare’s 3-Stage Model of Perception\n\nPreattentive, at-a-glance unconscious attention<\/li>\nPattern recognition<\/li>\nAccessing long-term memory to “process” the information in our visual working memory.<\/li>\n<\/ol>\n<\/li>\np. 22: “Effective visualizations make intentional use of the preattentive features in the representation of graphical marks.”<\/li>\nGestalt (guh-shtahlt<\/strong><\/em>)–Grouping\n\nFigure-ground discrimination (or contrast)\n\np. 22: Meirelles calls this “Segregation between Figure and Ground”\n\nsee p. 34 for an example<\/li>\ncamouflage<\/li>\nWhat color scheme has the highest figure-ground contrast?<\/li>\n<\/ul>\n<\/li>\nModern(ist) Art disrupts our attempts to perceive “good figure” by violating expectations\n\nGino Severini’s Dynamism of a Dancer<\/em><\/a><\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\nLaws of Grouping\n\nProximity and Similarity<\/li>\nContinuation<\/li>\nEnclosure<\/li>\n<\/ul>\n<\/li>\nUsers come to design from many backgrounds, perspectives, so a one-size-fits-all T\/theory isn’t the whole story<\/li>\nAnd Gestalt<\/em> isn’t just for objects…<\/a><\/strong><\/li>\n<\/ul>\n<\/li>\nCase Study–SmartMoney Map of the Market<\/a>\n\nThe at-a-glance goal for any stock market prices\/values is to quickly ascertain gains and losses.<\/li>\np. 32: Humans project the container metaphor “onto other physical objects, events, and actions.”<\/li>\nWhat’s inside your brain…Open up to me…Don’t shut me out…<\/li>\np. 33: Closure or good continuation–our minds fill in the gaps or what’s “behind” an object<\/li>\np. 35: scale of signs<\/a><\/strong> and other visual displays<\/a><\/strong><\/li>\np. 36: color schemes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nAnalyzing Assumptions\/Prejudices<\/h2>\nTime permitting (you’ll hear that line all semester), we’re going to get into group discussions on analyzing assumptions. Remember, one of the main goals of this semester is for you to be able to articulate WHY you make certain design choices. Although it happens sometimes, rarely do you do something “just because.”<\/p>\nI want us to consider more familiar assumptions first, but the goal is to get you to think about your preconceived biases in order to do this level of critical thinking about your assignments specifically and information design in general. Let’s hop on over to the Prejudice and Rhetoric page if we need any reminders<\/a><\/strong>.<\/p>\nWorkshop: Business Cards and Letterheads<\/h2>\nLet’s take a look at (very) brief InDesign tutorial<\/a><\/strong> from last week.<\/p>\nRemember, I expect you to work the entire time. If you’re “finished,” let me know…I’ll fix that. (BTW–how are those webpages coming along). Please have others look at your designs. I don’t have a formal workshop system, but, if our workshops aren’t productive, I’ll institute a formal structure. Your participation grade can go negative, so use your time wisely.<\/p>\nAt a minimum, I want you to have a perfect, final product to turn in at the end of the evening…that was a joke.<\/p>\nRemember, your assignments must have memos. The format below will suffice:<\/p>\nPlease do not copy and paste this. Take the time to type it out.<\/strong><\/p>\n\nAudience & Purpose<\/strong><\/p>\nMy audience is…\nMy purpose is…<\/p>\nDistribution<\/strong><\/p>\nIdeally, I would most likely display my documents…<\/p>\nDominant Element in the Documents<\/strong><\/p>\nWhat is the dominant element of your documents? This isn’t just the biggest design element. Consider what draws readers’ attention in your document. Maybe it’s an image, logo, text, color, etc. that is a focal point (see Williams, “Create a Focal Point,” p. 124). Whatever it is, describe it and explain why you think it is appropriate for your document.<\/p>\nRhetorical Analysis<\/strong><\/p>\nWhy do your design choices convey the message you intend? First, state your intended message. Then, explain how you convey a particular ethos<\/em> (professionalism, artistic, academic, etc.) with your design choices. You will have logos<\/em>, but you most likely won’t have any pathos<\/em> appeals. Focus on ethos<\/em> for your first documents (business card and letterhead). You’ll discuss logos<\/em> and pathos<\/em> (in addition to ethos) for Documents #1 & #2.<\/p>\nIf you don’t use the word “ethos,” you’re doing something VERY wrong on this assignment. We will discuss ethos in class.<\/p>\nEstimated Cost<\/strong><\/p>\nI expect 200 business cards will cost $$$.$$ and 1000 sheets of letterhead to cost $$$.$$.<\/p>\nStyle<\/strong><\/p>\nMake sure you identify the following for each document:<\/p>\n\nTypeface<\/li>\nFont size(s)<\/li>\nFont color(s) (C=__, M=__, Y=__, K=__) or HEXADECIMAL<\/li>\nStock–paper or substance cards will be printed on<\/li>\n<\/ul>\nSoftware Used<\/strong><\/p>\nMy creation came to life through the following computer tools…. [Make sure you tell me what area or section or component was created by which computer tool, assuming you used more than one]<\/p>\nReferences\/Citations\/Sources<\/strong><\/p>\nYou must reference where you found images or other information used in your design(s) that you did not personally create from “scratch.”<\/p>\n\nRemember, you must also reflect on changes you’ll make after I look at your work (in the portfolio), so the entire list on the Assignments Page<\/strong> will not apply to your memos for this draft. The above sections should be included in your memos for this draft. Any questions?<\/p>\nPhotoshop Fancy Logo Tutorial<\/h2>\nTime permitting…<\/p>\nAs your Assignments Page states, you’ll have some software requirements. Today I’m going to try my best to show you how to make a floating, glossy, or fireball-ish effect using Photoshop. I’ve got a page here that will help, but this tutorial comes from a YouTube video–Web 2.0 Logo Design Tutorial<\/a><\/strong>–and it’s specific to CS3 (Mac version).<\/p>\nSo follow along with me, go at your own pace, but please don’t distract others. Hold your questions for our pauses during the tutorial.<\/p>\nThis tutorial has two aims<\/a><\/strong>: 1) to get you to do something difficult with Photoshop and 2) to get you to observe a “live tutorial.” You may critique me all you want, but consider the conditions we’re under and how that may affect this tutorial. I want you to notice how or why we get off the same page\u00a0as we go\u00a0through this tutorial. It’s ok if that happens! I’m trying to get us to slow down and think about the fact that an audience following a step-by-step process can have different results. Why?<\/p>\nWant a more advanced tutorial? If so, try to follow along with the example from Aquul on Photoshop CS6: “Clean Professional Logo” tutorial<\/a><\/strong> (an ad pops up first). Remember, I expect you’ll devote time outside of class to learning this software because…why? Exactly, this is not a software instruction class.<\/p>\nNext Week’s Readings<\/h2>\nMake sure you read Chapter 2 in\u00a0Design for Information<\/em> and Chapter 4 in The Non-Designer’s Design Book<\/em> before coming to class next week (9\/18). Also, keep bringing your books!!! You will fail the class if you don’t. Stay on top of your reading so you don’t fall behind. That midterm<\/strong> (10\/02) will be here before you know it!<\/p>\nOf course, don’t forget your Business Cards and Letterhead (and memos)–they’re due next week.<\/p>\n","protected":false},"excerpt":{"rendered":"Overall Plan for the Evening Below is the overview we\u2019re going to try to stick with tonight: Overview for Notes, Workshop, Tutorials Back up to August 28th\u00a0(if needed) Rhetorical Principles of Design International Laundry Symbols Business Cards are no laughing matter… Design for Information Ch. 1 discussion Theory Discussion Analyzing Assumptions (if needed) Some Photoshop […]<\/p>\n","protected":false},"author":598,"featured_media":0,"parent":3590,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-3609","page","type-page","status-publish","hentry"],"jetpack_shortlink":"https:\/\/wp.me\/P2HAOx-Wd","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3609","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/users\/598"}],"replies":[{"embeddable":true,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/comments?post=3609"}],"version-history":[{"count":9,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3609\/revisions"}],"predecessor-version":[{"id":3716,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3609\/revisions\/3716"}],"up":[{"embeddable":true,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3590"}],"wp:attachment":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/media?parent=3609"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"http:\/\/en.wikipedia.org\/wiki\/File:Lorem_ipsum_design.svg\"){kind=link}
![other visual displays<\/a><\/strong><\/li>\np. 36: color schemes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nAnalyzing Assumptions\/Prejudices<\/h2>\nTime permitting (you’ll hear that line all semester), we’re going to get into group discussions on analyzing assumptions. Remember, one of the main goals of this semester is for you to be able to articulate WHY you make certain design choices. Although it happens sometimes, rarely do you do something “just because.”<\/p>\nI want us to consider more familiar assumptions first, but the goal is to get you to think about your preconceived biases in order to do this level of critical thinking about your assignments specifically and information design in general. Let’s hop on over to the Prejudice and Rhetoric page if we need any reminders<\/a><\/strong>.<\/p>\nWorkshop: Business Cards and Letterheads<\/h2>\nLet’s take a look at (very) brief InDesign tutorial<\/a><\/strong> from last week.<\/p>\nRemember, I expect you to work the entire time. If you’re “finished,” let me know…I’ll fix that. (BTW–how are those webpages coming along). Please have others look at your designs. I don’t have a formal workshop system, but, if our workshops aren’t productive, I’ll institute a formal structure. Your participation grade can go negative, so use your time wisely.<\/p>\nAt a minimum, I want you to have a perfect, final product to turn in at the end of the evening…that was a joke.<\/p>\nRemember, your assignments must have memos. The format below will suffice:<\/p>\nPlease do not copy and paste this. Take the time to type it out.<\/strong><\/p>\n\nAudience & Purpose<\/strong><\/p>\nMy audience is…\nMy purpose is…<\/p>\nDistribution<\/strong><\/p>\nIdeally, I would most likely display my documents…<\/p>\nDominant Element in the Documents<\/strong><\/p>\nWhat is the dominant element of your documents? This isn’t just the biggest design element. Consider what draws readers’ attention in your document. Maybe it’s an image, logo, text, color, etc. that is a focal point (see Williams, “Create a Focal Point,” p. 124). Whatever it is, describe it and explain why you think it is appropriate for your document.<\/p>\nRhetorical Analysis<\/strong><\/p>\nWhy do your design choices convey the message you intend? First, state your intended message. Then, explain how you convey a particular ethos<\/em> (professionalism, artistic, academic, etc.) with your design choices. You will have logos<\/em>, but you most likely won’t have any pathos<\/em> appeals. Focus on ethos<\/em> for your first documents (business card and letterhead). You’ll discuss logos<\/em> and pathos<\/em> (in addition to ethos) for Documents #1 & #2.<\/p>\nIf you don’t use the word “ethos,” you’re doing something VERY wrong on this assignment. We will discuss ethos in class.<\/p>\nEstimated Cost<\/strong><\/p>\nI expect 200 business cards will cost $$$.$$ and 1000 sheets of letterhead to cost $$$.$$.<\/p>\nStyle<\/strong><\/p>\nMake sure you identify the following for each document:<\/p>\n\nTypeface<\/li>\nFont size(s)<\/li>\nFont color(s) (C=__, M=__, Y=__, K=__) or HEXADECIMAL<\/li>\nStock–paper or substance cards will be printed on<\/li>\n<\/ul>\nSoftware Used<\/strong><\/p>\nMy creation came to life through the following computer tools…. [Make sure you tell me what area or section or component was created by which computer tool, assuming you used more than one]<\/p>\nReferences\/Citations\/Sources<\/strong><\/p>\nYou must reference where you found images or other information used in your design(s) that you did not personally create from “scratch.”<\/p>\n\nRemember, you must also reflect on changes you’ll make after I look at your work (in the portfolio), so the entire list on the Assignments Page<\/strong> will not apply to your memos for this draft. The above sections should be included in your memos for this draft. Any questions?<\/p>\nPhotoshop Fancy Logo Tutorial<\/h2>\nTime permitting…<\/p>\nAs your Assignments Page states, you’ll have some software requirements. Today I’m going to try my best to show you how to make a floating, glossy, or fireball-ish effect using Photoshop. I’ve got a page here that will help, but this tutorial comes from a YouTube video–Web 2.0 Logo Design Tutorial<\/a><\/strong>–and it’s specific to CS3 (Mac version).<\/p>\nSo follow along with me, go at your own pace, but please don’t distract others. Hold your questions for our pauses during the tutorial.<\/p>\nThis tutorial has two aims<\/a><\/strong>: 1) to get you to do something difficult with Photoshop and 2) to get you to observe a “live tutorial.” You may critique me all you want, but consider the conditions we’re under and how that may affect this tutorial. I want you to notice how or why we get off the same page\u00a0as we go\u00a0through this tutorial. It’s ok if that happens! I’m trying to get us to slow down and think about the fact that an audience following a step-by-step process can have different results. Why?<\/p>\nWant a more advanced tutorial? If so, try to follow along with the example from Aquul on Photoshop CS6: “Clean Professional Logo” tutorial<\/a><\/strong> (an ad pops up first). Remember, I expect you’ll devote time outside of class to learning this software because…why? Exactly, this is not a software instruction class.<\/p>\nNext Week’s Readings<\/h2>\nMake sure you read Chapter 2 in\u00a0Design for Information<\/em> and Chapter 4 in The Non-Designer’s Design Book<\/em> before coming to class next week (9\/18). Also, keep bringing your books!!! You will fail the class if you don’t. Stay on top of your reading so you don’t fall behind. That midterm<\/strong> (10\/02) will be here before you know it!<\/p>\nOf course, don’t forget your Business Cards and Letterhead (and memos)–they’re due next week.<\/p>\n","protected":false},"excerpt":{"rendered":"Overall Plan for the Evening Below is the overview we\u2019re going to try to stick with tonight: Overview for Notes, Workshop, Tutorials Back up to August 28th\u00a0(if needed) Rhetorical Principles of Design International Laundry Symbols Business Cards are no laughing matter… Design for Information Ch. 1 discussion Theory Discussion Analyzing Assumptions (if needed) Some Photoshop […]<\/p>\n","protected":false},"author":598,"featured_media":0,"parent":3590,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-3609","page","type-page","status-publish","hentry"],"jetpack_shortlink":"https:\/\/wp.me\/P2HAOx-Wd","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3609","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/users\/598"}],"replies":[{"embeddable":true,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/comments?post=3609"}],"version-history":[{"count":9,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3609\/revisions"}],"predecessor-version":[{"id":3716,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3609\/revisions\/3716"}],"up":[{"embeddable":true,"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3590"}],"wp:attachment":[{"href":"https:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/media?parent=3609"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"http:\/\/assets.theatlantic.com\/static\/coma\/images\/issues\/200609\/Height.jpg\"){kind=link}