6.0 Theme

6.0 Theme

This question has suggested answer(s)

Is there any documentation and best practice on how to create a 6.0 theme?  I understand that the way that we create themes are much different from 5.x.  Before, we used to copy the "fiji" theme in the physical web directory and start from there.  In 6.0, there is no fiji directory anymore.  We used to be able to make changes to *.master pages.  In addition, we used to defined custom-created header fragments and footer fragments in theme.config for a specific theme.  Understand that in 6.0, we can create widgets for headers and footers as well.  Is creating widgets the only way?

All Replies
  • All the documentation to date is here including a section on Themes: http://telligent.com/community/developers/w/developer6/
     
    To answer some of your questions directly, the easiest way to create a new theme is still to copy a theme such as Fiji and re-import as a new theme.  The difference being is that you can do this all in the Control Panel and are not dealing with files anymore(as you noticed with the lack of the folder).
     
    Making changes to master pages really has not been recommended since 5.0 since it makes upgrading a challenge, and this continues in 6.0.  There really shouldn’t be a need to modify the master page or any core web file, but if you have a specific situation please feel free to post it and we can see if you have an alternative.
     
    For Header/Footer Fragments… correct, there is no specific header or footer fragments anymore and the headers and footers are editable in terms of adding/removing widgets.  What is important to note though is even in 5.x Header Fragments were still a type of widget, they just were specifically meant for the header region and could only be added via file based configuration.  We simply enhanced that process by making them exchangeable via the UI and editable in the widget studio.   You can still create widgets with the intention to only use them in the header, we simply are providing the opportunity for any widget to be used in the header or footer and styled according to the region it lives in.
     
     
    Hope this all helps
    Patrick Mason
    Development Lead- Extensibility
    o: 214.420.1329
    telligent.com
     
    From: Will Yip [mailto:bounce-willyip@communities.telligent.com]
    Sent: Friday, September 23, 2011 1:12 PM
    To: discussion_evolution@communities.telligent.com
    Subject: [Telligent Evolution Platform Discussion] 6.0 Theme
     

    Is there any documentation and best practice on how to create a 6.0 theme?  I understand that the way that we create themes are much different from 5.x.  Before, we used to copy the "fiji" theme in the physical web directory and start from there.  In 6.0, there is no fiji directory anymore.  We used to be able to make changes to *.master pages.  In addition, we used to defined custom-created header fragments and footer fragments in theme.config for a specific theme.  Understand that in 6.0, we can create widgets for headers and footers as well.  Is creating widgets the only way?

  • There are 2 default footer fragments.  One has the Telligent logo and the other is the User Info Popup.  How do I remove the default footer fragments because they seem to be locked.  I am the admin of the site.

  • These are defined at the site level, you'll need to edit the footer of a site-level page to remove the widgets.

    Child theme types (groups, blogs) inherit their headers/footers by default.  Inheritance of headers/footers in group and blog themes can be modified via the configuration of individual groups/blogs themes within the control panel.

  • Patrick,

      Question regarding your last paragraph above. Those this mean that in 6.X a widget does NOT need to inherit ExternallyImplementedHeaderFragmentBase and ExternallyImplementedFooterFragmentBase to be respectively placed in the header and footer.

    Thanks,

    Jean

  • Correct..and this bleeds over into your question here: telligent.com/.../1356941.aspx

    If you still needed to use the ASCX based widgets just use ExternallyImplementedContentFragmentBase or the configurable version, especially if you are not using a legacy file based theme.  New themes don't use Header and Footer fragments anymore they are all content fragments.

    That being said while ASCX based widgets are supported, we really don't recommend using them unless it is absolutely necessary.  You lose functionality/flexibility that comes with the widget studio.

  • Thank you much.