We really wanted to focus on the Content Editor experience and how we as Umbraco developers could make their lives easier. Some of the things we presented were out of the box in Umbraco and some were packages that enhance the Content Editor experience.
1 of 35
Download to read offline
More Related Content
Umbraco Packages and Helping Content Editors - uWestFest '16
4. Improve the
Content Editors
Experience
Its the little things
Add property descriptions
DocTypes inheritance
Use tabs wisely
Pick icons that make sense
Organize the Media
Use the dictionary
RTE stylesheets and toolbar
Customize the List Views
21. Data Sources:
SQL, XML, JSON,
.NET Classes,
Enums, Examine
And thats not all!
Custom Label
Rendering using
Macros
22. More Property
Editors to Try:
Archetype
u7 Grid DataType
Content Picker with Preview
Extended Media Picker
UrlPicker
MultiUrlPicker
Angular Maps
Switcher
Vorto
26. More Packages
to Help You:
Core Value Converters
uSync
Hybrid Framework
Ditto
LINQ to Examine
UmbracoFileSystemProvider.Azure
MemberListView for Umbraco 7
UnVersion
TheDashboard
34. Where to Learn
and Get Help:
Learn
Our.Umbraco.org
uHangouts on YouTube
Conference and Festival
Videos
Umbraco.tv
Ask
Our.Umbraco.org
Twitter
Slack
#3: History:
Building Umbraco sites since 2009 (v4.0.3)
We have seen a lot of Umbraco implementations (inherited several)
We have been advisors on several implementations
The Back-Office setup affects clients perception of the project and Umbraco
#5: The build process is long and its easy to cut corners to get things done, we do it all the time.
But after youve finished the site and its the Content Editors time to take over, its the little things you do that can end up creating a great user experience.
#6: Being consistent with descriptions on your properties on docTypes goes a long way.
Its like theres always someone there, helping out.
Instead of it just saying image it could have crop sizes, image dimensions.
#7: Use docType inheritance wisely to make sure the correct properties are shared.
Avoid showing unnecessary fields or tabs.
Compositions help with this.
Un-check allowed docTypes for items only created once like Blog or Search Results
#8: Avoid having all the properties in one tab.
Avoid having too many unnecessary tabs.
#9: ** show of hands ** who here has seen or made a site with all folders for icons? Yep we have too and were trying to make sure to pick icons that make sense
Makes it easier to see at a glance where you are in the content tree.
#10: Its common in our experience to see all the media just dumped into the root.
You can start them off on the right foot by setting up folders.
Makes it easier for content editors to find media
#11: Common words or phrases can be made into dictionary items so if down the road they need to be changed you can easily site-wide.
The word Submit is a good example. My friend Eric was working on a European project making web forms that were getting sent out to 6 different European countries. His client made him change Submit to something else because it could be offensive like being submissive
#12: Add every kind of style you can think of to the RTE formats dropdown.
H1 - H6, blockquotes, larger text, smaller text, for flexibility
Bring basic styling into the RTE, fonts, titles, line-spacing, background colors.
Enable all the icons you need from the RTE data type.
#13: List views can help keep the content tree tidy
But you can edit the properties shown on them
#14: Dashboard--
If you want to be really cool make custom dashboards with instructions or how-to videos. Here we linked to screencasts.
Bookshelf --
A package you can install to keep manuals and in-depth tutorials and help sections.
Inline Help --
A package we created to keep in-depth help in context.
#16: Sent out a tweet to the Umbraco community and got a great response