Hi All:
I see that adding CMS features is on the Roadmap. I am trying to convince the team at my work to adopt ASP.net ZERO for all our development, but the cms features would be needed.
I am wondering what the best plan for that would be. Perhaps integrating an existing open source CMS project would be quickest and maybe best way to add this functionality? I guess integration would need to have a system for sharing of user base / auth.
Or does ABP/Z team plan to build from scratch so that it is more deeply integrated?
Any timeline for intial release? Will it include versioning of CMS documents?
8 Answer(s)
-
0
Also, perhaps existing clients of asp.net zero have already added some cms features on their own that they would hopefully be willing to contribute back to the anz? This would be in their best interests since it would then allow the asz team to focus elsewhere on yet more features (-:
-
0
Hi @dparizek,
We thought on CMS and we decided to integrate an existing CMS if possible. Because, a CMS is a very compherensive system. While we can make a small subset, most of our customers will need other features and will compare with existing CMSs. We think it's not our business (at least, for now). If we can integate user base with an existing CMS, that will be excellent. We will investigate it in near future.
-
0
Hello there, please review this link , it's one of the most filemanager i have ever seen
http://www.element-it.com/asp-net-explorer-browser/online-share/web-file-manager.aspx -
0
I think AspNetZero is more Enterprise Web Application Framework for business applications, not a CMS. I prefer to define what is the CMS requested features by clients before doing any efforts , as I face a lot of people have a confusing between CMS , ECMS , WCMS , DMS :oops:
CMS > Content Management System, ECMS > Enterprise Content Management System, WCMS > Web Content Management System, DMS > Document Management System,
for WCMS there are many free available in the market, and you can take a look to evaluate the integration
<a class="postlink" href="https://our.umbraco.org/">https://our.umbraco.org/</a> <a class="postlink" href="http://www.orchardproject.net/">http://www.orchardproject.net/</a> <a class="postlink" href="http://kooboo.com/">http://kooboo.com/</a> <a class="postlink" href="https://piranhacms.org/">https://piranhacms.org/</a> <a class="postlink" href="https://www.composite.net/">https://www.composite.net/</a>
finally I recommend to focus more on Enterprise Application Framework [Features] ;)
-
0
Rashed is completely correct! There are lots of good CMS systems out there. I use this framework because it is NOT a CMS! I think if you needed CMS functionality for say a blog or something like that, then this is a good place for an aspnetzero_contrib project where users could share different examples of implementations on top of AspNetZero. But keep in mind, there are already 3 different front ends of AspNetZero (Jquery, Angular, Angular2), and hopefully more coming :)
I would rather see many more implementations with different front ends, a React version, React / Redux version, Aurelia version. Give developers more choices on the front end instead of bulking up the back end. Keep the framework just a framework! I think doing this type of stuff and maintaining a CMS type system would be very difficult.
As always, this is my opinion! It's good to be able to openly discuss this stuff.
-
0
Hi @JeffMH,
Thank you very much for your valuable opinions :). We will definitely consider this.
Thanks again.
-
0
Is there any direction in the new roadmap to integrate with any CMS?
I really need simple CMS functionality to my website, any recommendations?
-
0
Hi,
It is not in our road map for now.
