Closed unscriptable closed 11 years ago
Seems like a good idea. If there was a way we didn't have to maintain it individually for every tutorial, that'd be even better :)
I'd rather put this in the readme once than duplicate it everywhere. Once we serialize the markdown to html, we can include something in the footer of each post easily. It's safe to assume that people reading on GitHub understand how GitHub works.
OK, let's plan to add some boilerplate to the generated html.
I'd rather put this in the readme once than duplicate it everywhere. Once we serialize the markdown to html, we can include something in the footer of each post easily.
I think some people will find the footer links to be helpful, so yeah, I'm all for automating it via whatever means we decide to render the tutorials to html.
It's safe to assume that people reading on GitHub understand how GitHub works.
Not sure if that's applicable here (?) since the boilerplate @unscriptable suggested points to other cujo resources, not to say, an issues list or somesuch.
It's safe to assume that people reading on GitHub understand how GitHub works. Not sure if that's applicable here (?) since the boilerplate @unscriptable suggested points to other cujo resources, not to say, an issues list or somesuch.
I think what @scothis said will be more applicable once the web site is up. We should definitely maximize linkage between this repo and cujojs within the README as well as within the tutorials. I've been using cujo.js libs in my code samples and linking to the related repos if I can find a way.
Seems like this is done, too?
I put this at the bottom of each of my tutorials:
Does this work? Any suggestions? Maybe the website generator should add this?