-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
request: add page and pages/collection variables to the context #930
Comments
@danifornells Thanks for the issue! If you're reporting a bug, please be sure to include:
If your issue is related to one of the following, please open an issue there:
|
There is some information about this on the readme.
Sorry to hear that, you could have saved some time by checking the readme first.
Thanks for the input, but we won't be adding We are working on documentation, and one of the things we'll be adding is a migration guide for switching from grunt-assemble to assemble. We've also discussed publishing a plugin that adds the defaults used in grunt-assemble, so that it can be used in assemble or grunt-assemble. closing since I think this has been clarified. |
Thanks, crystal clear.
|
after thinking about this more, I'm going to reopen so we can discuss more. What else would you like to see in assemble by default? |
Great to see this as an open discussion. How I discovered and decided to use assemble? How did I feel using it? What I would like to see on assemble?
I do not have a lot of time for OS, and I am investing few in other project, but I can help on documentation if you need a hand. Would I recommend assemble to others?
|
version
assemble v0.24.3
description
Question:
I am moving assemble tasks from grunt-assemble to assemble. After doing that and having everything working, I realized that grunt wrapper adds page and pages data that helps a lot on resolving common things like navigation menu.
After struggling myself and checking spread and obfuscated docs, I suspect to found the two sources doing the jobs:
As far as I know, the main difference from assemble-core and assemble, is that the last one, besides other improvements, comes with the pages/collection feature pre-configured and ready to work.
In my opinion, having the pages/collections fully working, should include both mentioned plugins configured, otherwise you cannot have fully functional feature.
Let me know if the proposal makes sense, or correct me if I am wrong.
assemblefile.js
Assemble file is not relevant on this issue, it is just a question
The text was updated successfully, but these errors were encountered: