-
Notifications
You must be signed in to change notification settings - Fork 66
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
How are collections made available in templates #6
Comments
Found out they are available under their very own name:
The reason I didn't find this at first, is that the collections plugin must be the first to run, not the last. Very obvious actually. |
ah yup, sorry for the confusion there. they just need to be before your templating step if you want to use em in the templates |
the globals exposed are a single i've been debating whether to simplify to just a single |
I would vote in favor of just the collections global On Mon, Mar 31, 2014 at 7:40 PM, Ian Storm Taylor
|
That's an important point. I suggest to add that to |
+1 to add to the README.md in fact I think this would be a great documentation structure to suggest for all plugins given the pipeline nature of metalsmith. Maybe something like a "Template Usage" section or maybe - since we're not necessarily using the template plugin - "Using the results" or "Results"? Would help get a sense of what each plugin achieves, which for now is usually only minimally described in intros. |
+1 to add to the README, I understand that it's fairly obvious and logical to that if you need a variable in a template it needs to be defined before the template, but it's still not an immediate thing to notice, specially if you are a beginner. |
How are collections made available in templates, for example jade?
The text was updated successfully, but these errors were encountered: