One approach to handling this is to treat each section as it's own document type.
You would then create each document type beneath "Home" and render each child template accordingly.
A basic example could look like so:
Home
Discover
Features
etc.
You could also use a multi-node treepicker to select nodes instead, which would allow you to have more flexibility in how your project is structured - but ultimately they both do the same thing.
I don't know about the best way, but if you code your site in HTML and get it working in a browser first, it might make it easier. Then you can take that HTML and simply paste it into an Umbraco template. You can stop there and simply update the template each time you want to change things, or you could move on and attempt to break things down into document types. When you get to that point, you have to begin with the end in mind, as it will help you understand how you need to structure things.
That being said, the point I want to emphasize is that that when you look at the output of a page completely separate of how it actually operates[is administrated], there are many solutions. The solution that you need, comes from listening to who you are building the site for. You can feed Umbraco something hard coded to serve as a deliverable and then slowly put in the ability to change various parts of the site.
what is the best way to make this flow like in this theme
How do i make this flow like in this theme in umbraco. I simply can't figure it out
https://blackrockdigital.github.io/startbootstrap-new-age/
Hi Mikkel
What did you mean to make this flow like in this theme?
Do you want to do the same page in Umbraco?
Thanks,
Alex
One approach to handling this is to treat each section as it's own document type.
You would then create each document type beneath "Home" and render each child template accordingly.
A basic example could look like so:
You could also use a multi-node treepicker to select nodes instead, which would allow you to have more flexibility in how your project is structured - but ultimately they both do the same thing.
I would recommend using Nested content or Stacked content for blocks like that.
Check out these packages, they are awesome for block's structure, like you need.
https://our.umbraco.com/documentation/getting-started/backoffice/Property-Editors/Built-in-Property-Editors/Nested-Content/
https://our.umbraco.com/packages/backoffice-extensions/stacked-content/
Thanks,
Alex
I don't know about the best way, but if you code your site in HTML and get it working in a browser first, it might make it easier. Then you can take that HTML and simply paste it into an Umbraco template. You can stop there and simply update the template each time you want to change things, or you could move on and attempt to break things down into document types. When you get to that point, you have to begin with the end in mind, as it will help you understand how you need to structure things.
That being said, the point I want to emphasize is that that when you look at the output of a page completely separate of how it actually operates[is administrated], there are many solutions. The solution that you need, comes from listening to who you are building the site for. You can feed Umbraco something hard coded to serve as a deliverable and then slowly put in the ability to change various parts of the site.
is working on a reply...