Hello. I have installed Grav yesterday, far from an expert - but I googled and documentationed before posting this.
Question: Can I reuse existing content as components of a modular page?
That is: Imagine that I have a modular page “modular_page” which shows page A in slot “_top” and page B in slot “_main”. Can I use the same page A and page B in slots “_left_top” and “_left_bottom” in the modular page “another_modular_page” - ?
I refuse to believe at this point that the only way is to duplicate page A and page B.
Thank you for your time!
@grav101, On many forums, including this forum, it’s a good habit to show which docs you’ve consulted, what you’ve tried and where things got stuck.
@grav101, Admin does not cater for all possible situations…
Keep in mind that a modular page is constructed using a collection of modules. Have a look at the following sections of the docs:
Thank you for the response. It highlights the main issue I am having: I am expected to know a lot about Grav even to ask the most noob question. Complex collection - good to know, thanks!
As I am reading the official page about Complex collections, I keep asking myself: “What is the use case? What everyday problem is solved by this approach? When should I use complex collections and not, for example, simple collections or modular pages?” With my severely limited knowledge, I cannot answer this question, and thus cannot learn enough about Grav to seriously consider it for my business needs.
If a 5-year old asked you “How do I use Grav?”, where would you suggest that they start? Thanks.
If a 5-year old asked you “How do I use Grav?”, where would you suggest that they start?
“I’m sorry, but Grav wasn’t build for a 5-year old. You first need to go to school, do sports and eat you spinach.”
Grav is build with speed and flexibility in mind, which is why it is a flat-file cms. See the bottom section of About. That lead to the following:
- It’s fast.
- It’s easier to extend.
- Everything can be done using any file editor you prefer and the CLI.
This also means you’re expected to understand the concepts.
- Admin is an add-on providing an easy interface for configuration, page editing and necessary tooling.
Except for easiness, Admin does not add any capabilities to Grav itself.
- Backup/restore is as simple as copying the
I agree most of the above is useless to a non-developer who wants to manage all aspects of a cms from a graphical user-interface.
If none of the themes or plugins provide the functionality you require out-of-the-box, you will need to know the concepts of Grav, knowledge of Twig templates and/or PHP to extend the functionality.