Change-Request Template
How to describe a site change so you get what you meant. Four elements do the work: where, what to copy from, the actual content, and what not to touch.
Syntax
tenant-onboarding
[what and where — the route or page]
[what to model it on — an existing page, so styling matches]
[the actual content, pasted]
[navigation and internal links to add]
Don't change any other page.Parameters
| Parameter | Type | Description |
|---|---|---|
| where | route | The exact path. "Add a gutter page" leaves the location to guesswork. |
| model | reference | Name an existing page to copy structure and styling from. |
| content | text | Supply it. Asking the change loop to also invent the copy merges two jobs. |
| do-not-touch | constraint | Prevents a helpful tidy-up you did not ask for. |
Example
tenant-onboarding
Add a new service page for gutter cleaning at /services/gutter-cleaning.
Use the same layout as the existing pressure washing service page —
same section order, same styling, same call-to-action component.
Content: [paste the copy you wrote earlier]
Add it to the services navigation menu, positioned after pressure
washing. Add a link from the pressure washing page's "related
services" section.
Don't change any other page.