content management system - Developing an asset/node based CMS -

I am a page-based (why, instead of doing so, using the property-based architecture to create fun / personalized CMS I want to develop the purpose of this question), but I did not get much information on this subject. Everything I have found is that the surface is roughly crushed (a good chance I am searching with the wrong words).

As the information on property-based CMS stores is called property block.

What are the benefits (DIS) of such a system?

What is the primary principle of asset based architecture?

What should not be 'property' and what? Where can I read?

After leaving my comment, try to answer it :)

Your definition of "property" is on the lines of "node" (like a drupp), or some documents (such as json-style documents in MozodiBi or CHDB), here's some information:

I I'll use the word "node" for the post, I think it is the closest and most popular form of "asset" is. This can also be a very clear answer, but hopefully it will point you in the least thinking and right direction.

The node-based architecture, nerve networking pattern and object-oriented programming key is that "nodes" are digits of data, and nodes can be connected to each other in some other way.

Some architecture treat nodes as objects-oriented classes, where there are different sections of your nodes that can attain different symptoms of parental nodes- each type of node has the basic properties of its origin Handle - A "essay" node can achieve the properties of a "text-document" node, which in turn receives the properties of the base node. Droplet implements this legacy model, although it does not emphasize the connection between the nodes, which is something like Facebook's grappa / open graph protocol.

This pattern of node-based architecture can be implemented at any level, and is present in nature - the idea of ​​social circles within society or ecosystems;) At the software engineering level, this one Can take the form of a database, such as MongoDB has nodes of data (which is called a document in that case). These documents can refer to other documents, however, such as Drupal does not insist on the Mongo engagement. Ironically, unlike document-based databases, relational databases like MySQL actually insist on excess, but this is a discussion for another day. I have mentioned above that Facebook's Grapeppee has been implemented at a web API level. The Open Graph Protocol gives it shape and then, like a drap, it is implemented at some front-end level (although the bottom-end node pattern is applied to its lower level).

Finally, node-based architecture is more flexible than traditional document / page based CMS architecture, but it also means that there is a lot of programming and configurations in favor of developers. A node-based system will eventually be connected to a greater difference and its components will be integrated with one another's deeper levels, but it can be more sensitized to break due to this deeper level of connection - it is less than different Personally, in personal modules, I see a huge tendency where people are moving forward to becoming "node-based" and less "content-based" because people with websites Trakt start to do, such as electronic magazines as they did in the 90s. Also, node-pattern is well-fitted with increasing emphasis on user-contributing and social browsing because people and their accounts / profiles on a web site dramatically increases complexity.

I know that you have said "property", so I would also say that the asset node gives more emphasis on the data side of the pattern, while "node" is the relationship between the pieces of the maximum data Emphasizes.

But for further reading, I tell about the software that I mentioned. You can also check node.js, JSON, and document-based databases, and grieppe because they are well-fit with this idea of ​​property / node-based architecture. I am sure Wikipedia has some good stuff on these samples.