Rafa Lluis 2 Years Ago There are tons of possibilities here. Thanks for sharing! Please sign in to reply. Reply as... Cancel
Evan Thibodeau 2 Years Ago If you want to see an example of a site initializer created in a workspace outside of Portal check out the one I created here: https://github.com/lfrsales/site-se-site-initializerIt includes examples for creating web-content including structures and templates, collections, display page templates, pages, master pages, navigation menus, style books, and widget templates. Site Initializers really are a powerful way to programmatically create sites and content. Please sign in to reply. Reply as... Cancel David H Nebinger Evan Thibodeau 2 Years Ago - Edited Thanks Evan! When you need to implement one, having more examples available as a reference can be a great thing! Please sign in to reply. Reply as... Cancel
David H Nebinger Evan Thibodeau 2 Years Ago - Edited Thanks Evan! When you need to implement one, having more examples available as a reference can be a great thing! Please sign in to reply. Reply as... Cancel
Dominik Marks 2 Years Ago - Edited Nice explanations David.However I still prefer using the resources importer. Exactly because it is the easiest way to get resources into an existing site. Webcontent templates or application display templates are mostly written by our designers and they don't know how to write Java code (which is required for site initializers). They just want to write their Freemarker templates and have them deployed somehow. In our case we have written our own "advanced" resources importer that is able to import even more type of resources like application display templates for the new search portlets, vocabularies and categories or document types (https://github.com/dmarks2/advanced-resources-importer) Please sign in to reply. Reply as... Cancel