Re-ordering a page based on A/B testing using something like optimizeĪs you can probably appreciate, these are all pretty understandable needs.this is the power of the grid editor! If you are still struggling to wonder what sort of flexibility a client might ask for, then have a skim of the list below: They no longer need to rely on a developer. Now imagine a scenario where a content editor is empowered to make the layout changes. When you tell someone that they won't be able to get what they want for days/weeks/months, they get annoyed. These changes typically have a timeframe. Most changes are typically required due to some business need, like a new campaign. This process can understandably cause a lot of frustration for a client. this means the timeframe from a client asking for a simple layout change to when that change is available in production can take weeks. Like most teams, I work in sprints where multiple changes will be bundled together. Finally, the change needs to be released into production. A round of testing and sign off would need to happen. If a client decided they want to change the layout of a document type, typically they would need to schedule in a developer, or designer to make the required changes. As hard as you try on a new build, it's impossible to forward guess every permutation and content requirement a client might have. These pre-set layouts were cumbersome to change. This process usually involves an agreement with the client, a designer, and a developer. The structure of the layout was agreed upon at some stage at the start of the project. Traditionally in a CMS, you would define a template that had a very pre-set layout. If something doesn't work well in one, it is unlikely to work well in another. The reason I mention it is that most CMS systems have more similarities than differences. You are reading this for some Umbraco love, and you probably don't care about Episerver. How do you delete a macro when it's used throughout your website (in rich-content areas) without wasting a lot of time? Macros caused so much trouble for Episerver that in version 7 they deprecated them completely and moved towards a content area/block architecture. These issues have mainly around maintenance and upgrades. In most CMS systems where they have been implemented, Macros have caused headaches for software engineers. Traditionally, Umbraco has provided some form of flexible layout via macros. NET CMS systems, like Sitecore or Episerver then you will be very familiar with creating flexible layouts. If this sounds like something you might want and your clients will love, then read on. The grid layout property provides a new level of power for content editors. ![]() Recently, Umbraco introduced a really cool feature called the grid layout editor. In this tutorial, you will learn how you can build truly flexible layouts within Umbraco that will empower your content editors to take their content to the next level.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |