When I start a new front-end project coding HTML/CSS I will ask the designer to provide a style guide to outline the typography used through the website. I find when I mark-up the CSS for the typography first, before starting the grid, the overall CSS is cleaner. How do you communicate what elements need to be in the style guide? Well there are some basic elements such as headers, forms and table that I provide in a HTML file that the designer can start with. Then additional typography elements, such as typography in sidebars and call-to-actions are added to the style guide. Are there any elements you think need to be included in my basic HTML file? I like to keep it relatively simple so I don't add things like definition lists, but perhaps I should. Let me know.
Blog
About this Blog
This blog is no longer being maintained. The blog once was a part of my Ruby on Rails freelancing practice. If you would like to find out what I'm currently working on, please visit CivilCode Inc - Custom Software Development; we specialize in building tailored business application in Elixir and Phoenix.
Blog Archive
-
▼
2010
(70)
-
▼
September
(27)
- SearchLogic ordering not working: Uses association...
- Status not showing in Redmine in Issues
- BlankStatic updated for latest Compass, Haml, Sass...
- Use Terminitor to get your Rails Development work ...
- Translating Booleans in I18n files
- Update to Firsthand Rails Template
- Rails Application Launch Checklist
- Install Compass in an existing Rails application w...
- The Other RSpec Methods: #subject, #specify, and #let
- Custom default attribute in ActiveRecord
- Basic HTML Template for Designers to create a Styl...
- Rails Validations can be any ActiveRecord Model In...
- How to get the options for a named_scope
- Configure RMagick gem in a Rails 2.3.x application
- Autospec problem, autospec exiting without results
- BlankStatic Version 1 released with "Bundled" Gems...
- How to display Facebook Profile information when u...
- RSpec #stub vs. #stub!
- Class Methods Called Against Associations in Activ...
- Ruby Hook Methods
- Radiant Training Resources and Email Template
- Shopify (eCommerce) Pre-Launch Checklist
- Usability Issue on American Airlines Reward Travel
- Ruby RDoc Example
- Radiant Releases Now Listed on the Wiki Page
- Leave a project how you would like to find it
- Radiant 0.9.1 and Globalize2 Extension
-
▼
September
(27)
Labels
- active-record (6)
- agile (5)
- application development (4)
- application-architecture (1)
- ask for help (1)
- associations (3)
- blank-static (2)
- bourne (2)
- bundler (1)
- business (1)
- capistrano (1)
- capybara (1)
- centos (2)
- checklists (11)
- compass (2)
- content management systems (3)
- craftmanship (1)
- css (7)
- cucumber (4)
- cufon (1)
- customer-centered web design (4)
- developer-challenge (4)
- domain-modelling (1)
- domain-patterns (1)
- ebooks (1)
- elixir (1)
- ember.js (1)
- error-handling (1)
- errors (1)
- facebook (1)
- fundamentals (3)
- gems (2)
- git (4)
- google-site-search (1)
- haml (1)
- heroku (9)
- html (3)
- html-5 (1)
- i18n (1)
- internet-explorer (2)
- interview (1)
- javascript (1)
- jquery (4)
- launch (10)
- life hacks (2)
- maintenance (1)
- memcached (1)
- memory-consumption (1)
- meta-programming (3)
- mocha (2)
- mocks (1)
- monitoring (1)
- mysql (1)
- named scopes (3)
- object-design (2)
- optimization (1)
- osx (2)
- personas (4)
- presentations (4)
- productivity (1)
- radiant (4)
- rails (35)
- rails-3.0 (5)
- rails-3.2 (1)
- railsconf (2)
- rake (1)
- rdoc (1)
- redmine (3)
- refinery (1)
- rest (1)
- rmagick (1)
- rspec (12)
- ruby (18)
- rvm (1)
- s3 (1)
- safari (1)
- sass (2)
- saving (2)
- searchlogic (1)
- sftp (1)
- shopify (1)
- spork (1)
- spree (2)
- sql (1)
- stand-up (7)
- static-matic (2)
- strategy (1)
- templates (1)
- testing (4)
- textmate (1)
- tools (1)
- unix (2)
- uploads (1)
- usability (1)
- user-stories (1)
- validations (1)
- vim (3)
- web design (1)
- workflow (2)
Firsthand Blog Archive
2002-2019 Nicholas Henry
All Rights Reserved