Welcome to the SaaS foundation

This is a SaaS foundation you can deploy yourself. It combines accounts, content and personal subscriptions so you can start building your product around real user journeys.

Complete one journey first

Open the documentation and prepare a local environment using the installation guide. Then create a test account and inspect the account and billing pages. The default examples do not make real purchases or send messages to unknown contacts on your behalf. After connecting your own provider configuration, verify the full journey in a controlled environment.

Before starting, confirm three things:

1. You know whether you are using a local test environment or a deployed environment.
2. You have configured your product name, public address and support contact.
3. You understand which features need external services and which content comes from repository files.

Content consists of complete versions

This article is a complete English version maintained alongside its Chinese counterpart. Both share the same topic identity. The title, summary and body publish together; changing the interface language does not generate another article.

Content without a translation offers an English reading link. A Chinese address does not silently present English prose, and unpublished drafts do not enter public search. After withdrawal, the article and its retained addresses no longer provide public reading.

Edit and publish safely

When editing an article in administration, saving a draft does not replace the published version readers currently see. Review the title, summary and full body first, then explicitly publish the saved version. Use withdrawal when public reading should stop temporarily.

Language does not change your account, product identity or billing currency. If a purchase result has not been confirmed, inspect the original operation's status. Refreshing the page or changing language does not mean another purchase should be submitted.

Next steps

Read the English documentation for local preparation and configuration checks before publication. The template supplies composable foundations; the deployment owner remains responsible for the final product's features, policies and support commitments.