document ideas behind the springboard reboot

[garrett]

random thoughts from IM:

ideally, there's no logic in the actual pages themselves
you just include things if you want it
(or don't, if you don't care about it)
and I was thinking of having a convention of either having includes be community_foo.html or community/foo.html where community (or whatever) is the site name
so ovirt_foo.html or ovirt/foo.html under `_includes/` for site-specific ones, for example
not a hard rule, but one to make it clear when there's something SPECIFIC to the site
and doing similar stuff for CSS/JS
also, look into the possibility of having optional CSS, like fonts.scss, so we don't need to include it in the starter repo, but it checks for the presence of it and uses it
like how I have /img/logo.svg — it's optional to have a logo
and you can change the name (like to PNG even) in the _config.yml
logo: "/img/foobar.png"
if you don't have a logo (and the forkable site won't), then it will fall back to not having the HTML for it, but having just a plain link in the H1
planning on having some page header stuff, like if you want to include special CSS/JS for just that page
like style: and script: in the frontmatter
so it can put those in the HEAD
and special class/classes too
all optional
but would be useful
and all this should be documented
I guess I should write this up and then add it
also, I should write up some rules I try to abide by
like no gem deps
and include only what's necessary
and try to keep content purely separated from logic and such
and explain the dirs a bit (although Jekyll explains them already)
anyway, I have ideas about it in my head... I just hope I don't forget them before implementing them (:
simplify is the #1 constraint and goal behind this, and everything falls into line from that
and to be able to understand everything that's going on
not hide behind layers of dependencies and libraries doing magic things (bootstrap is included in this)
it's POSSIBLE, but not a good idea
(to do things in a wacky way)

Anyway, this needs to be written up properly.

[garrett]

...and included in README.md