Where to Go Next
At this point the tutorial app should feel familiar. You have touched the same product surfaces the checked-in Shoppr app uses:
- storefront pages under
apps/shoppr/templates/pages/** - CMS pages under
apps/shoppr/templates/cms/** - account pages under
apps/shoppr/templates/account/**andapps/shoppr/templates/memberships/** - admin pages under
apps/shoppr/templates/admin/** - customer-owned backend logic in
apps/shoppr/crates/shoppr-backend/src/lib.rs
This final chapter should not be a generic wrap-up. It should tell the reader exactly where to go when they want to keep working on one of those seams.
If You Are Changing Templates, Theme, I18n, Or SEO
Look at these docs first:
website/docs/reference/template-language.mdwebsite/docs/reference/template-models.mdwebsite/docs/reference/theme-structure.mdwebsite/docs/reference/theme-asset-delivery.mdwebsite/docs/reference/internationalization.mdwebsite/docs/reference/seo.md
Then look at these Shoppr files:
apps/shoppr/templates/layouts/base.htmlapps/shoppr/templates/pages/home.htmlapps/shoppr/templates/cms/page.htmlapps/shoppr/templates/account/nav.html
Why:
- the reference pages explain the template and render-model contract
- the Shoppr files show how that contract is actually used in a full app shell
If You Are Changing CMS Pages Or Block Rendering
Look at these docs first:
website/docs/reference/cms-page-builder-model.mdwebsite/docs/reference/render-model-hooks.mdwebsite/docs/core-concepts/themes-rendering-and-assets.md
Then look at these Shoppr files:
apps/shoppr/templates/cms/page.htmlapps/shoppr/templates/cms/pages.htmlapps/shoppr/templates/cms/blocks/**
Why:
- the docs explain the block model and render-model handoff
- the Shoppr files show the live frontend and admin sides of that same block system
If You Are Changing Accounts, Memberships, Or Entitlements
Look at these docs first:
website/docs/reference/modules/commerce.mdwebsite/docs/reference/modules/memberships.mdwebsite/docs/reference/linked-rust-hook-apis.md
Then look at these Shoppr files:
apps/shoppr/templates/account/dashboard.htmlapps/shoppr/templates/account/nav.htmlapps/shoppr/templates/account/passes.htmlapps/shoppr/templates/account/orders.htmlapps/shoppr/templates/memberships/account.htmlapps/shoppr/templates/memberships/passes.htmlapps/shoppr/crates/shoppr-backend/src/lib.rs
Why:
- the module docs explain what the platform already provides
- the backend API docs explain where customer-owned validation and policy belong
- the Shoppr files show the account flow as customers and operators actually see it
If You Are Changing Admin Resources
Look at these docs first:
website/docs/reference/modules/admin.mdwebsite/docs/reference/modules/cms.mdwebsite/docs/reference/modules/commerce.md
Then look at these Shoppr files:
apps/shoppr/templates/admin/dashboard.htmlapps/shoppr/templates/admin/nav.htmlapps/shoppr/templates/admin/audit.htmlapps/shoppr/templates/cms/pages.htmlapps/shoppr/templates/commerce/catalog-admin.html
Why:
- the module docs explain the admin resource contracts
- the Shoppr templates show the checked-in operator shell, tables, actions, and audit surface
If You Are Changing Jobs, Webhooks, Or Integrations
Look at these docs first:
website/docs/reference/linked-rust-hook-apis.mdwebsite/docs/reference/wasm-host-apis.mdwebsite/docs/operations/jobs-and-schedulers.mdwebsite/docs/operations/webhooks-and-integrations.mdwebsite/docs/reference/modules/commerce-payments-stripe.md
Then look at these Shoppr files:
apps/shoppr/crates/shoppr-backend/src/lib.rsapps/shoppr/templates/commerce/checkout.htmlapps/shoppr/templates/commerce/checkout-confirmation.html
Why:
- the docs explain which integration and background seams are framework-owned
- the Shoppr files show how customer-facing pages reflect those flows honestly
If You Are Changing Local Or Production Runtime Shape
Look at these docs first:
website/docs/reference/platform-config.mdwebsite/docs/reference/environment-variables.mdwebsite/docs/operations/build-and-deploy.mdwebsite/docs/operations/configuration-and-secrets.mdwebsite/docs/operations/database-migrations.mdwebsite/docs/operations/cache-tls-cutover-and-rollback.md
Then look at these Shoppr files:
apps/shoppr/platform.dev.tomlapps/shoppr/platform.tomlapps/shoppr/docker-compose.ymlapps/shoppr/Dockerfile
Why:
- the docs explain the runtime contract
- the Shoppr files show the current customer-root deployment shape in a real app
Keep The Ownership Boundary Straight
If you are unsure where a change belongs, use this rule:
- if it is product policy, account logic, booking validation, or entitlement logic, start in the customer backend crate
- if it is HTML structure or customer-facing copy, start in templates
- if it is admin presentation, start in admin templates
- if it is jobs, webhook handling, or integrations, start in linked backend hooks and the relevant operations/reference docs
- if it is core module behavior, check the official module docs before adding customer code
That is the same boundary the tutorial has been teaching all the way through.
Final Checkpoint
Run the app one last time:
docker compose up -d
cargo run -p tutorial-app-bin -- validate
cargo run -p tutorial-app-bin -- serve
Open and verify:
/The branded shell, CMS content, and navigation still render./accountThe account and entitlement surfaces still work./adminThe operator shell still renders.- one integration-backed or job-backed flow The request path and follow-up path still agree.
If that all works, the tutorial is no longer just a sequence of chapters. It is now a map of the actual code and docs you need to keep building.