How to use Extended Attributes/SubType
Not long ago we blogged about how to dynamically create Extended Attributes/SubTypes. After its post a commenter asked some VERY good questions.
"This might seem like a really basic question, but where would this code go? Could you build an example to show us what a sub page might look like? Would it be smart to use this for something like a resume, where the sub type would store data such as job and education history?"
This expressed to me that we needed much better documentation on the Class Extension Manager which I am happy to say is now available! We encourage you to read the documentation and learn how to build subTypes and attributes through Mura's admin before venturing into building them up dynamically. You may find that the admin console provides you all you would need to get things started.
Now on to the questions
"This might seem like a really basic question, but where would this code go?"
This type of code can be placed either within a site's eventHandler or within a Mura plugin. Within the event handler/plugin you could hook to something like the onApplicationLoad event (this event only fires when Mura is either loaded for the first time or reloaded).
"Could you build an example to show us what a sub page might look like? Would it be smart to use this for something like a resume, where the sub type would store data such as job and education history?"
Yes. What you can do is create either a Mura page subType or a user subType. This all depends on your overall needs of course. If you would like to correlate resume information to a user's profile for instance, then you would go the "user" type route. If the resume is meant to accompany the "user" type then you could build a "page" subType, then link it to the user's profile. The examples found within the Class Extension Manager's documentation should cover the basics on how to do this.
If anyone has any other questions, please let us know so we can write some more stuff up for you.
Team Blue River