Help and contact

Our Core library in Storybook has all the documentation you need for all components and foundations.

You can post questions about anything Builders-related in the #team-builders Slack channel. Before posting, consider checking whether others have had the same problem before – try searching in the channel history.

If you could use more discussion about your challenge than Slack provides, we suggest you book a spot at the next Builders Forum! Any conundrum is welcome.

We post breaking changes to Core in the #team-builders Slack channel. The changes in our most recent release will be pinned there, so it's easy to find.

You can also view the release notes for each component in Storybook.

If you think that other teams might benefit from your component, then it probably belongs in Core! Please reach out to us on Slack, so we can discuss it.

We prioritise and fix major bugs as soon as they appear. For other requests or minor bugs, we try to create GitHub issues for these and fix them when we have time.

If your request is urgent for your project, please create a pull request to Builders core. We depend on teams contributing. When you do, please make changes to Builders Core instead of overwriting the CSS. The CSS might change in the future, resulting in overwriting not working anymore. Also, other teams may benefit from your changes.

Also, we are getting help from this year's summer students setting up an issue app to help you report and follow issues. More to come!

First, check that you're using the latest version of the components in your design tool, and that your application is up to date as well.

If there's still a discrepancy, there might be something wrong on our part. Please let us know by messaging us in the #team-builders Slack channel, and we'll try to sort it out.

Our platform is a "website builder as a service", offering everything you need to build and maintain a website, including:

• Our content management system, Content Studio
• An asset server that hosts images and illustrations
• 30 building blocks with which to build pages
• Content types and structured data
• Global elements such as navigation and search functionality
• Micro frontends that allow us to embed applications to pages built in the CMS (and more)

Updates to Parts and Content Studio will be posted in the #builders-platform Slack channel.

First, we update the gjensidige.builders test environment so that we can test our changes and discover bugs. When we consider the changes were successful, the new version will be released to your test environment, so that you may test them on your solutions. If you do not alert us of errors, the changes will be released to all production environments a few days later.

Team Builders have created a so-called "starter pack" with 31 parts.

These parts are based on what we had before and the challenges editors faced there. The starter pack covers the most basic editorial and user needs, such as different types of headers, CTAs, link lists, tables, text snippets, article content and more.

This starter pack is our first edition, so to speak, which will always be iterated, improved and possibly expanded so that it covers needs that are shared across all of Gjensidige.

Our "starter pack" is based on basic editorial needs and the main user tasks on gjensidige.no, gjensidige.se, gjensidige.dk and gjensidige.com.

When developed, parts are first tested on gjensidige.builders for a while before they are available on the Gjensidige sites. We ensure universal design and code quality, follow best practices for UX/UI, and of course iterate and improve the parts continuously.

Qualitative tests put the combination of design, content, code quality, information architecture and much more to the test. This means parts in themselves cannot be tested per se – their flaws need to be identified during tests of actual user journeys with actual content, either with prototypes or on a finished website.

Therefore, parts are tested every time the websites that consist of them are tested. We depend on feedback from the teams, editors and customers who use them to improve them.

See summaries from the tests run while developing new gjensidige.no

Oh no! This sometimes happens, and we don't always know why. These are the most common:

• A 504 message means Content Studio has lost connection to the React server, meaning it's unable to display the frontend of the parts. You can still work "blindly" and not lose your work.
• A 502 message means Content Studio has lost connection to the CDN server. You will not be able to work as usual.
• A 403 message means you do not have access. You can request access from the editor responsible for the website.

To report an error, send us a message in the #builders-platform Slack channel, and we'll look into it as soon as we can. Feel free to notify us by starting your message with @builders. Please include the type of error message you're getting – a screenshot could sometimes be valuable as well.

If you have not filled out all required fields for a part in Content Studio, the part will not preview or show up.

If your custom part doesn't show up, please check that the keys fetching the app are correct.

Yes! Some editors like to keep work in progress within the test environment, and we get that. When you're ready to make your changes in production, you should of course not have to build it from scratch. We have documented export and import through XP's Data Toolbox in GitHub.

While the content type Shortcut inside Content Studio may be used to create redirects, we recommend using the Rewrite Manager app inside XP. You can read all about how it's used and why we prefer it to shortcuts in our documentation of Rewrite Manager.

Our platform is a "website builder as a service", offering everything you need to build and maintain a website, including:

• Our content management system, Content Studio
• An asset server that hosts images and illustrations
• 30 building blocks with which to build pages
• Content types and structured data
• Global elements such as navigation and search functionality
• Micro frontends that allow us to embed applications to pages built in the CMS (and more)

Updates to Parts and Content Studio will be posted in the #builders-platform Slack channel.

First, we update the gjensidige.builders test environment so that we can test our changes and discover bugs. When we consider the changes were successful, the new version will be released to your test environment, so that you may test them on your solutions. If you do not alert us of errors, the changes will be released to all production environments a few days later.

Team Builders have created a so-called "starter pack" with 31 parts.

These parts are based on what we had before and the challenges editors faced there. The starter pack covers the most basic editorial and user needs, such as different types of headers, CTAs, link lists, tables, text snippets, article content and more.

This starter pack is our first edition, so to speak, which will always be iterated, improved and possibly expanded so that it covers needs that are shared across all of Gjensidige.

Our "starter pack" is based on basic editorial needs and the main user tasks on gjensidige.no, gjensidige.se, gjensidige.dk and gjensidige.com.

When developed, parts are first tested on gjensidige.builders for a while before they are available on the Gjensidige sites. We ensure universal design and code quality, follow best practices for UX/UI, and of course iterate and improve the parts continuously.

Qualitative tests put the combination of design, content, code quality, information architecture and much more to the test. This means parts in themselves cannot be tested per se – their flaws need to be identified during tests of actual user journeys with actual content, either with prototypes or on a finished website.

Therefore, parts are tested every time the websites that consist of them are tested. We depend on feedback from the teams, editors and customers who use them to improve them.

See summaries from the tests run while developing new gjensidige.no

Oh no! This sometimes happens, and we don't always know why. These are the most common:

• A 504 message means Content Studio has lost connection to the React server, meaning it's unable to display the frontend of the parts. You can still work "blindly" and not lose your work.
• A 502 message means Content Studio has lost connection to the CDN server. You will not be able to work as usual.
• A 403 message means you do not have access. You can request access from the editor responsible for the website.

To report an error, send us a message in the #builders-platform Slack channel, and we'll look into it as soon as we can. Feel free to notify us by starting your message with @builders. Please include the type of error message you're getting – a screenshot could sometimes be valuable as well.

If you have not filled out all required fields for a part in Content Studio, the part will not preview or show up.

If your custom part doesn't show up, please check that the keys fetching the app are correct.

Yes! Some editors like to keep work in progress within the test environment, and we get that. When you're ready to make your changes in production, you should of course not have to build it from scratch. We have documented export and import through XP's Data Toolbox in GitHub.

While the content type Shortcut inside Content Studio may be used to create redirects, we recommend using the Rewrite Manager app inside XP. You can read all about how it's used and why we prefer it to shortcuts in our documentation of Rewrite Manager.