Anti-Patterns
What NOT to do
A few Umbraco content patterns are prevelant thoughtout the community and you will see them in many Umbraco instances out there in the wild. Some are even taught in official lessons or documentation.
Global Manifesto says NO
- Do NOT create webpage subnodes if they are not webpages themselves. Use either global data or complex data types like Grid control, Nested Content within the webpage itself instead etc.
- Do NOT create arbitrarily links between pages using ancestors, siblings or descendants searches. Instead use content pickers or MNTP to set links
- Do NOT use hard coded ids or magic names to make links between pages. Use Content Pickers instead.
- Do NOT hardcode Urls that deliever webpages. This is prevelance in those that have external data but don't implement in an Umbraco way. Use ContentFinders instead.
Good content nodes structure creates flexible Umbraco instances, which makes happy content managers.
