FAQs
Please find below frequently asked questions.
GENERAL
We onboarded colleagues with no knowledge with just one training session and they got used to the process of optimizing super fast. In the very beginning it took ~30mins to work through certain pages. Now everyone needs ~10mins per page.
When you setup the process based on the Excel template it is only about working through all pages. Some types are easier to fix, like product pages, some have more variants in content and need a bit more time.
If you calculate with 15-20mins per page in average, you should get a reasonable total number.
You can estimate around 1.000 pages (includes navigation, microcopy, old content, many news and blogs) per website in average.
We will migrate the DEVELOP websites to Contentstack. This project will be kicked off in FY25.
Yes, we are already working on a new version that reflects the new technology. This will be shared via the DPO/GDPR Team to your local GDPR contacts.
You can use any available element in Contentstack to build the page. There is no option to choose from different designs. In the future, due to the headless CMS, we can define new visual elements for landing pages or a complete different design if need be.
The login is here:
https://eu-app.contentstack.comYou can find Storybook here:
https://konicaminolta-storybook.vercel.appStorybook is a tool for developers to check improvements made to the code. For editors it is a nice overview of all elements available in Contentstack and how they behave. You can take a look here:
https://konicaminolta-storybook.vercel.app
We will inform as soon as new items are available.You are already here:
https://contentstack-guide.konicaminolta.euIn the future you can set them in Contentstack and also export the full list. Prior to the launch, please send all redirects to Active Elements so they can be set on server side.
We only offer a separate/new navigation that can be used on landing pages. In the new design, the main navigation can drill down to the third level and should cover existing sub-navigations.
MIGRATION - Best practices
Yes, you should set up your own Excel and take the template as a start.
It will be empty in the beginning. It doesn't take too long to add the pages, and it gives you the opportunity to rethink if all the content is still needed. Here are several ways to start populating the Excel sheet:
- Collect the URLs from the current menu of the live site (recommended)
- Collect from Kentico backend
- Walk through all Contentstack entries
- Kentico HTML sitemap
- According to defined structure
Unfortunately Kentico does not provide a way to export a complete list. We can use a crawler to get all URLs, but that list will be unsorted and furthermore, it will not cover landing pages or any other pages outside the main page tree. So you should not rely on that list and set up the list manually. Thanks to Martin Elias (BCZ) you can also follow these steps using Ryte:
- At https://en.ryte.com/ use the Data Explorer (beta) / URLs / All pages agenda. By exporting here, you will get a table with about 1000+ page URLs.
- In Excel, I disassembled the column (URL) into individual parts via the command Data / Text into columns, see the image below.
Then it is enough to view the Hardware / Office section using filters, for example, and you will get all the URLs for all office machines. You can filter anything anyway, or view the entire web structure.
Until the day you decide to switch your new website live.
Yes, there will be no further migration. Ideally, keep the timeframe with double-efforts in both systems as short as possible.
Yes, this is part of the optimization. We highly recommend optimizing content, remove content that is outdated, but keep the number of new content low. Just because this takes a lot of time and you need to maintain two systems for a longer period of time.
This is currently under evaluation, and we will give a clear answer and guidance soon!
All information for a product page is merged into that one product entry. So each product page has it’s own “Functionalities” content, it is not shared. The formerly re-used content is now available separate in each product, it is not duplicated.
No, not at the moment. We recommend to copy an existing product page and adapt it, so it already has the necessary elements in the page. Product pages will be available for translation anyway by BEU, but same is true for any other page of course.
No, it was not possible to migrate this information. It needs to be re-set manually.
It would be helpful if you need any redirections later on. It is also probably good for you to have a complete list of pages, too. The Excel chart is mainly a tool for you to keep track of the migration process. So if you don't enter new pages there nothing will break. But when it comes to setting up redirections for the old URLs it will be helpful to have all pages in the Excel chart.
Technically Kentico has a completey different code base, so there was no 1:1 migration possible. In fact, we are surprised how good the automated migration works and all text, images and content is migrated and editable.
Yes, we use the same Canto instance. Both CMS are accessing the same content, whatever you change in either or CMS, it will be available in the other.
Currently, no carousel element is available apart from an image gallery. We are looking into making it available soon.
We will cover content distribution and translation in future sessions separately. For the moment, please get in touch with Tino. BEU needs to actively share/make the entries available.
Please drop us an email in this case, that shouldn’t be the case.
Excel is only for you to keep track on your pages and maybe to generate redirects after the launch. What you set in Contentstack is what is used.
CONTENTSTACK UI - General
They are always sorted alphabetically. But there is a search field at the top, so you don't need to scroll.
Please check if the entry was published to "staging" environment. If it is already published, please save your changes and reload the full browser tab (contentstack-url, not only the preview).
Please check if the entry was published to "staging" environment. If it is already published, please save your changes and reload the full browser tab (contentstack-url, not only the preview).
Please check if the latest version of your entry was published to "production" environment.
You can upload them directly where you need them. All images just need to be uploaded in the best available resolution (at least 1300px width) and don’t care about the size – Canto takes care to deliver a compressed webp format in the right size automatically!
Some thumbnails, eg in cards, have a landscape aspect ratio, make sure to not utilize a portrait mode image. Always check if it fits, including alignment options you have in Contentstack.
Any source format should work
You can share an entry when it is published to “staging”. This will show the “Edit” buttons in the frontend, which might not be nice to share externally. You can also publish to “production” and use the “Hide Page” feature.
Yes, we offer a dark mode as well. It will uncover a lot of images that use white background and should be transparent. We haven't evaluated how much additional work it is to fix all images to fit both modes though.
Based on the system setting or a browser plugin you will experience the dark mode of the website. We added the image optimisation as a task to the Excel sheet.
Update: The existing Chrome browser addon doesn't really show the correct dark mode, please change your system settings for now.
No, these are only the number/identifier of the block element. Each Columnblock has ID 12, each Card Grid ID 5, ... Unfortunately, we can't hide them.
Please let us know, this seems to be a problem with migration, the path is not set correctly. We have to check that.
WORKING WITH CONTENTSTACK - Entries
The name at the top is only for INTERNAL purposes. It will not determine the URL.
In the following types it is defining the content of the page (XXXX). In all other types it only serves for reference information when adding a card element in another page referencing to this page.
It is not part of the page content for the following types (XXXXX), it only serves for reference information when adding a card element in another page referencing to this page.
Not automatically at the moment, we had the same idea. We will look into this and see if we can enable it.
Yes, all elements in a page have the EDIT button. Some of them might not be editable for you (like the logo in the top left) but it will still bring you to the item in Contentstack.
PRO TIP: If the link to the item you want to edit doesn’t work correctly - just reload the page!
This is up you us and should fit the image in the best possible way. This is mostly to overcome the issue with "text on image is not readable" like it is now.
Yes, you can switch the preview. There is a button in the top right to toggle between mobile/tablet/desktop.
You can upload them directly where you need them.
It is not part of the column element, but in the Marketo element you can add text left or right to the form to achieve this.
No, not yet. If this will be a requirement we can discuss in the Core Team.
Yes, exactly.
Only on the "sending" page. The receiving page just pulls the information from the card and displays as a card.
Yes, we do have the option to show "latest news" e.g. on the start page, same works for blogs, events and products.
The "Card Grid" block is flexible and allows you to adjust everything. The "Reference" block is set up by simply selecting the elements (like blog entries), the rest is done automatically.
Yes, it is. When you select the brochure in a card you get the thumbnail automatically.
Will each NOC work in its own Excel sheet? Or there will be tabs?
The images can be aligned left, right, top, bottom, center. That should fix the issue with cropped of heads/faces, If not, you need to change the image in the "card" section in the page that you want to reference to.
The former "Advanced Marketo form" widget and the standard form widget have been merged. All information set in Marketo (thank you message or follow-up URL) are still valid and will be executed. Unless you overwrite it in Contentstack.
The title in the header image/slider is h1, if you don't use one you can set h1 in the RTE yourself. Other than that you can choose in RTE the h-definition.
They are actual pages/entries that can be modified.
If you create a new page you need to type the URL, but there is a feature that supports you, called “parent page”. Select the parent page and enter the “child identifier” which will automatically build the URL. Make sure to not use special characters!
You can press "Send without references", because they did not change.
Some pages reference other elements (link to them). You see in the window if there are references - if not you can simply press "Send without references".
Overview pages (for products, news, blogs, etc.) are based on Algolia. We disable Algolia for the moment because it costs money whenever the index is rebuild, which happens with every change on a product page for example. We will enable it once you optimized all products, news, blogs and events.
For now you can use the following link adjustment 123-456-7890 - we will try to make this available in the UI as well.
Doesn't work with hero image slider, or when no header image is available - use the chance to fill the fields with optimized information
No, it's not. Currently we are evaluating the K+C design of using multiple columns for content (like images spanning over 2-3 columns). More info to follow!
We will pull the "alt text" from Canto and you can overwrite it/localize it when adding the image. Currently it doesn't show the Canto alt text (e.g. taken from stock images automatically) yet, this will be fixed.
No, we optimized spacing and margins in the design (frontend). In Contentstack we should only enter content, the frontend rendering is taking care of the design. If any spacing and margin needs to be adjusted, we can discuss for overall optimization.
You can add them in an RTE field by using the Embed Link from YouTube (click “share” on a YouTube video to get the link)
Currently, it is not available in the "image picker", an update will be deployed soon. For now you can use Kentico to get the URL of a PDF and implement the direct link in Contentstack.
Yes, you can choose from three different background colors when using the “flat” variant. Alternating the colours only works when you setup different accordions.
No, font color is only black to meet accessibility standards.
No, currently this is not possible. You need to recreate the content in another element.
The content itself comes from Marketo, I am not sure if we can manage this via the frontend design. We also need to check if this would be legally allowed.
You can simply select the text in the RTE and add a link via the respective button. It can be external via URL or you can select an existing entry/page to link to.You can simply select the text in the RTE and add a link via the respective button. It can be external via URL or you can select an existing entry/page to link to.
Yes, at the moment it is not possible. We will work on an easier solution to select PDFs or other entries.
Create a card element and use the "business area" variant as an alternative. A clickable image itself is currently not available.
If entries are directly linked to another element (navigation/parent page) Contentstack checks if all linked elements are published. If not, it offers to "Send with references" so all connected pages will be published together. Usually, you should be fine by sending "without reference".
We are not forcing upper case letters anywhere anymore. It is not readable nicely. If you still see them, they have been migrated this way because you typed it in upper-case in Kentico. Please use upper and lower case consistently.
For accessibility reasons we only have black font available on different background colours. Only within column-elements we allow to center text. Headlines will never be centered by design.
No, by design it is left aligned. We are checking to have the CTA buttons in the navigation right aligned, which would make the UX easier.
You can't nest an accordion in a column any longer, please put them below each other.
This is not necessary anymore and the website navigation and structure will be handled via each pages URL. We also added a feature called "parent page" which will help to setup the structure. Additional session how to setup the structure will follow.
Not all elements are allowed everywhere. In some sections only a few types are allowed and therefore selectable.
Please don't use images with text on it. Please let Contentstack put the text onto it, this is much better from the SEO perspective. You can align the image to the top, right, center and so on, that should solve the problems with most images.
This number is the ID from Kentico. It can be deleted after migration.
These texts are stored as Microcopy Entries ("Product links: ..."). We will check if we can add edit-buttons for these texts in the preview.