Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
Sitefinity uses Telerik’s RadEditor to bring a Word-like text editing experience to the web browser. RadEditor allows content editors to easily style and format text . However, RadEditor also contains an HTML mode that can be used to directly inject HTML into the content.
Because HTML mode allows raw HTML to be injected into the content, this feature can be used by savvy editors to create very advanced content layouts. However, in my opinion, it is inappropriate to toggle into RadEditor’s HTML mode and create HTML formatting. This should never be done in Sitefinity. Not even by highly technical editors. In fact, RadEditor’s HTML mode fundamentally defeats the purpose of having a WCMS.
To understand why I think this is a bad practice we need re-visit what life was like before web content management systems. Many years ago, webmasters created web content using raw HTML and then published this content using FTP.
This had several disadvantages:
These old problems are resurrected when editors resort to injecting raw HTML into a WCMS.
There are plenty of one-off examples where toggling into HTML mode seems to make short-term sense. Heck, I do it too. However, frequent use of HTML mode represents a fundamental problem that should be addressed through…
Unfortunately, all of these solutions require content editors to contact others (developers, designers, Telerik) to accomplish their immediate content management objective, thus interrupting their workflow. This might be appropriate if substantial new functionality is required, but often the editor’s objective is much less substantial (for example, adding a new column to a page).
We want content editors to feel empowered to do their job. Furthermore, developers or designers shouldn’t be required to accomplish trivial tasks (for example, adding a new column to a page).
In my experience, people often use RadEditor’s HTML mode for page-specific layout tweaks. For example, adding a new 3-column layout:
This looks like a simple task, but accomplishing this quickly becomes complex. Tables could be used to create this layout in RadEditor, but using tables for layout is frowned upon. To avoid tables we need to inject raw HTML into RadEditor or create a brand new template. Either path becomes a hassle.
To address this challenge, Sitefinity 4.0 includes a new Layout Editor. The Layout Editor makes this task effortless by allowing editors to simply drag & drop a new 3-column layout onto the page:
Once in place, widgets can be placed (just like normal) into any of these new placeholders. Furthermore, the layout toolbox is fully extensible. This combines the best of both worlds.
To use Sitefinity 4.0’s new layout editor download the Sitefinity 4.0 CTP.
1. Create a new Sitefinity page.
2. Click the Layout button
3. Drag & drop new layouts.
4. When finished, toggle back into Content mode
As always, we welcome your feedback in the Sitefinity 4.0 Forums
View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.