I stubbled across an interesting post by Yoke Designs on dating a designer. These are things you should expect when dating a design.
Click here: Dating A Designer: 10 Things You Need to Know
Sone of you may smile.
Sunday, March 02, 2014
Thursday, February 13, 2014
Just like most CSS frameworks, all of the frameworks will help you rapidly develop sites by eliminating the need to write basic CSS styles yourself, as you would expect.
Regardless, of whether you use CSS grids for prototyping or production systems, there are multiple aesthetic and design benefits:
- Visual design cohesion between page elements.
- Uniformity and consistency in HTML element placement.
- Easier to apply the “rule of thirds” and the “golden section” to design.
- Mostly eliminates the need to use nested HTML tables.
- Nested sub-grids, for very complex designs that are relatively simple to produce.
- Easier to apply images and text callouts to produce asymmetric layouts for visual texture.
- Cross-browser support, so less screaming and hair pulling when you get around to testing for that bane of designers, IE.
- Reduced effort for producing slicker web page layouts, compared to coding the necessary CSS from scratch.
- Reduced future effort if you need to reposition elements or change rendering characteristics (typography, margins, etc.) for related elements en masse.
- Usable with static pages and CMSes/ blog platforms.
For example, Blueprint CSS
- Relatively small file sizes. Has compressed versions for production use, for further size decreases.
- Print + screen stylesheets.
- Simple to integrate and use.
- Easy to remember CSS classes and ids that are unlikely to clash with any that you’re already using.
- Lots of support tools, especially for generating custom grids.
- Lots of articles/ tutorials about Blueprint, with lots of positive vibe.
- Lots of use of Blueprint by WordPress theme designers.
This, along with other CSS Grid is good for development depending on the designer to keep everything organized and simple while creating websites.
I do have a lot to say about this question from constantly changing my portfolio site to the point during lectures of a different class.
I believe that a successful design is all about usability and the utility not the visual design that can determine the success or failure of a website. The navigation and site architecture needs to be intuitive. The more "question marks' on a website can make it harder for users to comprehend how it works and how to get from point A to point B. A clear structure, moderate visual clue, and easy-to-find link can help users find their way around a website.
I believe you should be able to offer your users some services and tools, but it should be kept at a minimal. The less action require for a user, the more likely the user will actually try it out. A first time user is willing to play around with a website while not filling out long contact forms. In all, let the users explore the website and discover the services without forcing them to fill out any data.
Another point is to keep the users attention. For example, if a service is free then put it there in big a big font. Users recognize and love the word "free" and it grabs the attention. Again, the less question marks on a website, the better. As far as services, let the user see clearly what functions are available. What matters is how understandable the content is so the user can interact with the system. As far as being understandable is concerned, make sure the type is easy to read. Even though, I love the cursive and elegant font I have to keep it at the basic for my users to red legibly.
The design aspect of what makes a website successful is different. White space is becoming popular with website design. White space, for me, is best only behind text or another light color (tans and grays), but don't be afraid of black either. Black is universal. For a general business monochromatic is the best way to go. The general design and aesthetic for the website should be simple for the user. The users should always be able to recognize the header, navigation, content area, and footer. If you can see these, then your user wont either.