-
Notifications
You must be signed in to change notification settings - Fork 80
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
Roadmap #146
Comments
Might be nice to have a Also |
Oh, thats not a bad idea. It's actually pretty easy. If you guys wanna take a stab at it, go ahead. npm install --save-dev docpress
mkdir -p docs
cat << EOF
# Table of Contents
* [Project name here](../README.md)
EOF > docs/README.md
echo '{ "github": "github/url" }' > docs/docpress.json
# add { scripts: { docs: "docpress build" } } to package.json
# add { scripts: { "docs:watch": "docpress" } } to package.json gh-pages integration is harder though (it has some manual steps), so I'd hold off on that. |
...you can even build that as a |
Theming roadmap (v0.8)
Future themes will replace |
I'd love if we could switch stylus --> postcss and pug --> to something html like (handlebars?). Makes contributing so much simpler, and understanding the code for building themes. |
stylus to postcss-cssnext + postcss-easy-import? yes, that's certainly possible. the lack of pug to something else? that'd be hard. the menu generation relies on pug's recursive mixins, something not easily doable in handlebars. mustache, maybe. |
Maybe swig, not really set on a specific preprocessor, but it should be something that keeps the html in it's normal state. |
We should probably also lock into Node 6.9-lts for v1.0 |
Roadmap
Here's a tentative roadmap.
docpress-disqus
,docpress-google-analytics
).Road to v1
And criteria for a v1 release:
docpress-theme-light
(or whatever) and edit along.The text was updated successfully, but these errors were encountered: