FROM COMPANY FACTS TO PAGES
Start your website from the information your business already maintains
Prepare a grounded site structure from company facts and supported content sources, then review the pages before making them public.
Reuse the facts without removing editorial responsibility
A company website repeats information that already exists elsewhere: what the business does, how to reach it and which services or products it offers. Tsumira can use those facts to prepare a practical page structure. Generated content is a starting point tied to supported sources, while the owner still chooses the message, checks the detail and decides what should become public.
Prepare the core company pages
The core page family covers home, about, access, contact, FAQ, news and the company-owned privacy-policy and terms routes. Its composition uses company facts and the selected site goal. Initial materialization creates unpublished drafts for review. A legal-page heading or a generated paragraph is not proof that its content fits the company; the responsible person still needs to check what the page says before release.
- A defined core site structure
- Company facts and chosen site goal
- Initial pages prepared as unpublished drafts
Add the supported catalog context
Enabled modules can contribute their supported public page families, such as service, product or quotation content. Their availability depends on the relevant source and publication approval, not just a module name appearing in a menu. This makes reuse practical without promising that every record, every possible location combination or every internal field automatically becomes a search landing page. Choose the public content that actually helps the visitor.
- Supported module page families
- Source-linked public information
- Explicit selection of useful visitor content
Preserve work that people have customized
Generation distinguishes a generated draft from an operator-owned or detached page. Custom work should not be silently replaced just because company facts are regenerated. The supported flow can retain human-owned pages and let an operator customize a generated page through its editor. Keep that distinction in mind when improving a source: a deliberately customized page may need its own editorial update.
- Human-owned content retained
- Generated and customized pages distinguished
- Editorial review after relevant source changes
A concrete workflow
Maintain the company facts
Check the company identity, contact information, offer and intended visitor action.
Prepare the page structure
Generate the supported core drafts and choose relevant enabled public content families.
Review and customize
Check wording, imagery, links and the meaning of each page before approval.
Publish deliberately
Use the authorized publication workflow and verify the resulting public routes.
An illustrative working example
Example: a service company’s first site
A services team enters its company details and prepares the core site drafts. It reviews the contact page, adds its actual imagery and chooses the supported service family for the offer. A custom page explains an unusual engagement type. Later, regeneration can improve pristine generated drafts without treating that custom explanation as disposable. The company gains a practical starting structure while retaining responsibility for what visitors read.
Questions about this topic
Does generation immediately publish everything?
No. The initial core flow prepares unpublished drafts. Public release follows the relevant review and publication process.
Will every internal record become a public page?
No. Only supported and appropriately enabled public sources and page families participate. Internal records retain their own permissions.
Can I customize a generated page?
The supported editor and detach/customize workflow provide that route. Customized ownership changes how later generation should treat the page.
Are generated legal pages automatically sufficient for our company?
No automatic suitability is established by generation. The responsible company must check its actual content and required statements before publishing.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Docs
Workflow concept: Prepare approved company facts and service explanations as input for reviewing generated page drafts.
Google Drive
Workflow concept: Organize the company images selected for the first generated site structure.
Notion
Workflow concept: Compare the generated page outline with the company’s maintained positioning and editorial brief.