For our company i have been developing a CMS for years now, because it's hard to keep up with developing i am looking to use a open source CMS.
Because i am developing in C#, Umbraco looks like the obvious choice.
I am happily suprised by the extensibility of Umbraco and i am certain i can tweak it so it will have the same features as our own CMS.
In our own CMS we had more separate content sections: articles, pages, events etc. It looks like in Umbraco everything will be placed in the "content" section.
When i see this i get a natural urge to customize Umbraco so i can split the content in separate sections.
Is this easy to do ? And do you recomment this kind of separation, or would you slap me on the wrist en tell me to embrace Umbraco's filosophy to keep this kind of content in de content section ?
When you are working with Umbraco then everything thats frontend related will come into the content section ( stylesheets, javascript and other static files are excluded ). In this way you only have to work in one place and you have a nice overview about how your content is structured because of the treeview.
What many developers do is you seperate some of the elements into a seperated root node.
What I mean about that is your content always starts with a root node, for example Home, after that you add child nodes along the way to structure your content. But sometimes you want to add elements to your page that doesn't require a template ( and no template means no direct url to that node ). What we then do is creating some sort of a Content Repository. This is also a root node in our content section, but the only difference here is that it will only contains document types without templates.
For example, newsitems, sliders, contacts, and so on. These all do not require a template so we can add these in our Content Repository.
In your CMS you say you use articles / pages / events. What you can do then in Umbraco is:
Pages: normal document types with template to add under your Home root node.
Articles/events: if they need to be accessed by an url you can add them under your Home root node or another node where you want to add these items. Or if they doesn't have to be accessed by an url then you can create a Articles Repository and a Events Repository under your Content Repository. Then using content pickers or partials views you can tweak the way they are presented on one of your pages.
If you are a beginner with Umbraco we always recommend to have a look at http://umbraco.tv/. There you have a lot of videos with tutorials about how to use Umbraco and tweak it. It requires you to take a license but the money is well spended.
If you have any questions then just add them to our forum here and we will try to help you out in the best way be can.
Hope you find this usefull and start loving this wonderfull CMS.
split content section in : articles/events/pages
For our company i have been developing a CMS for years now, because it's hard to keep up with developing i am looking to use a open source CMS.
Because i am developing in C#, Umbraco looks like the obvious choice.
I am happily suprised by the extensibility of Umbraco and i am certain i can tweak it so it will have the same features as our own CMS.
In our own CMS we had more separate content sections: articles, pages, events etc. It looks like in Umbraco everything will be placed in the "content" section.
When i see this i get a natural urge to customize Umbraco so i can split the content in separate sections.
Is this easy to do ? And do you recomment this kind of separation, or would you slap me on the wrist en tell me to embrace Umbraco's filosophy to keep this kind of content in de content section ?
Hi Teade,
When you are working with Umbraco then everything thats frontend related will come into the content section ( stylesheets, javascript and other static files are excluded ). In this way you only have to work in one place and you have a nice overview about how your content is structured because of the treeview.
What many developers do is you seperate some of the elements into a seperated root node.
What I mean about that is your content always starts with a root node, for example Home, after that you add child nodes along the way to structure your content. But sometimes you want to add elements to your page that doesn't require a template ( and no template means no direct url to that node ). What we then do is creating some sort of a Content Repository. This is also a root node in our content section, but the only difference here is that it will only contains document types without templates.
For example, newsitems, sliders, contacts, and so on. These all do not require a template so we can add these in our Content Repository.
In your CMS you say you use articles / pages / events. What you can do then in Umbraco is:
Pages: normal document types with template to add under your Home root node.
Articles/events: if they need to be accessed by an url you can add them under your Home root node or another node where you want to add these items. Or if they doesn't have to be accessed by an url then you can create a Articles Repository and a Events Repository under your Content Repository. Then using content pickers or partials views you can tweak the way they are presented on one of your pages.
If you are a beginner with Umbraco we always recommend to have a look at http://umbraco.tv/. There you have a lot of videos with tutorials about how to use Umbraco and tweak it. It requires you to take a license but the money is well spended.
If you have any questions then just add them to our forum here and we will try to help you out in the best way be can.
Hope you find this usefull and start loving this wonderfull CMS.
Hace a nice day!
/Michaël
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.