I have a large collection of articles to be shown on my website. Could anyone give a suggestion how i need to add articles? Do i need to add each article as a node on the content section or i need to create a custom table and add, edit and delete articles through this custom table?
A common, and arguably the best way, to do this would be to set up a document type to contain articles, then create an article data type to allow articles to be created inside the container. Then you can set up a node in your content area called 'articles' of the 'article container' document type, inside which you can add multiple articles.
You can then easily pull your articles into your template through XSLT or Razor.
The other way to do it would be by using some kind of data-type to allow you to create multiple pieces of content within one node (e.g. uComponents datatype grid) but that has several potential down-sides for your particular scenario, such as lack of support for RTE and unweildy user-interface if you have lots of articles.
Another way would be to create a custom table to hold the articles, but really there's no need - you'd be re-inventing a lot of existing functionality.
Personally I'd use nodes in a container folder to tackle this.
I thought about the first method but if creating articles like nodes, there will be 1000's of nodes under article container node. The problem here if i want to search and edit one particular articles it is not user friendly. This is why i thought about a custom table and create a custom section in the admin side to search, list, add, edit and delete functionality. Give a response.
A common way to tackle that would be to organise your articles into sub-folders, such as alphabetically or by date (year and or month). It's been a while since I last did this but there used to be packages to do this automatically, so that when you create an article node it automatically creates year/month folders to put your article into. See the datefolders package for example. I would say that listing thousands of nodes in the back-office without dividing them into sub-folders is a bad idea as there will be performance issues there. There's the potential to customise the back-office search to be more relevant if you require more control over the back-office search.
The 'radical' approach would be to use a custom table and write a hive provider using Umbraco 5, which is kind of what it's there for. I guess it depends on the detail of the project and where your skills lie.
Umbraco nodes or Custom table
I have a large collection of articles to be shown on my website. Could anyone give a suggestion how i need to add articles? Do i need to add each article as a node on the content section or i need to create a custom table and add, edit and delete articles through this custom table?
Waiting for a valuable suggestion.
Hi, and welcome to the forum!
A common, and arguably the best way, to do this would be to set up a document type to contain articles, then create an article data type to allow articles to be created inside the container. Then you can set up a node in your content area called 'articles' of the 'article container' document type, inside which you can add multiple articles.
You can then easily pull your articles into your template through XSLT or Razor.
The other way to do it would be by using some kind of data-type to allow you to create multiple pieces of content within one node (e.g. uComponents datatype grid) but that has several potential down-sides for your particular scenario, such as lack of support for RTE and unweildy user-interface if you have lots of articles.
Another way would be to create a custom table to hold the articles, but really there's no need - you'd be re-inventing a lot of existing functionality.
Personally I'd use nodes in a container folder to tackle this.
Hope this helps...
Thank you for the reply.
I thought about the first method but if creating articles like nodes, there will be 1000's of nodes under article container node. The problem here if i want to search and edit one particular articles it is not user friendly. This is why i thought about a custom table and create a custom section in the admin side to search, list, add, edit and delete functionality. Give a response.
A common way to tackle that would be to organise your articles into sub-folders, such as alphabetically or by date (year and or month). It's been a while since I last did this but there used to be packages to do this automatically, so that when you create an article node it automatically creates year/month folders to put your article into. See the datefolders package for example. I would say that listing thousands of nodes in the back-office without dividing them into sub-folders is a bad idea as there will be performance issues there. There's the potential to customise the back-office search to be more relevant if you require more control over the back-office search.
The 'radical' approach would be to use a custom table and write a hive provider using Umbraco 5, which is kind of what it's there for. I guess it depends on the detail of the project and where your skills lie.
Hopefully food for thought though.
Thank you Dan for the detailed information. We will think about it.
Maybe this old topic can help: http://our.umbraco.org/forum/developers/extending-umbraco/10412-Store-webshop-products-as-nodes-or-in-a-custom-table
Jeroen
is working on a reply...