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

Is this plugin obsolete when using jade, which has its own partial (mixin) implementation? #16

Open
timaschew opened this issue Jan 10, 2014 · 5 comments
Labels

Comments

@timaschew
Copy link

timaschew commented Jan 10, 2014

In jade you can do this: http://jade-lang.com/reference/mixins/

@RobLoach
Copy link

No reason why you couldn't use both.

@timaschew
Copy link
Author

but what is the difference?
expect that in jade is parsed before docoad do it (or what is the order?)

@timaschew
Copy link
Author

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.

@techdragon
Copy link

techdragon commented May 4, 2014

I'd say the same statement applies for using any templating engine that supports partials/includes, such as swig.

@mikeumus
Copy link
Member

Hey @timaschew.
I'd say it's fine to do a PR with the disclaimer.
Good for people to have and know of options. 👍

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

No branches or pull requests

4 participants