Knowledge Base

Capabilities across admin, storefront, commerce, and APIs—with links to detailed examples.

Clone, configure, migrate, and sign in to the admin.

What Struxa is, who it is for, and how the pieces fit together.

PHP, extensions, database, and web server expectations.

How the admin sidebar is organized.

Keeping the site healthy.

Uploading and reusing images and files.

Building header and footer links.

When to use Pages versus Content types.

Helping visitors and search engines find content.

Global settings that affect SEO and layout.

Who can do what in the admin.

Compose pages and entries with reusable visual blocks.

Moving structure and sample content between sites.

Saved queries over entries—filter, sort, paginate; use on pages, in Twig, or via the API, with real-world examples.

Relating content and powering dynamic blocks.

Day-to-day editorial workflow.

Link entries to other entries with the entry_refs field type.

Drafts, review, history, compare, and restore.

Titles, descriptions, and social cards.

Organizing entries with terms.

The building blocks of structured content.

Schema changes, composer migrate, and bin/cms.php.

Where code lives and how requests flow.

Extending behavior without forking core.

Slim routes, middleware, and public URL patterns.

Headless access to content, lists, and entry references.

From folder to activation.

Declaring requirements, hooks, and permissions.

SQL on activate, async work, and uninstall.

Wiring screens into the admin and public site.

Overriding index, show, taxonomy, lists, and block sections.

theme.json, views, assets, and activation.

Parents, theme_asset(), and the storefront asset boundary.

Digital delivery, customer access, admin orders, and refunds.

End-to-end commerce checklist.

Product fields, storefront flow, and CSRF.

Keys, webhooks, tax modes, shipping zones, and coupons.