Development recipes
Connect pages, business data, paid entitlements, and multilingual publishing through four practical tasks.
Once the basic configuration is complete, building your own application usually involves four tasks: creating pages for signed-in users, storing user data, controlling paid access, and supporting new languages. This chapter covers each task in a separate article, explaining which files to change, how to connect existing modules, and how to verify the results.
Where to start
| Tutorial | What you will build | Prerequisites |
|---|---|---|
| Add a business page for signed-in users | A workspace page with localized text and a sign-in check | A local project that runs and supports sign-in |
| Build a user data API from a business table | A personal saved-links API with creation and paginated retrieval | An initialized local D1 database |
| Add paid entitlements to a business feature | A complete flow connecting plans, payments, and business permissions | A working Stripe test environment |
| Add a language to your website | Japanese support for pages, UI text, and content | Familiarity with the existing page and content directories |
You can work through the first two articles in sequence. The third adds paid access to the saved-links feature, and the fourth can be read independently. The workspace, saved-links, and saved_links_access names introduced in the code are tutorial examples, not features included in the template.
All file paths in these articles are relative to the root of the application you created with Saavo. Code blocks labeled “New file” can serve as the starting point for that file. For blocks labeled “Merge into,” add only the specified fields without overwriting the existing configuration.
How this chapter relates to earlier chapters
The tutorial demonstrates the full process from product idea to launch. This chapter covers individual tasks you can complete during everyday development. The feature documentation explains each module's responsibilities, configuration, and behavior. Refer to the relevant article when you need that background.
The following topics already have dedicated documentation, so this chapter does not maintain a separate, abbreviated tutorial for them:
- Social sign-in: Google OAuth.
- Usage counts, quotas, and credits: Permissions and entitlements and Design plans and entitlements.
- Files, email, and scheduled tasks: Storage and uploads, Email, and Scheduled tasks.
These tutorials follow the template's existing layered architecture. Database schemas, SQL, data transformations, business rules, and HTTP endpoints each have a defined place. You can extend the same flow as you add features.