Yes — now that you have a working layout, that should become the locked master page for the rest of the site. Paste this to Trae exactly: Trae Task: Create Locked Master Page and Roll It Out Sitewide We now have an approved working page layout. Use it as the master page for the remaining public pages on the site. Main objective Duplicate the approved working layout and make it the required standard for: homepage-related public pages all service pages all remaining public content pages All public pages must carry: the same top navigation/header the same sticky nav behavior the same footer the same clean content container/layout 1. Create the locked master structure Create these files if they do not already exist: /components/site-header.html /components/site-footer.html /templates/master-page.html /templates/service-page.html /assets/css/site-header.css /assets/css/site-footer.css /assets/css/site-layout.css /assets/css/service-page.css /assets/js/site-header.js Required rule Do not build new page-specific headers or footers anymore. Header and footer must only exist in the shared component files. 2. Master page requirements Use the currently approved working page layout as the master reference. The master page must include: Header same approved navigation bar same sticky behavior same logo placement same nav links same CTA buttons same mobile menu behavior Main content area clean centered layout controlled max width consistent spacing between sections no broken wrappers no overlapping elements no random floating buttons or leftover legacy boxes Footer same approved footer on all public pages no Admin Login no Customer Portal no duplicate footer markup 3. Build one general master page template Create /templates/master-page.html using this structure:
4. Build one service page template Create /templates/service-page.html using the same shared header and footer. Service pages must include: shared sticky header service hero/content section clean readable content area two-column “issues we repair” section where appropriate nearby service area/city links section if needed shared footer Important Do not allow service pages to have: separate top bars Customer Portal buttons floating in the page Free Inspection mini boxes custom headers custom footers stretched or broken layouts 5. Apply master page to remaining pages Update all remaining public pages so they use the same master shell: shared header shared footer same page container same spacing rules same typography rules This includes all service pages. 6. Clean content placement For all pages: keep content inside a clean centered container maintain consistent padding left/right maintain consistent section spacing ensure content sits properly between header and footer remove layout junk from previous versions Use a single sitewide container rule such as: .container { width: min(100% - 40px, 1100px); margin: 0 auto; } And global page rules like: html, body { margin: 0; padding: 0; min-height: 100%; } body { display: flex; flex-direction: column; min-height: 100vh; } main { flex: 1; } .page-main { width: 100%; } .page-content { padding: 48px 0 64px; } 7. Lock the shared components At the top of the shared files, add these comments. site-header.html site-footer.html master-page.html service-page.html 8. Rollout process Do this in order: Create locked master page template Create locked service page template Confirm homepage still works Update one non-homepage page using master template Update one service page using service template After visual approval, roll out to all remaining pages Do not do another uncontrolled broad refactor. 9. Final QA requirements Before marking complete, verify: same sticky header on all public pages same footer on all public pages no duplicate nav bars no duplicate footers no broken page spacing no leftover legacy CTA boxes no Admin or Portal links in public footer all service pages use the same clean layout mobile layout works across all pages all internal links still work Do not mark complete from code review alone. Verify visually in browser. 10. Important rule From this point on, header and footer changes must only be made in the shared component files, never inside individual pages. If you want, once Trae does this, send me one regular page and one service page screenshot and I’ll check whether it truly followed the master layout. St. Paul RV Roof Repair | Mobile RV Roofing Twin Cities

Minnesota Mobile RV Roofing

RV Roof Repair in St. Paul, MN

RV Roof Renewal provides expert mobile RV roof repair and replacement in St. Paul and the East Metro. We provide lifetime leak-free repairs and replacements right in your driveway or storage lot. Stop leaks forever without yearly caulking.

RV roof issues we repair include:

  • Roof leaks around vents and seams
  • Cracked or failing sealant
  • Water intrusion and soft spots
  • Storm and hail damage
  • Full RV roof resealing and restoration
  • Tears, holes, and membrane separation

Serving St. Paul & Surrounding Areas

We proudly serve RV owners in St. Paul and the East Metro including:

St. Paul Woodbury Maplewood Oakdale Stillwater White Bear Lake Roseville Little Canada