Improvements in content items preview
This is a feedback we received from one of the customers. He's looking for an improved version of content items preview. Based on my understanding, the current preview of content items is not sufficient for his needs (Configuring preview of content items).
"I hope this can help you serve customers with requirements like mine.
I signed up to test your headless CMS, as I'm looking for an alternative to GatherContent — a product I'm very familiar with.
The reason I didn't continue with my Kentico account was simply this: I couldn't preview a 'full, complete HTML page, including all content' within your service. Or at least I couldn't find out how to.
I realise it's easy enough to do this if I was hosting my own site, using your API. This is your core offering. But I'm often modelling content a long time before there's a production (or even UAT) environment accessible for me to plumb content into.
I need to preview all material, in full, in context, in your cloud.
What I'm looking for is simply a 'vanilla' rendition of all template/object fields, with basic CSS styling only, so my authors (and importantly, my clients legal teams) can "view each page" in full, at a specific URL, long before the clients' site is established.
It is important, specifically, that any repeating/linked content object(s) are rendered inline (in full, on the same page — rather than each related content block/object requiring a previewer to visit individual records).
I generally deal with highly structured content, that requires many individual fields of varying format. Many 'pages' also feature content/fields from related content objects. This is typically difficult to 'preview', in totality, till the content has been integrated with front-end templates.
By rendering a page as it might appear in full, in a production environment, any content stakeholder can get a clear picture of their material, without the need to use your web app interface, or visit multiple addresses. It's important for many of my stakeholders to read all fields of a particular content object, including metadata, taxonomy and summary content that may appear in specific contexts such as search, mobile only, or in list views etc.
This is what I failed to be able to do with your proxy CMS, and it's why I never returned to my demo after testing it out.
In the end, I opted to use WordPress, with a custom post type plugin (to configure all the content modelling and relationships), then a rudimentary, largely un-styled front-end template to render 'full pages' including any meta, and linked/related/repeating objects. A simple index/sitemap was all that was needed to navigate the structure.
This way a legal team was able to review each page of their prospective site, in full, signing off material before it ever made it to UAT.
On a related topic, I also want to add custom HTML tags (https://developer.mozilla.org/en-US/docs/Web/Web_Components/Custom_Elements) into the rich text field, in code edit mode, and not have them stripped. This will become increasingly important."