The site I will be designing will have a lot of content (few hundred pages) and users need for content will vary. Most probably some of the content will be dynamically generated based on users location on site ( = area of interest). We will probably use bootstrap as the front end framework.
To get the UX right we are planning to user test it both in wireframe and "html" prototypes. I do not look forward to create an ton of static html pages. One option would be to use PHP template structure but there would still be a lot of manual work - navigation for example.
I have been reading a lot of information about using Static Site Generators (SSG) for prototyping. The problem is that there seems to be an ton of options and I do not have time to test that many of them. I'm familiar with HTML, CSS, LESS and some PHP - and I would love not to dive too deeply to coding.
I am mostly interested in having templates for segments of HTML-code, prettier-than-PHP logic for showing them and handling of navigation. And simulating dynamic content using variables - inserting page title to H1 etc.
Stephen Hay advocates Dexy in http://www.amazon.com/Responsive-Design-Workflow-Stephen-Hay which seems nice for documenting features. However documenting is only an nice-to-have feature for us. Also Dexy does not, to my understanding, watch for changes and offer live generation of content but needs to be constantly rebuilt.
Jekyl, Nanoc, Phrozn, PieCrust and Stacey, for example, seem nice choices. Mixture is an option also.
My question is which SSG would make it easy to have multiple navigation levels, like this...
Home | |- Group 1 | | | |-section 1 | |-section 2 | |-section 3 | |- Group 2 | | etc. etc.
...and simulate dynamic content by inserting variables from separate text / markdown etc. files into html / template language templates, if possible from subpages, for example to create this kind of navigation:
–––––––––––––––––––– –––––––––––––––––––– –––––––––––––––––––– | section 1 | | section 2 | | section | | –––––––––––––––––––| | –––––––––––––––––––| | –––––––––––––––––––| ||image from subpage|| ||image from subpage|| ||image from subpage|| || || || || || || || || || || || || || || || || || || || || || || || || || || || || || || | ––––––––––––––––––|| | ––––––––––––––––––|| | ––––––––––––––––––|| | text from subpage | | text from subpage | | text from subpage | | | | | | | | | | | | | –––––––––––––––––––– –––––––––––––––––––– ––––––––––––––––––––
I could of course use some simple cms, php includes and custom fields on cms pages but that would be quite slow to edit.