English
See what is included
Choose features by the journey you want people to complete. This guide separates the examples you can explore here from the scope of the upcoming downloadable product.
What you will learn
You will have a short feature list tied to a visitor goal, with examples and release status checked separately.
Start with one visitor goal
Write down what a visitor should be able to finish: read an article, send a response, browse a product, or use an account. Choose one main journey first. A feature is useful when it supports a step in that journey; a longer feature list does not by itself make the project more useful.
Understand how the parts connect
Content presents pages and articles. Forms collect responses. Accounts control access, while store features connect products, checkout, and customer views. These parts work with the same design rather than requiring unrelated pages. Follow the existing form or order lesson to see both the visitor side and the owner or customer side of an example.
Read an example as an example
The website offers interactive previews. Example edits, responses, and orders stay in your browser; they do not publish a site, send an example email, or take payment. The first-release capability list describes intended scope. It is not evidence that a downloadable product or a live service is available.
Make a selection you can explain
For each feature, record the visitor task it supports and which connected parts it needs. Optional features are selected for the project rather than all being added to every project. Keep a separate list of questions about hosting, services, or release availability so those decisions are not hidden inside the feature list.
Put it into practice
Your result is a project brief: one visitor goal, the features needed for it, and the questions that still need an answer. Use it as the starting point for setup planning.