Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have posted my directory structure and comments in another thread, but it is applicable here too!</p> <p>I have been using the following setup for a while now with great results:</p> <ul> <li><p>/site: This is where my actual working website will live. I'll install my CMS or platform in this directory after the templates are created.</p> <ul> <li>.htaccess <em>(basic tweaks I usually find myself enabling anyway)</em></li> <li>robots.txt <em>(so I don't forget to disallow items like /admin later)</em></li> </ul></li> <li><p>/source: Contains any comps, notes, documents, specifications, etc.</p></li> <li><p>/templates: Start here! Create all static templates that will eventually need to be ported into the CMS or framework of /site.</p> <ul> <li>/_behavior <ul> <li>global.js <em>(site-specific code; may be broken out into multiple files as needed)</em></li> </ul></li> <li><p>/_media: Images, downloadable files, etc. Organized as necessary</p></li> <li><p>/_style: I prefer modular CSS development so I normally end up with many stylesheet for each unique section of the website. This is cleaned up greatly with <a href="http://github.com/cgriego/front-end-blender/tree/master" rel="nofollow noreferrer">Blender</a> - I highly recommend this tool!</p> <ul> <li>print.css <em>(this eventually gets blended, so use @media print)</em></li> <li>reset.css <em>(<a href="http://meyerweb.com/eric/tools/css/reset/" rel="nofollow noreferrer">Eric Meyer's</a>)</em></li> <li>screen.css <em>(for @media screen, handheld)</em></li> <li><em>additional modules as necessary</em></li> </ul></li> <li><p>/_vendor: all 3rd party code (jQuery, shadowbox, etc.)</p></li> <li><p>Blendfile.yaml <em>(for Blender; see above)</em></p></li> <li>template.html <em>(basic starting template; can be copied and renamed for each unique template)</em></li> </ul></li> <li><p>/tests: <a href="http://seleniumhq.org/" rel="nofollow noreferrer">Selenium</a> unit tests</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload