Creator — Aura Storage deep dive

Browse guides and resources in this category

21 resources
Updated regularly

CMS theme & menu apply / remove without wiping data

Change the panel look or site menu with CMS buttons — posts and orders stay in the warehouse.

View

Configure the IDE on Windows safe paths

Avoid path errors: folders without spaces; use / or \\ exactly as the zip package shows.

View

Content security settings who can view / append

Adjust in the CMS UI: guests only send contacts; hide drafts; some actions are admin-only.

View

Enable MCP in Creator: session · token · download package

Follow the MCP tab buttons in order — match the UI labels; you don’t need to know the code underneath.

View

Aura webapp handoff checklist before customers use it

One check sheet: Creator · Storage · CMS · MCP (if used) — tick everything before you hand off.

View

CMS runs on Aura only two declaration files · correct Prompt · no Easy

Know what the content manifest and UI contract each do — so you and AI stay aligned, and the Panel doesn’t break.

View

Contacts · Products · Orders small-shop end-to-end

Visitors submit contact forms or place orders on the site → you change status in CMS — one operations loop with no code.

View

Content map why file names must match

CMS already has 3 “Published” posts but the blog page is empty? Usually the page and CMS are not reading the same ledger.

View

Custom data types Panel Save · fields · taxonomy · real-estate site

Declare on the Panel so CMS updates both declaration files correctly — then ask AI to polish list/detail pages and filters.

View

IDE ↔ Creator conflicts & expired tokens

When several people edit: who clicks Save changes last; what to do when a token expires — clear and safe.

View

Open CMS for the first time & the owner account

Enter the back office: create the owner account once, then use Overview every day — no need to open Creator just to publish a post.

View

Posts · Pages · Categories day-to-day CMS work

Publish posts, go live, manage static pages — like WordPress admin, already wired to your Appifio site.

View

Public contact form (no login required)

Safe flow: visitors append one row to the contact ledger, see a thank-you, and if they submit too often they see “Try again later”.

View

Secrets & server functions (send mail / payments…)

Keep service keys in the vault (Secrets) — do not paste them into HTML where anyone viewing source can see them.

View

Symptom → error layer Creator · Storage · CMS · MCP

When something breaks: don’t guess — use the table below to see which “room” failed, then open the right lesson.

View

AI declares a custom type merge correctly · Panel reads without errors

When you ask AI to create a type without clicking Save on the Panel — AI must update both declaration files with the same Panel conventions, then create HTML + routes.

View

Admin login & site roles

Who can do what: light editor, admin, super admin — in everyday jobs, without memorizing tech jargon.

View

Two data shapes: config sheet vs multi-row ledger

Before you ask AI to “save data”, pick the right shape — like choosing a one-time sticky note versus a ledger with one row per customer.

View

URLs and HTML pages must travel together

Avoid “blank page / 404”: having a page file is not enough — you also need a matching route.

View

What is Aura? Three layers: pages · data · admin

Opening lesson for the Aura series: separate Creator, Storage, CMS, and MCP with a shop metaphor — so you know where to go and what to do each day.

View

What is MCP? When you need it — and when you don’t

For shop owners who don’t code: MCP is a side door for builders who bring an IDE — not required to sell products or publish posts.

View

Build with Appifio

Create websites, bio links, and web applications — explore our guides and resources to get started.

Get started free

Subscribe to our newsletter

We provide useful information for you. No spam, we promise.

We respect your privacy. Unsubscribe anytime.

Secure Regularly updated No spam