We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In jade you can do this: http://jade-lang.com/reference/mixins/
The text was updated successfully, but these errors were encountered:
No reason why you couldn't use both.
Sorry, something went wrong.
but what is the difference? expect that in jade is parsed before docoad do it (or what is the order?)
I've creted a template in jade for the menu plugin: https://github.com/sergeche/docpad-plugin-menu It works with the jade mixins without the partial plugin.
So my suggestion is to put a note on the Readme, that you don't need this plugin when you using jade. When it's okay I can create a PR.
I'd say the same statement applies for using any templating engine that supports partials/includes, such as swig.
Hey @timaschew. I'd say it's fine to do a PR with the disclaimer. Good for people to have and know of options. 👍
No branches or pull requests
In jade you can do this: http://jade-lang.com/reference/mixins/
The text was updated successfully, but these errors were encountered: