I will need to set up a magazine site in the very near future. This could potentially grow very large over time (assuming ~2 posts per day).
Do any of you have any tips on how to go about handling this? I am mostly concerned about content structure. Do you go for example for:
home/category/title
home/category/year/month/day/title
or do you have any suggestions for a better structure?
Any tips for scalability? I have made a news site before with lots and lots of content nodes but in V4 and that definitely had a lot of performance issues. I know most, if not all, of those issues will have been resolved in the very latest releases of Umbraco, but I was just curious if any of you ran in to performance issues. And if so, how you went about tackling them.
Why structure the pages under subfolders at all? I could see doing this in the past due to it taking some time to expand content nodes with lots of children, but now that list view works well I don't see any reason that can't be used instead. That is, just put all the nodes under a single parent node (say, the homepage or some node that serves as a bucket).
As far as the speed of the frontend of the site, you can use some intelligent caching. I tend to rely on this:
Basically, you can convert the posts to instances of some class (say, MagazinePost), then store that in a list, which you can then store in an InstanceCache. You can then use an invalidator to force that cache to update whenever the content changes.
Best practices for setting up magazine site
Hi fellow Umbracians.
I will need to set up a magazine site in the very near future. This could potentially grow very large over time (assuming ~2 posts per day).
Do any of you have any tips on how to go about handling this? I am mostly concerned about content structure. Do you go for example for:
Any tips for scalability? I have made a news site before with lots and lots of content nodes but in V4 and that definitely had a lot of performance issues. I know most, if not all, of those issues will have been resolved in the very latest releases of Umbraco, but I was just curious if any of you ran in to performance issues. And if so, how you went about tackling them.
Thanks for your input.
Hi Giovanni
I would recommend you do not use "category" as part of URL, because what if you would like to have few categories for one post?
I would like to use some checkbox list for categories for example.
This structure is nice:
Thanks,
Alex
About performance, if you will not touch problems described in this article - https://our.umbraco.org/documentation/reference/Common-Pitfalls/, it will work really fast.
Thanks Alex. This article is really helpful.
Why structure the pages under subfolders at all? I could see doing this in the past due to it taking some time to expand content nodes with lots of children, but now that list view works well I don't see any reason that can't be used instead. That is, just put all the nodes under a single parent node (say, the homepage or some node that serves as a bucket).
As far as the speed of the frontend of the site, you can use some intelligent caching. I tend to rely on this:
Basically, you can convert the posts to instances of some class (say,
MagazinePost), then store that in a list, which you can then store in anInstanceCache. You can then use an invalidator to force that cache to update whenever the content changes.Hi Giovanni, not directly related to your question but have you considered using PugPig?
https://our.umbraco.org/projects/starter-kits/pugpig-for-umbraco-v7/
is working on a reply...