php - webapp vs. CMS - the same or not -


I think the classical definition of a CMS: this is a "webpad" whose main purpose is to handle "content" This is generated by our users (like all of us, the more content here and what we provide is the text and the code).

I always got the impression that making CMS is really difficult but how? CMS is not just a webfone like any other I think many webapps are difficult to code in comparison to traditional CMSs.

If I were to create a CMS like making any other webapp, would I be wrong?

I think that you can consider CMS as another type of web application; The only thing is that there are a lot of functionality, both of which are necessary, and / or required by the users.

Some of those that come to mind:

  • Authentication / Access control
    • For application
    • But in every way
    • And even, maybe, each area of ​​each type of content
  • A small bit of Ergomony - especially if technical users Do not aim.
  • Dealing with media (photos, videos, music, flash content, ...);
  • If you have to design a CMS that is not oriented towards a specific website, then you have to make some generic, which can work in those cases which you do not think about
  • < Li> Extensibility: You will create the core of your CMS;
  • / Li>>

    OK, this is actually a short list indeed; And maybe there are many other ideas that can come to mind ...

    So, yes, a CMS is a web application - but it should be normal, if you want to work it for more only From one (type) website


Comments

Popular posts from this blog

asp.net - Javascript/DOM Why is does my form not support submit()? -

sockets - Delphi: TTcpServer, connection reset when reading -

javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -