This may be a really ridiculous question, but do you / should you have a new document type for each page of your website?
My site is slow, so I am trying to figure out if things were set up correctly.
Eg. Site has: homepage, about, articles, contactUs, and let's say 50 submenu pages. Would / should each of those pages (so 54 pages) have a document type? If I set it up so each has a doc type, would that affect site performance?
Number of document types shouldn't affect performance, but to answer your question, you'd need not a document type for every page. Best is to identify the "types of pages" and start from there.
Example, you may have a blog post, a content page and news section articles. Because their data might be unrelated, it's obvious to create different document types for each of these.
However, you could have a news section article presented in two different ways, in which case you don't need a different document type, but will create two different templates and specify the template you want when you create a news section article.
Does it make more sense?
Also, if you really want to know the basic building blocks, I'd suggest to have a look at umbraco.tv which is an essential resource for anyone starting to build sites using umbraco.
Good luck and post more questions when you move along on your journey.
So if you have 50 pages that have a similar layout, but different content on the page, then you would still have the same document type.
I've set it up in such a way that each of those pages has a different doc type, but you are saying that should not negatively affect things (performance, etc.), so there would be no need for me to remove all of those "duplicate" doc types.
Yes, if pages are of similar layout, a single document type might be enough (don't know enough about your use case...)
For performance > no, don't see any issue with having ~50 document types, i'm running projects with possibly +100 document types (not recommending it, kind of legacy stuff) and 1000's of nodes without issues
From a technical point of view, it's probably not best practise, but I guess you'll learn by doing it, and asking for advice/questions and getting answers will prove of great value as well (haven''t said my answer should be considered as THE solution, there's always trade off's to make)
As a rule of thumb, consider document types as tables in a database (Defining what content it is), whereas your content would be rows of such a table (the actual content)
Document Types
This may be a really ridiculous question, but do you / should you have a new document type for each page of your website?
My site is slow, so I am trying to figure out if things were set up correctly.
Eg. Site has: homepage, about, articles, contactUs, and let's say 50 submenu pages. Would / should each of those pages (so 54 pages) have a document type? If I set it up so each has a doc type, would that affect site performance?
Number of document types shouldn't affect performance, but to answer your question, you'd need not a document type for every page. Best is to identify the "types of pages" and start from there.
Example, you may have a blog post, a content page and news section articles. Because their data might be unrelated, it's obvious to create different document types for each of these.
However, you could have a news section article presented in two different ways, in which case you don't need a different document type, but will create two different templates and specify the template you want when you create a news section article.
Does it make more sense?
Also, if you really want to know the basic building blocks, I'd suggest to have a look at umbraco.tv which is an essential resource for anyone starting to build sites using umbraco.
Good luck and post more questions when you move along on your journey.
--Dirk
Thanks!
So if you have 50 pages that have a similar layout, but different content on the page, then you would still have the same document type.
I've set it up in such a way that each of those pages has a different doc type, but you are saying that should not negatively affect things (performance, etc.), so there would be no need for me to remove all of those "duplicate" doc types.
Yes, if pages are of similar layout, a single document type might be enough (don't know enough about your use case...)
For performance > no, don't see any issue with having ~50 document types, i'm running projects with possibly +100 document types (not recommending it, kind of legacy stuff) and 1000's of nodes without issues
From a technical point of view, it's probably not best practise, but I guess you'll learn by doing it, and asking for advice/questions and getting answers will prove of great value as well (haven''t said my answer should be considered as THE solution, there's always trade off's to make)
As a rule of thumb, consider document types as tables in a database (Defining what content it is), whereas your content would be rows of such a table (the actual content)
--Dirk
Ok, that makes things a lot clearer! Thanks again Dirk.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion