English
Keep planned work in view.
Schedule supported actions, follow their results, and see what needs attention.
One shared schedule. Visible status. Clear next steps.
Inspect a scheduled action
Follow a Content action from current review to its retained result. These browser records are authored examples.
Review before scheduling
Choose a registered Content action, inspect its target and check the exact instant before keeping a local schedule record.
Owner · Content
Publish Content
What you can build with Kottoko- Display time
- Dec 1, 2026, 10:00 AM
Europe/Stockholm - Resolved UTC instant
- 2026-12-01T09:00:00Z
- Target revision
- Approved revision · example 1
Scheduling keeps the action, target, owner and exact time together. Review the approved revision first. Changing the action, revision or display zone makes the draft review out of date.
Review this draft before creating its local schedule record.
Fixed example: 1 December 2026 at 09:00 UTC. The two display zones show the same instant. No live article status is inferred.
Review this action
Change the draft, review it and keep a local schedule record. Cancellation and recovery retain the example history. Reset affects this sample only.
Action and attempt history
No local action has been recorded yet.
Installed setup and limits
Installed Content registers publish and unpublish actions. A real schedule binds the entry revision, current approval, verified actor, permission and resolved future UTC instant. Ambiguous local times require an offset; nonexistent times are rejected. Workers recheck authority and keep attempts. Newsletter sending has a separate registered adapter; form retention and rollouts are not generic Content schedule actions. This browser calls none of them.
Follow registered activity
Inspect a form-submission observation, its read and archive state, and the recovery path when the source is unavailable.
Owner · Forms
Form submission received
forms.submission.receivedAn activity item points to its source. Reading, archiving and restoring affect the item, while source availability and current permission still determine whether it can open.
The link opens the real public form example. It is an example source, not a receipt or an existing submission for this authored observation.
Summary: received. No personal answers or submission identifier are shown.
Manage the activity item
Archive marks the item as read. Restore keeps that read state. The notification choice applies only to this local in-app example.
The example source is available. The link opens the public form, without implying a stored response.
Installed setup and limits
The installed type is forms.submission.received, produced by a registered Forms transition. It has a subject-account audience and an optional in-app preference. Opening a real source rechecks current access and the source route. Archived items are read; restoring does not make them unread. Inactive Activity blocks preference changes. This sample creates no submission, activity event or email.
Review a staged release
Inspect one registered flag and a bounded audience. Each transition needs a fresh review; this example changes no public navigation.
Owner · Core
Counter navigation refresh
core.counter-navigation-refreshA staged release combines a registered flag, an audience and reviewed transitions. The selected flag has no consumers, so these local states have no visible navigation effect.
- Safe fallback
- Disabled
- Registered consumers
- None
- Authored observation window
- 1–7 June 2026 · UTC
Choose an audience and review before applying the example.
Review a release transition
Inspect the audience, review one next action and apply it locally. Each later action needs its own review. Reset clears only this release sample.
Transition history
No transition has been applied in this sample.
Installed setup and limits
The installed registry owns core.counter-navigation-refresh. Its safe fallback is disabled and its consumer list is empty. Real transitions bind the current configuration and authority to a one-use review; future starts can be scheduled, while pause, resume, complete and retire have distinct rules. This local observation neither installs features nor changes access, invitations or navigation.
Supported events and actions
Provider work has its own setup, permissions and results. It is separate from these Content schedules and form-activity observations.
Where provider work belongs
Configured providers, credentials and their results belong in the installed project. These public examples make no provider requests. Inspect the separate Settings example for the public configuration explanation.
View the Settings exampleBuild a website or app.With the core features included.
Kottoko is a starter project for websites and apps. It includes pages, user accounts, forms, and online store features you can customize instead of building from scratch.
The features you need, already built in.
See your changes as you make them.
Edit content, tune the design and choose features against the same website your visitors see.
Make Kottoko your own.
Change the heading and accent in this miniature page. It uses the same heading, field, and color controls as the website.
Make Kottoko your own.
Change the heading and accent in this miniature page. It uses the same heading, field, and color controls as the website.
What you can build
Explore starting points for websites, shops and member experiences.
Websites
Publish your ideas, work and resources.
Commerce
Sell products, downloads and subscriptions.
Members & apps
Create spaces for members and customers.
Growth
Connect with your audience and understand what works.
Design
Shape the look and feel of your project.
Operations
Keep your project connected and running.
Questions before you start.
Is Kottoko for websites or apps?
Both. Start with public pages, then use accounts, dashboards, forms, commerce, and other included features as your idea needs them.
Do I need to write code?
The editor lets you try supported content, design, and feature choices visually. Building custom behavior, connecting services, and deploying the project can require a developer or coding agent.
Are payments and email ready to use?
The payment integrations currently support test mode. These browser examples do not charge money or send transactional email. Live payment support still needs implementation and review; email delivery needs its own provider setup.
How do updates work?
Review how a change affects your project, prepare a backup, and check the result before release. Your hosting and setup determine the recovery steps.
Can I download Kottoko now?
Public downloads are not open yet. Explore the examples and documentation, or join the list below for launch updates.
Build your next project with a head start.
Get launch news, new examples, and product updates.
Confirm by email. Leave anytime. Read our privacy notice.