Five pages no longer need an NgModule

// comparison-page.module.ts
@NgModule({
  declarations: [ComparisonPageComponent],
  imports: [
    CommonModule,
    ComparisonPageRoutingModule,
    MarketingPageSharedModule
  ],
  schemas: [CUSTOM_ELEMENTS_SCHEMA]
})

// comparison-page-routing.module.ts
const routes = [
  { path: '', component: ComparisonPageComponent }
];

// component
@Component({
  selector: 'app-comparison-page',
  standalone: false
})

// component
@Component({
  selector: 'app-comparison-page',
  imports: [
    CommonModule,
    MarketingPageSharedModule
  ]
})

// route
{
  path: 'topfan-vs-patreon',
  loadComponent: () =>
    import('.../comparison-page.component')
      .then((m) => m.ComparisonPageComponent),
  data: { comparisonSlug: 'topfan-vs-patreon' }
}

- loadChildren: () => import('./.../link-in-bio-fan-preview.module').then(m => m.LinkInBioFanPreviewModule)
+ loadChildren: () => import('./.../link-in-bio-fan-preview.routes').then((m) => m.LINK_IN_BIO_FAN_PREVIEW_ROUTES)

Behavior change /creators/login used to render the login page

CreatorsHomeModule imported AuthModule and SetupProfileModule. Neither exported anything the template used. But both import their own routing modules, and RouterModule.forChild registers routes through a multi-provider. When the router lazy-loaded CreatorsHomeModule, it collected every route in that module's injector. So the real route table under /creators looked like this:

''  CreatorsHomeComponent          // first in the list, so /creators still worked
''  AuthLandingComponent           // from AuthRoutingModule
    'login'          LoginComponent
    'signup'         SignUpComponent
    'verify-by-otp'  VerifyByOtpComponent
    ...
''  SetupLandingComponent          // from SetupProfileRoutingModule
    'setup-profile'    SetupProfileComponent
    'content-creator'  ContentCreatorSetupComponent
    'confirm-creator'  ConfirmYourCreatorComponent

The same list was under /creator. I'm fairly sure nobody meant this. Nothing in the code navigates there. The signup button goes to auth/creators-signup from the root, and Application.confirmCreator is an absolute /edit-preference/... path. prerender.routes.txt and the sitemap don't list any /creators/* URL either.

A standalone component's imports don't feed the router, so these routes are gone now. /creators/login falls through to the profile sub-page route and renders app-sub-page-view. If someone bookmarked one of those URLs, that's what they'll see.

Same Route data lookup. The marketing and comparison components read marketingSlug and comparisonSlug by walking up route.parent until they find it. Before, the data sat on the parent of the component's route. Now it sits on the component's own route. The loop finds it one step earlier.

Same Case-insensitive URLs. withCaseInsensitivePaths turns each path into a matcher. A route without a children array counts as a leaf and has to match the whole URL. loadChildren routes never had a children array either, so /Athletes matches and /athletes/extra doesn't, exactly as before.

Same Modal service. An earlier commit on this branch fixed a bug where two BsModalService instances fought over one dialog. I checked ngx-bootstrap 21's ModalModule. It provides nothing, so the service still comes from the root injector. Dropping ModalModule from creators-home can't create a second instance.

Same Initial bundle. I built the base branch and this branch with the QA config. Both report 12.30 MB initial. The routes still use dynamic import(), so none of these pages moved into the first load.

High Creators home, /creators and /creator

The old module imported FormsModule, NgSelectModule, ModalModule, AccordionModule, and NgMultiSelectDropDownModule. The template uses none of them, so the component doesn't import them. Modals opened through BsModalService don't need ModalModule in the opener, but clicking each one is the only real proof.

• "Apply now" opens the creator requirements modal. Check all three copies, in the marketing section, the button row, and the bottom of the page.
• "Request demo" goes to the request-demo page.
• "Watch video" opens the video player modal and plays.
• On the non-marketing layout, the IVS player at the top loads and plays.
• The book-demo form modal opens, submits, and shows the thank-you modal. The thank-you "Close" button closes it.
• ?watch_demo_video=true, ?apply_now=true, and ?watch_sizzle_video=true each open their modal on load, then disappear from the URL.
• ?key=<creator username> shows the referee card with the creator's photo and name. Clicking the photo opens their profile.
• The FAQ accordion expands. The testimonial cards scroll and expand on hover.
• On a white-label domain, /creators still redirects to the white-label home.
• Try /creators/login. It should now render the sub-page view, not the login page. That's expected. Flag it if anyone depends on the old URL.

Medium Link in bio, /bio/:userName

Use a creator whose link-in-bio has at least one of each product type. Each type renders through a different component, and a missing import shows up as a blank tile.

• Banner, profile photo, name, tick icon, and bio text all show. Clicking the name or photo opens the profile.
• Social icons show and open the right links in a new tab.
• A specific store item renders its card and opens on click.
• A portfolio item renders. Clicking an individual item opens it with the player.
• A feed content item renders and opens its modal.
• A general action item renders the monetize carousel.
• A welcome video item renders its preview.
• External links open in a new tab.
• The footer says "Powered by" normally and "Get your own platform" when the bio has a referral link.
• Check a mobile width. The layout switches to the mobile product list.
• /bio/<unknown user> goes to not-found. /bio/a/b also goes to not-found, through the wildcard in the new routes file.

Medium Sub-pages, /:id/:subPageUrl and white-label roots

• On the main site, open a creator's published sub-page at /<username>/<sub-page>. The loader shows, then the page renders with the cover page header and footer.
• Add ?preview=true to an unpublished sub-page while logged in as its owner. It renders the draft.
• On a white-label domain, open /<sub-page> with a single segment. This goes through whiteLabelRootSubPageMatcher, which returns nothing on the main site, so you can only test it on a white-label build.
• On a white-label domain, /<username>/<sub-page> redirects to /<sub-page> and keeps the query string. This check reads the id param through route.pathFromRoot, and that param now sits on the component's own route.
• On a white-label domain, a single-segment slug that isn't a sub-page but is a username goes to that profile. Anything else goes to not-found.

Low Marketing pages, 14 slugs

• Open a few, for example /home, /athletes, and /music-artists. Sections render, and the animated counters and scroll-in effects run.
• Mixed case still works, for example /Athletes.
• Reach one from another page without a full reload, for example by following an in-app link, and check it renders.
• On a white-label domain, they redirect to the white-label home. In the installed PWA, logged out, they redirect to the referrer login.

Low Comparison pages, 7 slugs

• Open /topfan-vs-patreon and one more. The comparison tables and hero render with the competitor logo.
• Click through from the header's comparison list. That's the client-side lazy-load path.

Low Prefetch script

• Run npm run prefetch-pages-qa. The two generated route files should still say loadComponent and import the .component files. The only diff should be the timestamp and any slugs the API added or removed.
• The next QA deploy builds cleanly. That run is the first time the script output meets the build.