Site-Building Workflow

Tip: First time using AllinCMS admin? Follow the main path first: prepare before building -> edit the site -> check before launch -> operate after launch.

AllinCMS admin helps you build and manage a business website. You can create a site, upload products and posts, edit pages, connect your own domain, and publish the site.

This page is only for choosing the right route. Do not look for detailed operations here. First identify your current stage, then open the matching guide.

Start immediately when your domain and content are ready

If you already bought a domain and prepared product materials, posts, images, and contact details, go directly to Getting Started and follow the site-editing workflow.

Beginner rule: edit existing template content first, add only what is missing, and do not delete everything and rebuild at the beginning.

Search Keywords First

When you are not sure how to set something, use the search box in the top right first. Try keywords such as wa, domain, 404, or product category, then open the closest guide from the results.

Read Order

1Before buildingDomain, materials, images2Site editingSite, content, pages3Pre-launch checkTemplate, contact, 4044After launchIndexing, data, posts

Stage	What you finish	Doc
Prepare	Domain, hosting note, materials, images, contact details	Before You Build
Edit	Create site, add products and posts, edit homepage and pages	Getting Started
Check	Template content, contact, form email, 404, mobile	Launch Checklist
Operate	Submit sitemap, check indexing, review analytics, update posts	Submit Sitemap

Choose Your Entry

Your situation	Read first
No domain and no materials yet	Before You Build
Domain, product materials, images, and contact details are ready	Getting Started
The site is mostly finished and ready for customers	Launch Checklist
The site is live and you want to check Google indexing	Submit Sitemap
The site is live and you want to check traffic data	Google Analytics 4

Beginner Rules

• Check the frontend after creating a site. Make sure it is not 404.
• If theme, pages, products, and posts already exist, edit default content first.
• Use clear English slugs for categories, routes, and menu links.
• Check homepage menu, banner, category showcase, featured products, recommended posts, and footer contact info.
• After connecting a domain, DNS and SSL may take 10 to 30 minutes.
• After publishing, always open the live page and click through.

Next

Before You Build - prepare domain, materials, images, and contact details first.

AI-Only Global SOP / Knowledge Base Rules (covers all docs workflows)

This section is for AI / automation assistants. When asking AI to read materials, draft products and posts, edit pages, upload site content, troubleshoot issues, or run launch checks, have it follow this global rule set first.

1. Core Principles

• First identify the user's current stage: preparation -> site editing -> pre-launch check -> post-launch operation.
• Read the official docs before operating the AllinCMS admin. Do not guess backend behavior.
• Organize the source inventory and missing questions first, draft content next, upload a sample, then batch process only after user confirmation.
• Batch creation or batch publishing requires the sample and upload inventory to be confirmed first. Products and posts can only be previewed after publishing, so when publishing is needed, publish and return both the backend record and the frontend view link.
• Deleting content, clearing the media library, changing domains, changing routes, or overwriting many pages are high-risk operations and require separate confirmation.
• Before each edit, list what will be changed, what will not be changed, and what information is missing so the user can review it.
• After each edit, list what was actually changed or uploaded, what remains, and update the local handoff record for the next run.
• If the user provides a batch of materials, process the full batch. Do not stop after uploading only two or three categories, a few products, or a few posts unless the user explicitly narrows the scope.
• Do not invent product specifications, certifications, prices, capacity, customer cases, company history, or contact details.
• Do not copy unauthorized images, text, brand copy, cases, or product materials.
• Images used in public docs must use stable PicGo/COS URLs or repository static paths. Do not use local temporary paths.
• Images displayed on the live website must be uploaded to the AllinCMS admin media library first, then selected from the media library. Do not replace backend media with external image URLs.

2. Permission and Confirmation Boundaries

Operation level	What the AI may do	What must be confirmed
Read-only analysis	Read materials, docs, backend fields, and frontend pages	No content is modified
Local organization	Produce inventories, field maps, sample SOP, and handoff notes	Missing materials and planned edits
Backend create/edit	Upload media, create or edit products, posts, pages, menus, and modules	Target site, field map, sample content, and upload totals
Publish for preview	Publish products or posts and return view links	Products/posts require publishing before preview; state this first, then return backend records and frontend links
High-risk operations	Delete, overwrite many items, clear media, change domains/routes, rebuild the homepage	Confirm each operation separately; do not include it in a broad authorization

• If overwriting old content is uncertain, capture the original value or screenshot and mark it for user confirmation.
• Publishing is not the finish line. After publishing, return to the list page to confirm status, then open the frontend link and check images, text, links, and mobile display.

3. Doc Reading Order

Build the working knowledge base from the docs in this order:

