-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Plugin does not work for markdown sources in collections #5
Comments
@FokkeZB are you saying that without the plugin they're converted to markdown, or that they're not copied at all? With the plugin, it sounds like they're copied but not rendered, is that correct? |
What I mean is that Markdown files with no front matter that are part of collections are not processed by this plugin. As the source code shows it only processed pages. |
This would be especially helpful because Jekyll itself used to process files without frontmatter in collections, but stopped doing so in version 2.2.0. jekyll/jekyll-help#223 |
I'd be glad to a review a PR if someone would like to make this opt-in for collections (e.g., via flag when the collection is describe in the config). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@benbalter - Would be great to get this functionality added :) Looking to get the 96boards.org documentation into a pure markdown format! BR, Kyle |
Markdown files with no front matter are copied to
_site
as-is, with no.html
version.I'd expect the plugin to work on markdown sources in collections as well.
The text was updated successfully, but these errors were encountered: