content

Strukta

Available

Strukta is the content management workspace for structured pages, media, and publishing workflows. Editors can draft content, review changes, publish approved material, and expose content through web or API channels.

Open Strukta

Verified user manual

Strukta user manual

Create, review, version, and publish structured pages, posts, products, media, navigation, and site settings in Strukta.

Manual: Version 1.0
Product: Strukta 1.0.0
Verified: July 15, 2026
Language: English · Source
Owner: Strukta product and support
Source: strukta · abe4b2d
Review cycle: 90 days

Start here

Audience, scope, and prerequisites

Covers the Strukta administration interface for Pages, Posts, Products, Categories, Tags, Media, Homepage, Navigation, and Site Settings, plus verification on the rendered site. Direct database and deployment administration are excluded.

Who this is for

Content editors
Publishers and reviewers
Site administrators

Before you sign in

A Strukta role in the correct tenant
Approved editorial, accessibility, brand, and publishing rules
Rights to use uploaded media and product or post content

Access model

Roles and responsibilities

Role	Access	Responsibilities
Reader or auditor	Review allowed content, versions, and published output.	Use content for an approved purpose Report unexpected access
Editor or operator	Create and update content and media within assigned collections.	Maintain structure and metadata Keep work in draft until ready
Publisher or administrator	Publish content and manage site-wide configuration when permitted.	Review changes and timing Protect navigation and global settings

Chapter 01

Create structured content

Choose the correct collection and path before writing so content can be found, reviewed, and rendered reliably.

Procedure 1.1

Create a page

Build a page from approved blocks and save it as a draft before publication.

ForEditor

1
Open Pages
Search by title and path before creating a new record.
2
Set identity fields
Enter title, locale, path or slug, and the required metadata.
3
Add content blocks
Use the available Hero, Rich Text, Feature Grid, and Call to Action blocks in a logical order.
4
Check links and assets
Use approved targets and verify alternative text and rights for media.
5
Save as draft
Do not publish until the preview and review criteria are complete.

Expected result

A structured draft exists at a unique path with valid content, links, metadata, and accessible media descriptions.

Procedure 1.2

Create a post or product

Use collection-specific fields, classifications, and relationships.

1
Choose Posts or Products
Use the collection that matches the public content type.
2
Search for an existing record
Check title, slug, product identity, and archived records.
3
Enter required content
Complete title, body or product fields, summary, locale, and status.
4
Assign categories and tags
Reuse controlled terms rather than creating spelling variants.
5
Save and preview
Review the draft in its rendered context before requesting publication.

Expected result

The draft uses the correct collection and controlled metadata and can be reviewed in context.

Procedure 1.3

Upload and reuse media

Create one well-described asset and reuse it instead of uploading uncontrolled duplicates.

1
Search Media
Check filename, subject, and prior usage before upload.
2
Prepare the asset
Confirm file type, dimensions, classification, rights, and removal of hidden sensitive metadata where required.
3
Upload once
Use a durable filename and complete title, description, and alternative text.
4
Insert from the library
Select the existing media record in pages, posts, products, or globals.
5
Verify rendering
Check crop, clarity, caption, alternative text, and responsive behavior.

Expected result

A reusable, rights-cleared media record renders correctly and remains attributable to its metadata.

Chapter 02

Review, publish, and recover

Publication makes content visible to its configured audience; use drafts and version history as controlled review mechanisms.

Procedure 2.1

Review and publish content

Complete editorial and rendered checks before changing a draft to published.

ForPublisher

1
Open the requested draft
Confirm collection, locale, path, author, and intended publish time.
2
Review content
Check accuracy, spelling, links, accessibility, metadata, and rights.
3
Preview the rendered page
Test desktop and narrow layouts and any call-to-action behavior.
4
Resolve review findings
Return the draft to the editor or correct it with a traceable version.
5
Publish
Change status only when approval and timing requirements are satisfied.
6
Verify the public route
Open the expected locale path and confirm the new version is served.

Expected result

The approved version is visible at the intended route and the prior draft/version history remains traceable.

Procedure 2.2

Review or restore a prior version

Use collection history to understand and recover an earlier state.

1
Open the record history
Choose the relevant page, post, or product and open Versions.
2
Compare metadata
Review timestamp, author, status, and changed content.
3
Select the intended version
Confirm it predates the unwanted change and still meets current policy.
4
Restore into review
Restore or copy the earlier version, then treat it as a new change requiring review.
5
Verify and publish
Preview and approve before replacing the current published state.

Expected result

The selected content state is restored through a traceable version and reviewed before publication.

Chapter 03

Manage site-wide structure

Globals affect broad parts of the site and should be changed with stronger review than an individual page.

Procedure 3.1

Update homepage, navigation, or site settings

Change a global record with impact analysis and immediate verification.

ForPublisherAdministrator

1
Open the correct Global
Choose Homepage, Navigation, or Site Settings and confirm the active locale or scope.
2
Record current behavior
Capture the affected routes, labels, links, metadata, or brand elements.
3
Make the smallest change
Avoid unrelated cleanup in the same global edit.
4
Review dependent routes
Check homepage, header, footer, navigation hierarchy, and locale behavior as applicable.
5
Save and verify
Confirm the changed global renders without broken links or inaccessible navigation.

Expected result

The intended global behavior changes without disrupting unrelated routes, locales, or navigation items.

Operating rules

Security and data handling

Use least-privileged editor and publisher roles.
Keep drafts unpublished until editorial, legal, accessibility, and rights checks are complete.
Sanitize media and remove unnecessary sensitive metadata.
Review external links and embedded content before publication.
Treat global navigation and site settings as high-impact changes.

Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Strukta 1.0.0 scope and must be rechecked when the product changes.

Draft/version behavior is verified for Pages, Posts, and Products; other collections may not expose the same workflow.
Publication permissions depend on collection access rules and assigned roles.
The renderer serves only published content at public routes.
API use is outside this end-user manual and requires separate integration authorization.

Problem solving

Troubleshooting

You cannot sign in to Strukta

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

Open the application from the approved portal and complete sign-in again.
Confirm that the correct organizational identity and tenant are selected.
If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

Confirm the role and prerequisites listed for the procedure.
Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

Review inline validation, status indicators, filters, and the selected tenant or workspace.
Refresh once and search for the item by its stable name or identifier.
Do not repeat irreversible or externally visible actions until the original operation status is known.

Published content is not visible

Likely cause: The record remains draft, the locale or path differs, cache is stale, or a required field prevents rendering.

Reopen the record and confirm published status, locale, and path.
Open the exact public route in a fresh session.
Check related media and globals before republishing.

A media asset cannot be uploaded or selected

Likely cause: The file is unsupported, duplicates an existing filename, exceeds policy, or the role lacks media access.

Search the media library for an existing asset.
Verify file type, filename, size, and role.
Do not rename an unrelated asset merely to bypass a collision.

Escalation

Contact support

Contact support when

A repeatable Strukta error blocks an approved workflow
Expected data, permissions, or tenant boundaries appear incorrect
A security, privacy, compliance, or data-loss concern is suspected
A published or global change affects unexpected routes
Version history or public rendering does not match the approved record

Include

The page, action, and expected result
The exact error text and time of occurrence, including time zone
Your tenant, role, browser, and a sanitized record or item identifier
Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

Passwords, access tokens, API keys, recovery codes, or session cookies
Unredacted personal, health, financial, or other regulated data
Private encryption keys or complete confidential documents unless an approved channel is provided

Contact support