Stage	Required docs	What the AI must understand
Entry	Site-Building Workflow	Overall order, search entry, and which guide to use
Preparation	Before You Build, Image Guidelines	Domain, materials, images, and contact details
Editing	Getting Started, Create Site, Site Settings	Enter site admin from Workspace, edit template content first
Content	Product Categories, Add Products, Add Posts	Category, product, and post fields and upload order
Pages	Homepage Essentials, Product Module, Featured Products, Advanced Pages	Homepage, modules, cases, gallery, video, and popups
Links and menus	Redirect Links, Menu Order, Dropdown Menu	Prefer Internal links and do not guess paths
Contact	Contact Links, Form Editor, Popup Form, WhatsApp Floating Button, Location Map	Phone, email, WhatsApp, forms, and maps
Pre-launch	Launch Checklist, Bind Domain, Cloudflare DNS	Template residue, form testing, 404, DNS, SSL, mobile
Troubleshooting	Publish Failed, Site Not Secure, Page History Restore, Image Fit, FAQ	Diagnose before rebuilding
Operation	Submit Sitemap, Google Analytics 4, Article SEO Guide	Indexing, analytics, and ongoing posts
AI tools	AI Website Building and Automatic Content Upload	How AI should read sources, draft content, upload, and review

4. Knowledge Files the AI Should Produce First

After reading materials, output these structures before uploading:

File / checklist	Contents
source_inventory	Files, images, spreadsheets, URLs, and what each source contains
site_brief	Company name, industry, main products, target regions, contact details, tone
taxonomy_map	Product categories, category slugs, products under each category, and existing categories/tags that must not be missed
product_manifest	Product name, slug, category, tags, summary, specs, main image, gallery, detail images
post_manifest	Post title, slug, category, tags, summary, body structure, cover image, internal links
media_manifest	Image purpose, size, compression status, alt text, related product or post
field_map	Mapping between source fields and real backend fields, such as title, slug, category, tags, summary, main image, gallery, body, and publish status
page_plan	Homepage, About, Contact, OEM, Cases, and other page changes
link_map	Header menu, dropdown menu, buttons, homepage modules, and footer targets
missing_questions	Required information missing before upload
upload_plan	Full upload scope, total counts, what to upload first, sample items, and batch order
sample_sop	Confirmed sample rules for products and posts: fields, images, categories, tags, tone, and links
local_handoff	Local handoff record: current progress, confirmed workflow, uploaded content, unfinished items, and next continuation point
qa_report	Frontend check results, issue screenshots, and user-confirmation items

5. Site Editing SOP

1. Confirm the target site first to avoid uploading to the wrong website.
2. Enter Sites -> target site -> Enter Admin from Workspace.
3. Check site settings: site name, description, favicon, and notification email.
4. Edit existing template content first. Do not create duplicates when defaults can be changed.
5. For the first version, 3 to 4 main product categories are usually enough.
6. After creating a product category, the related category link already exists. Do not create duplicate category pages in Routes.
7. Before uploading, list the full inventory: total categories, tags, products, posts, images, missing fields, and user-confirmation items.
8. Before uploading, output a field_map and confirm which source field maps to which real backend field. Do not miss tags, categories, galleries, detail images, or page descriptions.
9. Before editing existing pages, products, posts, or menus, record the original content or screenshot. If overwriting is uncertain, ask the user first.
10. Products must start with 1 sample product. The sample should include category, tags, title, slug, summary, specs, main image, gallery, detail content, internal links, and the published view link. After user confirmation, use that sample SOP to complete all products.
11. Posts must also start with 1 sample post. The sample should include title, slug, category, tags, summary, cover image, body structure, H2/H3 headings, internal links, and the published view link. After user confirmation, use that sample SOP to complete all posts.
12. Batch upload must complete the full product_manifest and post_manifest. Do not treat a small partial upload as finished.
13. The homepage must have a working menu, banner, categories, featured products, recommended posts, and contact info.
14. Prefer Internal links for menus, buttons, and modules. Use Custom only when Internal is unavailable.
15. After major edits, open the frontend and click through. Backend save status alone is not enough.

6. Content Rules

• Product content must come from user materials. Do not invent specifications, certifications, materials, pricing, stock, or lead time.
• Product titles must be clear. Do not use Product 1, Untitled Product, or test names.
• Product summaries, page descriptions, and post summaries must be distinct.
• If user materials already include product categories, tags, product ownership, or post categories, keep them in the inventory. If uncertain, mark them as missing questions instead of ignoring them.
• Posts must answer real customer questions. Do not publish thin filler posts.
• For posts, follow the Article SEO Guide: choose a real question, prepare sources, answer early, use H2/H3 structure, and link to related products or categories.
• If removing the company name and product name makes the article usable on any competitor site, it is too generic and should be rewritten.
• AI may assist rewriting, but the final content must include real products, scenarios, parameters, images, experience, or cases.
• Unless the user explicitly asks AI to create content from scratch, missing specs, images, cases, and post materials must be asked about first, not invented.

7. Image and Media Rules

