How nathansmith/960-grid-system works
Project type and purpose
• This is not a “running” web application but a front-end design toolkit—specifically a CSS grid framework (the “960 Grid System”) with accompanying assets (sketch sheets, design-tool templates, editor plugins, demos).
• Its purpose is to provide a 12/16/24-column grid, a reset and text stylesheet, plus ready-to-use templates and plugins to streamline web-page layout prototyping.
File structure
• Top-level folders:
• code/
– css/ (core grid and helper .css files)
– css/min/ (minified versions)
– demo*.html (sample pages showing the grid in action)
– img/ (any demo images)
• app_plugins/ (design‐tool extensions for Fireworks, Photoshop)
• templates/ (grid templates for dozens of design packages: Acorn, GIMP, Illustrator, etc.)
• sketch_sheets/ (PDFs for printed sketching)
• logo_files/, licenses/ (assets and legal docs)
• There is no server backend, no database, no build script: it’s purely static assets organized by function.
README for additional insights
• Confirms the toolkit nature of the project.
• Explains installation of design-tool plugins.
• Shows how to include CSS in an HTML file and how to switch to RTL styles.
• Mentions MIT/GPL dual licensing.
a. Main components
1. Core CSS Library
• reset.css, text.css, 960.css (12/16/24-col), plus RTL variants
• Minified folder mirrors these files
2. Demo Harness
• HTML demo pages that load the CSS to illustrate usage
3. Design-Tool Integration
• /app_plugins for Fireworks & Photoshop extensions
4. Template Repository
• /templates containing per-tool grid files (Acorn, Illustrator, InDesign, QuarkXPress, GIMP, OmniGraffle…)
5. Sketch Sheets
• Printable PDF layouts
6. Supporting Assets
• /logo_files, /licenses
b. Relationships and interactions
• Demo HTML “consumes” the CSS files and images.
• Designers “consume” templates and plugin packages in their respective tools.
• CSS files form the heart—everything else orbits around illustrating or packaging the grid.
c. Architectural patterns/design principles
• Separation of concerns:
• Core CSS vs. minified build vs. demo
• Grid core vs. reset vs. typography
• Designer integration vs. developer integration
• Extensibility: plug-in model for design tools, file per tool type in templates.
• Simplicity: no runtime code, purely static distribution.
d. Key technologies
• CSS (grid system, reset, text)
• HTML (demos)
• MXP installer (Fireworks plugin)
• Various design formats (.psd, .ai, .xcf, .idml, .qxp, etc.)
Detail level
• Grouping (folders) and file relationships.
• Optional flows (e.g., RTL path only if dir="rtl" is set).