Migrating KX13 site with inline editable areas in rich text

Hey everyone,

I'm estimating an upgrade of KX13 website that apparently was built with heavy use of inline editable areas in rich text.

Site has got ~4.000 pages, where at least a third is using this approach to enrich rich text content with some widgets.

I wonder if anyone here has experience migrating things like that, and if there are any better ideas than trying to replicate the same approach in XbyK (Froala plugin and a custom rendering of those)?

Tags:
Migration / upgrade Page Builder

Answers

Hi Dmitry,

We have been migrating sites with 1000s of pages too. first it was to K13 MVC and now it is XbyK with the same architecture that we used for K13.

In my opinion the thing you have to consider is a balance between content modelling best practice, marketing team satisfaction and authoring usability.

  • the client budget and project timeline to allow the review all the pages after the migration. The more change you make, the more time it will take to ensure the migration was successful
  • the client author's appetite to break the content down into numerous fragments and place them in the content hub. We have taken over the management of K13 and now XbyK from several partners after they stopped being Kentico developers. Our customers have given us the feed back that the templates driven by single fields in the content tab did not give them the marketing flexibility and variability that they need to keep the brand fresh for the long term.
  • Time to produce the content. I am not a developer, I am what you would call an expert Kentico user (although I know enough code to be dangerous). What I found working on K13 and now XbyK sites (that we inherited) that break everything down into its parts and place that content into the content hub as separate objects is that authoring takes between 6 and 10 times more time. You need to create, save and publish all the component parts. Before the migration to XbyK we asked our clients if they were happy to place all their rich text into the hub. The answer was a resounding no. They are happy to place it into the hub if it is reused or likely to be reused - i.e. calls to action, advertising banners, multisite content. If not they want to author it in place on the site where it needs to be placed. Otherwise they want to just prepare their unique page content on the page that it is to appear.

    So we support a hybrid approach - place rich text into the content hub if it makes sense - calls to action, notification popups, people profiles, testimonials, customer reviews, locations, all product base information.
    Place rich text directly onto the page builder otherwise - product marketing descriptions, news article, information pages
  • To support this we built the following hierachy in our accelerator to provide the ulitmate flexibility for clients and ease of low cost project migration.
    Page templates all with a Subheader, Body, Secondary and Tertiary Section areas in fixed locations on the templates depending on the layout; 1, 2 or 3 column layouts, landing page, product, event and popup. All these templates have these editable section areas.
  • Sections with columns (1-4) with brand aligned classname configuration dropdowns (bg color, margins, padding, gutters, shapes, shadows, accents) so that site styling patterns can be maintained but with flexibility of authors to create marketing interest in different contexts.
  • Custom froala widget rich text that can be placed in any of the section columns. We pinned the editing bar and added a library of html dropin elements (using the froala star menu) for the clients to use (e.g. Block quotes, table markup, Feature text sizes)
  • Content hub content type we are calling a Content chunk for reusable rich text (unfortunately Froala is not available for use in the content hub so it means you have to configure 2 visual editors and train on 2 visual editors
  • Custom "Content chunk" widget for placing the reused/reusable content chunks into pages.
  • Page chunk widget - for placing entire page builder areas authored on pages in the tree into other pages (e.g. complex laid out multisection banners with multiple components) into the page

Then the approach you take for migration to this architecture scales with the migration budget.

  • Low budget projects we import 100% into single rich text fields. The page QC review splits content into sections to support image and video widgets only. This allowed us to do 1000 pages in a 6 week delivery timeframe - we have done this project half a dozen times with success.

  • Medium budget projects we imported 100% into single rich text fields and then improved layout with AI computer use. Splitting content into sections to achieve complex multisection pages with background /column treatments and markup. We also improve content hygiene and accessibility (heading hierachies, hyperlink markup, table markup) using computer use as we go. The AI produces a customer report of all the changes that were made for their approval. Then human review for quality of every page.

    • Medium budget projects may have a couple of content types in the content hub with the content placed on the page as a part of the migration using the correct widgets in the correct place amongst other unique content on the page. Why do we use content hub display widgets instead of a custom page content type? We are trying to keep the number of content types down. If we made a specific content type for every page layout type then we have to maintain all those content types for 3-7 years depending on the client and now with monthly Kentico refreshes. We are trying to maintain reasonable costs for high flexibility and functionality long term.
    • We produce widgets for custom forms or tabular data layouts from integrated systems. These can sit amongst unique rich text for marketing.
    • We produce page builder page layouts for pages like news and news month and save these as custom for the project.
  • If I ever land a high budget project then I would do the following.

    • Use frontier AI to assist in the audit of what content across the current site/s is conserved.
    • Plan for and develop content hub content types for all the reused, reusable content using best practice content model.
    • That content can be flagged and imported into content hub (as the appropriate content types) and placed on the page as a part of the migration using the correct widgets in the correct place amongst other unique content on the page.
    • We may include custom page content types for high value transformation but we havent found a project where
    • Use computer use of the Kentico GUI to close any gaps. We are finding if the migration tools are insufficient for complex migraiton patterns where content location changes are complex or complex widget configuration is required. In this case we are successfully using AI computer use can resolve issues extremely well including widget configuration in the page builder. The risk is acceptable in development environments with marketing content sites, in fact the work I believe can improve the performance of the site so we leave training on for this work.
    • The rest... the unique page text, never reused. I would still put in the page builder in rich text widgets above and below other widgets on the page so that the client team have the flexibility to improve the marketing outcomes long term with this content without being locked down in a rigid layout.

    • Hope that thinking helps.
      Dani

Hi Dani,

Thanks for taking some time to write this answer, though I was asking a very specific question, not general migration guidance here - what can we do with inline editable areas in rich text apart from migrating as-is?

To response this discussion, you have to login first.