Auth Scaffold & Source Ownership
Find the account pages, wrapper components and mock records in an Auth-enabled project.
Auth scaffold and source ownership
The project creator offers Developer Auth Sandbox as an optional feature. It adds Auth integration and account UI resources when selected; installing the Auth package into an existing theme does not automatically create those pages.
Resource Purpose LoginPage.tsx / login-form-wrapper.tsx Login entry and interface SignUpPage.tsx / signup-form-wrapper.tsx Registration entry and interface DashboardPage.tsx / dashboard-view-wrapper.tsx Account content and protected-page example VerifyEmailPage.tsx / verify-email-view-wrapper.tsx Verification-link destination ForgotPasswordPage.tsx / forgot-password-form-wrapper.tsx Recovery request ResetPasswordPage.tsx / reset-password-form-wrapper.tsx New-password destination cms/users, cms/roles, cms/sessions Mock account, capability and session records cms/email-logs Preview messages and account links |
|---|
The source resource catalog is under packages/compiler/templates/auth/ in the framework repository, with starter/project-template copies. The project creator materializes source pages/components and mock configuration; inspect your generated project's files rather than editing the catalog to customize one theme. Mock records can use TypeScript or JSON according to that project's setup.
The current project creator copies the five public account pages (login, signup, verification, recovery and reset). DashboardPage is a catalog example; do not assume it creates a dashboard route automatically.
The starter wrappers are theme source, while @forgewp/auth provides reusable actions/primitives. Edit page layouts and wrapper UI in the theme. Edit account policy in wp.config.ts or installed settings as described in the configuration reference. Do not edit exported PHP or .forgewp/ caches to make source changes.
Check the scaffold's policy explicitly
An example project can choose verification and role defaults for its demonstration. Review those settings, actual routes, and generated Page assignments before adapting it for another site.