nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Content Model, Best practices?

kbonnet

Hi All,

When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/properties directly to the aspect instead of to the content type?

Does anyone have experience with this decission?

Thanks for your posts!

Koen Bonnet

Find more posts tagged with

Comments

rdanner

Hi All,

When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/properties directly to the aspect instead of to the content type?

Does anyone have experience with this decission?

Thanks for your posts!

Koen Bonnet

Personally I think you want to consider your types carefully. In OO deep hierarchies can lead to issues and I think the same thing applies here.

Aspects can be added and removed and unless I have a very good reason to make a type, I'll tend to make an aspect (if we are talking about extensions of cm:content or cm:folder or other existing types.)

Good question BTW, I am curious to hear what others have to say.

dhalupa

Well, my approach, not necesserally the correct one

, is the following, I am trying to identify types like things which have strong evidence of existence like Invoice, Purchase Order, Purchase Requisition, Partner, Supplier… After that from these nouns I am creating types without any properties (sort of like marker interfaces) and I am trying to apply as much of properties through apects. Only if property is very much specific for a certain type I will apply it directly to the type.

Kind regards,

Denis

alarocca

I think this is a great resource:

http://ecmarchitect.com/images/articles/alfresco-content/content-article.pdf

BR,
Alessandro

Hi All,

When developing a custom content model, what are best practices so far? I can either attach properties to content types, but also to aspects. I can automatically attach aspects to content with a content rule, based on a content type. But what are the consequences when i attach metadata/properties directly to the aspect instead of to the content type?

Does anyone have experience with this decission?

Thanks for your posts!

Koen Bonnet