• Product main images and galleries: 800 x 800 or 1000 x 1000 square, centered subject, even margins.
• Post cover images: around 1200 x 700.
• Homepage banners / carousels: around 1800 x 1000.
• Product and post detail images: width no more than 1500; suggested 1500 x 1000 or 1500 x 600.
• Every image displayed on the live website must be uploaded to backend Media first, then bound to a product, post, or page module from the media library. Do not only paste external image URLs.
• Compress before upload, prefer WebP, and keep each image around 300KB when possible.
• Do not write alt text such as "image 1". Describe the actual image.
• If the image ratio is uncertain, read Image Guidelines first. Do not upload original phone images directly.

8. Batch Execution and Failure Handling

• Before a batch run, source_inventory, field_map, upload_plan, sample_sop, and the target site must already be confirmed.
• After each batch, verify backend counts, publish status, category/tag ownership, whether images come from the media library, and whether frontend links open.
• If the same type of operation fails twice in a row, pause the batch, record failed items, error messages, screenshots or response details, then ask the user whether to continue.
• Do not silently skip failed items. Skipped items, missing fields, missing images, publish failures, and broken links must be written to qa_report.
• If the user changes the workflow, update sample_sop and local_handoff first, then continue. Do not restart from scratch or keep uploading with old rules.

9. Launch Check SOP

Before launch, verify:

Check	Standard
Template content	No default industry copy, company names, test products, or template images
Contact details	Phone, email, WhatsApp, and address are real
Form email	Submit a test inquiry and confirm the notification email receives complete data
Links and 404	Header, dropdown, buttons, footer, product detail, and post detail all open
Images	No blur, distortion, severe cropping, or mobile overlap
Page descriptions	Home, Products, Posts, About, Contact, and other pages have real descriptions
Domain and HTTPS	DNS and SSL pass, and the official domain opens correctly

10. Completion Standards and Acceptance Path

Content type	Completion standard
Products	Every product in the inventory is created or updated, categories/tags are preserved, main/gallery/detail images come from backend media, and published view links are returned
Posts	Every post in the inventory is created or updated, title, summary, cover image, body structure, and internal links are complete, and published view links are returned
Pages and modules	Homepage, menus, buttons, forms, maps, popups, and product modules are completed within the confirmed scope and checked on the frontend
Images	Frontend images do not use temporary paths or external links instead of media library assets; size, compression, cropping, and mobile display are checked
Links	Header, dropdowns, buttons, footer links, product details, and post details open correctly without wrong redirects or 404s
Local handoff	local_handoff is updated so the next run can continue from the current progress without relearning the full workflow

11. Post-Launch Operation SOP

• First confirm https://your-domain/sitemap.xml opens.
• Submit the sitemap in Google Search Console.
• If the site is not indexed, check whether content is duplicated, posts are too thin, products are too similar, or images/text were copied.
• After GA4 is configured, visit the site in incognito or on mobile and confirm realtime data appears.
• Keep publishing useful posts every week. Prioritize real customer questions over generic industry essays.

12. AI Execution Format

Before execution, ask for confirmation:

I have read the materials. Please confirm before I proceed:

1. Current stage:
2. Target site:
3. Source inventory:
4. Full upload scope and counts:
5. What I will modify:
6. What I will not modify:
7. Missing information:
8. Field map:
9. Product sample:
10. Post sample:
11. Questions needing confirmation:

After confirmation, I will continue. When products/posts need publishing before preview, I will publish them and return both backend records and frontend view links.

After execution, report:

Completed:

1. Content actually modified/uploaded:
2. Products completed / total:
3. Posts completed / total:
4. Pages involved:
5. Product view links:
6. Post view links:
7. Page/module view links:
8. Frontend check result:
9. Failed items and reasons:
10. Information still needed:
11. Local handoff record:
12. Suggested next step:

13. Local Handoff and Continuation Rules

• After every edit, write the current progress into a local handoff record, such as local_handoff, upload_plan, qa_report, or the project's designated local file.
• The handoff record must include the confirmed sample SOP, field map, uploaded inventory, remaining inventory, published view links, failed items, next continuation point, and questions needing user confirmation.
• When continuing the same project later, read the local handoff record and previous inventory first, then continue from the confirmed workflow instead of restarting from step one.
• If the user changes the workflow, fields, categories, style, or upload rules, update sample_sop and local_handoff before continuing the batch.
• If the local record and actual backend content differ, re-check the backend and frontend before continuing, correcting, or rolling back.

14. Key Judgment

• If materials are insufficient, organize and ask questions first. Do not force-write.
• If a link is uncertain, read Redirect Links first. Do not guess paths.
• If an image is uncertain, read Image Guidelines first. Do not upload originals directly.
• If the site is ready to launch, read Launch Checklist first. Backend save status is not enough.
• If the site is not indexed after launch, read Submit Sitemap and Article SEO Guide. Do not guarantee indexing or ranking.
• Samples alone do not mean the task is complete. When the user asks AI to upload full-site content, completion is based on the full inventory of products, posts, pages, and images.