Symphony 2.3 features a significantly improved UI over it's predecessors due to the hard work of the UX Working Group and contributions by other dedicated members of the Symphony community. In making these changes, there's been a number of minor updates to the HTML, CSS and JS throughout the backend. The purpose of this guide is to help document some of these new features, and outline differences that extension developers can implement while updating their extension for 2.3. Eventually a dedicated style guide for Symphony will be available, but this will fill the void for the meantime.
-
Something about Navigation
-
Something about Breadcrumbs
In the past adding a With Selected select box to the bottom of your page was done by using the Widget::Select
and Widget::Input
functions. This is no longer required with the new Widget::Apply
function that takes a single parameter, an array of options.
-
Symphony now utilises
@media-queries
to provide an optimised layout for content editors when the screen size dips below 700px. -
Something about the
.tabs
styling/structure expected
Columns need a wrapping element (.columns
) and multiple columns (.column
). Additionally, the wrapper has to declare how many columns it should display per row. Symphony knows the following classes:
.two
.three
.four
Example:
<fieldset class="two columns">
<label class="column">…</label>
<label class="column">…</label>
</fieldset>
The two column mode knows a special setup known from the publish area: a primary and a secondary column.
Example:
<fieldset class="two columns">
<label class="primary column">…</label>
<label class="secondary column">…</label>
</fieldset>
The old classes .group
and .compact
have been deprecated, see symphony.legacy.css
.
- The Duplicator plugin
- Something about the new Drawer plugin
- Something about the new Notify plugin
If you want to have your Duplicators styled even with JavaScript disabled, wrap it with
<div class="frame" />
(which will be added on the fly, if you don't add it).