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

Unable to complete plugin, due to index file names being hardcoded #47

Closed
smebberson opened this issue Aug 28, 2012 · 1 comment
Closed

Comments

@smebberson
Copy link
Contributor

I've created a plugin for Wintersmith that allows you to use Jade as a content plugin, not just a template plugin (I like a little bit more control over my HTML sometimes than what Markdown affords me).

You can see the plugin here, https://github.com/smebberson/wintersmith-jade

I've had to modify wintersmith however (smebberson@ee44c94) so that it can accept an index with a different extension.

What would be the best approach to making this a part of wintersmith? Should the wintersmith.registerContentPlugin accept a list of index filenames that it needs to be aware of?

@jnordberg
Copy link
Owner

This was fixed in f6f3e1c. If you update your fork it should be all good :)

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

2 participants