Fat Frontend

gistfile1.txt

So, I'm gonna make a book. It's gonna start off as a document in sphinx-doc, so I just
 publish as a flat file HTML, and then maybe figure out funding it if there's enough 
interest in the output. The subject of the book would be an open source project that can
 be completely viewed on it's own, and the idea is that the book would go through the
 technologies involved, the decision process, and how it's all structured together to
 build a self sufficient Frontend client.


Key ideas are a structure of modular components, that means when you end up with shit
 going out of date, you don't have to change everything to adapt. Give new technology
 choices less overhead because frontend moves to fast to be over rigid. How to test 
the modular components to minimise dependencies, and have a quality CI build.

There's a lot to cover but it'd be exciting to really open up the process.

Throw ideas in here I guess. Gotta gets back to work :)

Would you consider development on a public GitHub repo as a way to gain interest and version your work. Especially if you're looking to do revisions down the track to keep the content relevant an applicable to current "best practices". Would also offer input from third parties to ensure the content never becomes stale. Also, who is the guy with a thermal filter applied?

Also, just a thought: in addition to CI would you cover CD?

Sphinx is actually a really light way to start writing, It just doesn't have limitations that I know I'm going to hit with other stuff, and it's well built for handling code in line of hand written articles.

And yeah, public git repo was where I was heading with this thing. Code in the repo and all that jazz.

CD is a consideration too, because the offline client needs to be 'updated' effectively.

Who is that sideways guy? Looks like a peak hipster. :)