Ok, so here is my question.
For general website layout - think CMS.
Let me say, that I am pretty sure other applications may offer this, but I am asking in regards to the software I am building currently. So with that said. On to the questions.
I have noticed a trend lately (for awhile actually) where some of the "major" sites out there, corporate, are using designs that when you click the main nav it scrolls you to that section. Now, for some designs I like this alot. So, I have been considering offering a feature in my cms that allows the user to choose a set of "pages" that will be built out in the landing presentation (landing page for lack of a better term, think site index). Now, along with that, when that feature is enabled ALL other pages go into a drop down based on page structure (think parent, child relationship) so they are still accessible, but will reload the app context between the header and footer sections to present their data (think ajax), the entire app will be SPA, it's just the landing, and the pages attached to it that will scroll. What are your thoughts on this?
Of course this presents a issue. What if none of the pages are attached this way? Well, I will provide options that allow pages to be marked as main nav items without the scrolling option, then they will build main nav options (nav tabs, buttons, whatever) and they will follow the same workflow that is already supported, which would be to fetch the content and update the app workspace (area between header and footer).
Which would immediately give a lot of flexibility to theme authors as each theme could be presented either way with zero changes.
Thoughts?
For general website layout - think CMS.
Let me say, that I am pretty sure other applications may offer this, but I am asking in regards to the software I am building currently. So with that said. On to the questions.
I have noticed a trend lately (for awhile actually) where some of the "major" sites out there, corporate, are using designs that when you click the main nav it scrolls you to that section. Now, for some designs I like this alot. So, I have been considering offering a feature in my cms that allows the user to choose a set of "pages" that will be built out in the landing presentation (landing page for lack of a better term, think site index). Now, along with that, when that feature is enabled ALL other pages go into a drop down based on page structure (think parent, child relationship) so they are still accessible, but will reload the app context between the header and footer sections to present their data (think ajax), the entire app will be SPA, it's just the landing, and the pages attached to it that will scroll. What are your thoughts on this?
Of course this presents a issue. What if none of the pages are attached this way? Well, I will provide options that allow pages to be marked as main nav items without the scrolling option, then they will build main nav options (nav tabs, buttons, whatever) and they will follow the same workflow that is already supported, which would be to fetch the content and update the app workspace (area between header and footer).
Which would immediately give a lot of flexibility to theme authors as each theme could be presented either way with zero changes.
Thoughts?
Last edited:
