Closed jacobrask closed 12 years ago
Hey Jacob, found it pretty funny you posted here. I was just about to implement your concept of Markdown syntax with support for Textile to. Will be doing it right now, yours is far superior. I thought of using Markdown at first but thought it might not work well but StyleDocco does it beautifully.
So I'd love to settle on Markdown as the content type.
I was going to spice Kalei up this weekend and add all the features that StyleDocco has and also adding in;
I was going to turn styles.css
into the index page which is also a contents page.
and auto generating a quick jump left hand menu generated from markdown headings.
Trying to think about other things we can collaborate on also
@jacobrask Ended up implementing StyleDoccos approach for the css and UI for now. Will update the index page to include credit for inspiration tonight.
Cool! Looking forward to try it out
Hi!
I'm working on StyleDocco, a tool that's similar to Kalei, but runs on Node.js. I really like your approach of running in the browser!
There are some other CSS documentation tools out there, and I think it would be very cool if we could work toward making our syntaxes somewhat compatible with each other, to let users easily try out the different tools without doing too many changes to their existing CSS documentation.
Here is a comparison between different syntaxes:
Kalei
StyleDocco
Knyle Style Sheets
I think headings are added in Ruby in KSS, and that the markup is assumed from the CSS, but I'm not sure.
Do you know of any other documentation tools?
I am obviously biased toward the syntax I'm using in StyleDocco, but I'm willing to compromise if you find the idea interesting.