English
Check release availability
An interactive example, a planned capability, and an available download describe different things. Learn how to read the current public status before treating a preview as a product you can install.
What you will learn
You will know what you can try now and what still depends on a public release.
Recognize what is public now
The public website offers feature previews, documentation, and a free email list for product and launch updates. You can explore the previews without an account. The documentation currently states that project downloads and purchases are not open yet.
Keep example activity in context
Article edits, form responses, and example orders stay in your browser. An example order shows a journey; it does not take payment or grant a real purchased product. A form example does not send an email. Use these examples to learn how the views connect, then test the actual services when preparing a real project.
Separate intended scope from release status
The first-release feature list describes what the product is intended to include. Local progress and a working preview do not mean the complete product has been released. Check the public status reference before making an installation or purchasing decision.
Choose a useful next step
While downloads remain closed, you can learn the examples and prepare a project brief covering content, hosting, services, and care. For release news, the website offers an email-confirmed waitlist with removal links. Recheck the documentation when you need current availability; this learning guide explains how to interpret it.
Put it into practice
You can practice on the website now. Keep the project plan separate from an installation plan until public status confirms that a download is available.