Tibi Editor Workflows
This page maps common editor tasks to the WordPress content type, block, frontend behavior, and developer owner area. It is intentionally practical: use it when an editor asks where content lives or what a change will affect.
Last modified: July 9, 2026
Task Guides
For step-by-step instructions, start with Editor Guides.
Create a Help page
Step-by-step publishing guide for Help pages.Add a FAQ
Reusable FAQ posts and page-level FAQ accordions.Add a brochure
Brochure/material order items, files, images, and language options.Update form text
Thank-you messages for custom forms.Test Help search
Verify Help pages and FAQs are findable.Help Content
| Editor task | Where to edit | Important effect |
|---|---|---|
| Create or edit a help article | Hjelpesider (tibi-help) |
Public URL uses /hjelp/...; pages are hierarchical and ordered with parent/menu order. |
| Create or edit a help FAQ | Ofte stilte spørsmål (tibi-faq) |
Used by the new Help experience and can be filtered by Hjelpekategorier. |
| Organize help content | Hjelpekategorier (help-category) |
Categories support sort order. They affect filters and grouping in the Help experience. |
| Edit older user guides | Brukerveiledninger |
Used by the legacy/global search allowlist and old help/user guide surfaces. |
Editor checks before publishing:
- Use clear titles; title text is used in search suggestions and result cards.
- Add a short excerpt when the result card or listing needs a useful summary.
- Assign the correct help category before publishing.
- Check both the page itself and the Help search result after publishing.
Developer references:
packages/wordpress/plugins/tibi-core/inc/post-types/configurations.phppackages/wordpress/plugins/tibi-core/inc/taxonomies.phppackages/wordpress/plugins/tibi-block-library/src/help-search/packages/wordpress/themes/tibi/inc/templating.php
Forms
| Editor task | Where to edit | Important effect |
|---|---|---|
| Add a flexible editor-managed form | Gravity Forms block | Entries are deleted after submission unless the form setting Keep entries in database is enabled. |
| Change signup thank-you text | Skjema: Meld deg inn block |
Updates the message shown after the custom enrollment API accepts the submission. |
| Change loan-right confirmation thank-you text | Skjema: Bekreftelse på lånerett block |
Updates the message after /v1/enrollments/verify accepts the submission. |
| Edit brochure order intro or thank-you text | Parent Brochures block |
Controls the order flow heading/description and confirmation text. |
| Add or remove brochure material | Child Brochure block inside Brochures |
Controls one orderable item, its image, file, and available languages. |
Editor checks before publishing forms:
- Submit a test on stage (
https://beta.tibi.no) after changing any form page. - Confirm required text appears in both Bokmal and Nynorsk when the form supports both.
- For brochures, verify each item has the correct PDF/file, image, and language toggles.
- For Gravity Forms, decide explicitly whether entries should be stored. The default behavior deletes entries.
Developer references:
packages/wordpress/plugins/tibi-core/inc/gravityforms.phppackages/wordpress/plugins/tibi-block-library/src/form-signup/packages/wordpress/plugins/tibi-block-library/src/form-confirm/packages/wordpress/plugins/tibi-block-library/src/brochures/packages/wordpress/themes/tibi/src/signup.tsxpackages/wordpress/themes/tibi/src/confirm.tsxpackages/wordpress/themes/tibi/src/brochures.tsx
Global Search
The site header search has two modes:
| Mode | What it searches | Where results go |
|---|---|---|
| Library | Book/catalog suggestions | /boker/søk?... |
| Web | WordPress content suggestions | /?s=... |
The web suggestions use the WordPress REST search endpoint. The backend can be overridden by Algolia for eligible searches, and Tibi adds rules around short/empty searches and help category filters.
Editor checks:
- Published pages and posts can appear in web search.
- Help pages and FAQs should be tested from the Help search, not only from global search.
- If a newly published item does not appear, check indexing before changing content repeatedly.
Developer references:
packages/wordpress/themes/tibi/src/search.tsxpackages/wordpress/themes/tibi/inc/algolia.phppackages/wordpress/themes/tibi/inc/query.php
When Editors Should Ask A Developer
Ask a developer before:
- Changing the meaning of a custom form field.
- Adding a new signup category or endpoint.
- Changing the brochure email recipients or sender.
- Changing what content types are searchable.
- Creating new Help templates or changing the Help landing page behavior.
- Expecting Gravity Forms entries to be retained for a new business process.