I have 10 years of experience in ASP.NET MVC mainly for building web applications (not web sites). and now i am starting a new project to build a web application which have a registration modules (only accessed by registered users) and also a public facing web site. for the public facing website it will contain 5 modules:-

1. About Us.
2. Contact US.
3. Services
4. Our Team.
5. Home page

where i need some kind of CMS, to allow end users to modify the above 5 sections's data without having to touch the source code.

i read about Umbraco which seems a very well established CMS for .net application, but i were thinking why not to build the CMS capabilities by myself. so is this a valid appraoch to follow? i can create some screens/modules which allow the users to enter the above sections' data (mainly text, images, links and videos) and show them accordingly? so is building our own CMS a valid approach to follow?

Thanks

CodePudding user response：

Umbraco is free, open source and very easy to extend. It has membership/login/locked off areas built in, which also can be extended fairly easily if need be. So I'd say try that out before beginning to consider building your own CMS. My 20 years experience with building, implementing and using content management systems including Umbraco tells me you'll enjoy that way more than having to maintain your own.

On our.umbraco.com there docs and guides galore to get you started, as well as a very friendly forum.

CodePudding user response：

I've built around 100-150 Umbraco projects over the past 8 years and can safely say, if the purpose of your project is managing content, you're not able to build something from scratch, that'll be better at managing content than Umbraco.

However, if your project has specific requirements or features that don't belong in a CMS, it may be worth considering building an application from scratch, instead of attempting to turn Umbraco into something it isn't.

An informational/marketing website might "expire" design-wise in 5-6-7 years and a redesign would be required, which might be costly for the client, if all features are built into the CMS website which will be needing the redesign.

Therefore, consider using Umbraco as a CMS for what it's good for, but build a custom application for any additional needs? Umbraco can indeed handle membership functionality, but it still might make sense to build the membership functionality in its own application to avoid adding it as a dependency on the "informational" website? After 5-6-7 years when the client might want the public facing website redesigned, the best approach IMO would be to create a new, fully updated Umbraco solution. It's unlikely your membership application would need a redesign - it's for "internal use", not for marketing purposes.

Anyways, that's just my take. I hope it was just a bit helpful.