Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YAML data #3

Closed
paulirish opened this issue Nov 9, 2011 · 8 comments
Closed

YAML data #3

paulirish opened this issue Nov 9, 2011 · 8 comments

Comments

@paulirish
Copy link
Member

the data in the site is getting a little unweidly. it'd be good to maintain in a better format.. YAML perhaps?

from there lets chuck it into the site. using a node build script might be nice.. pipe it through some nice templating library.

alternatively could pull it in clientside and apply it with MDV http://mdv.googlecode.com/svn/trunk/docs/design_intro.html .. but we lose SEO i suppose.. hard to tell

anyway.. we need a better data format and really easy step to bring that into the document. FWIW i think the haml is optional.. it was mostly to avoid the messy markup around this data.

@nimbupani
Copy link
Member

Work towards resolving this: f1c782d

@brianblakely
Copy link
Member

Divya, per our discussion last Wednesday I began work on this issue. I noticed this commit repeats much of the work I was doing, but I have a Node parser for the template as well. I'm going to clone the nodebackbone branch and make a pullreq on that tonight unless you have other plans. Just lmk, cheers.

@nimbupani
Copy link
Member

Brian, definitely. Please do.

@brianblakely
Copy link
Member

Oh, welly well, it looks like app.js already does exactly that. I guess everything is wrapped up in a nice neat little package!

@nimbupani
Copy link
Member

O cool stuff then! Brian, if you see anything missing, please do add it in. I think the JSON file needs more refactoring with the kind of data we need to consider. If you can think of ways to do so, please do!

@paulirish
Copy link
Member Author

so we can move form JSON to YAML when we get around to it.. http://search.npmjs.org/#/yaml

I think yaml will be better in the longrun as JSON is kinda nast for this sorta data

@nimbupani
Copy link
Member

We are already using something similar to yaml now, hence closing this issue.

@addyosmani
Copy link
Contributor

Looks like Divya meant to close this issue. Closing it now to clean up :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants