Small projects usually have traditional workflow:
- design -> pages' mocks in PSD
- psd2html -> HTML/CSS/JS static
- CMS -> finished site as it heart uses one of the popular CMS like Drupal, Joomla and so forth
Well, it's all about the second step: PSD->HTML workflow
Inevitably developers split mocks in some entities, blocks wich have independent meaning. Traditionally we do it only inside our minds and write code as it's need to be served for browser. In single files: html, css, js.
Modern even relative small web site is already enough complicated for using css preprocessors, dependencies manager and tools for routine tasks.
Approaches which assume splitting project into independent parts are wide spreaded within building huge web services: SMACCS, OOCSS, BEM.
It's convinient to use light BEM version for developing middle and even small web sites.
There is the next technology stack:
- Stylus with useful mixins
- HTML5 Boilerplate's normalize
- Nunjucks as a template enginge with
block,extendandincudekiller features - Bower for downloading and managing libraries, jquery plugins
- Grunt for routine tasks and assembling project for transfering it for the next step
So, this project about modern PSD->HTML workflow and tools for developing:
- project stubbing
- CLI program which helps working with file structure, maybe it should be
yeomangenerator - simple, powerful and robust developer's HTTP-server
- methodology and structure
- articles, experience
- something else...
If you want to help with something of the list above you should:
- find corresponding repo
- make issue
- create branch with name like
#1-make-some-killer-feature - make pull request, leave a comment with link to that issue
If you want to make new repo, you've got an idea — drop me a line