discuss.answer
-
☆ A M B ☆
- 2,213 Posts
I've done single page sites in the past using two different methods:
a) Create each section as a normal page, adjusting your pdoMenu/Wayfinder call to output a single page menu. I then use pdoResources/getResources to bring those subpages into the main single page.
b) It took a little extra work, but I was also able to use Content Blocks to power a single page site. The menu was generated using pdoTools along with weblinks, but could alternatively be done manually.
Ultimately, the best choice will depend on your client and what method works best for them. The first method is a little easier to setup, with the second method being more an exercise in possibility/practicality. If there was a method to output a menu based on the layouts used on the page in question it would have been easier to accomplish.
-
☆ A M B ☆
- 24,524 Posts
It shouldn't be too difficult to parse a single resource's content and pick out the section headings to build a menu out of.
However, I have found that the bigger the resource content is, the more likelihood of somebody messing up the whole page. Using separate resources for each section and building the page with pdoResources or something similar is much easier for clients to keep updated without breaking the whole page.
Basically, I use parent/child resources as standard for creating content (easier for content editors to update sections), use pdoResources to pull content into a single page structure, use pdoMenu to create the page nav along with pdoTools fast field to pull the alias of parents/children to use as the div hash for single page navigation.
-
☆ A M B ☆
- 2,213 Posts
You shouldn't need to use fastfield, but otherwise correct.
Thanks for all the help on this issue.
pdoResources looks like a great solution.
