A courtyard home project page should explain which rooms face the outdoor space, which have documented connections, and what approved views show those relationships. Build the story from a room-edge-to-view matrix. Separate a view from an entrance, keep sensitive details private, and leave daylight, comfort and drainage claims to verified project review.
Which relationship should your courtyard story explain?
Start with the rooms around the courtyard. Choose the relationship that the approved project material can explain most clearly. A living room may face the outdoor space without providing its entrance. A dining area may appear beside it in a drawing without an approved photograph showing the connection. Record those differences before writing.
Define your page question in plain language: which surrounding rooms relate to this outdoor space, and how? Avoid using the courtyard as a reason to describe the entire house. Give readers enough orientation to understand the published views. Leave the wider project narrative on its own page.
The builder website article library connects this narrow brief to other public page decisions. Use the courtyard story where a room list or isolated exterior photograph leaves the layout unclear. The article's proposed matrix is an editorial tool, not a design assessment.
Set the public boundary at the start. Decide which room labels, drawing excerpts and view directions the project owner has approved for release. Keep detailed entry arrangements, security equipment and private household routines out of the story. If a safe excerpt cannot explain the relationship, describe it in approved text.
How do you distinguish a view from an entrance?
Use separate fields for adjacency, view and access. Adjacency records where a room sits in the approved drawing. View records what an approved image or drawing supports about the room's visual relationship. Access records a documented connection. Do not fill one field from another.
For each room edge, ask what the supplied material establishes. A window in a photograph can support a limited description of that photographed view. It does not establish a walk-through route. An opening on an earlier drawing needs a version check before you describe the completed project.
| Room edge | Relationship to verify | Approved source | Public view | Unresolved item |
|---|---|---|---|---|
| [Public room label] | Faces courtyard | [Drawing version and reviewed image] | [Approved frame identifier] | [Any unconfirmed viewing claim] |
| [Public room label] | Documented connection | [Reviewed public drawing] | [Approved text or cropped frame] | [Version or release question] |
| [Public room label] | Adjacent without confirmed access | [Drawing version] | [Approved orientation view] | [Connection remains unknown] |
| [Outdoor edge label] | Extent of published story | [Public release decision] | [Approved boundary] | [Private detail to exclude] |
Replace the placeholders with confirmed entries before publication. Keep unresolved notes in the internal worksheet. Publish only the relationships that survive the source and release checks. The matrix should make omissions visible to your editor without exposing private information to readers.
The plan library guide covers how to explain a starting design and its status. Use that broader destination for plan comparison. A courtyard project story should explain the documented interpretation shown here, without implying the layout is currently offered elsewhere.
If your records confirm no courtyard entrance, avoid guessing one from furniture placement or a photographer's position. Ask the project reviewer for the missing information. You can publish a story about surrounding views while leaving the access description out.
Which claims should stay separate from the plan relationship?
Keep daylight, temperature, drainage and privacy in a separate claim register. A room arrangement does not supply the evidence needed for those conclusions. Do not describe a courtyard as brighter, cooler, dry or private because the plan shape suggests that story to the writer.
Privacy needs particular care in public wording. Your decision to withhold private details is an editorial boundary. It does not establish that the physical courtyard provides privacy. Describe only approved visible relationships. Leave performance and technical conclusions to the responsible qualified reviewer.
Use literal language where possible: the approved drawing places the dining room along one courtyard edge. That is a bounded plan statement. The dining room enjoys perfect daylight is a different claim. Omit the second claim when the packet contains only a drawing and selected photographs.
Keep the courtyard name project-specific as well. Confirm the term used in the approved project material. Do not rename a patio, garden or light well for editorial effect. If the team cannot confirm the public term, hold the title and request a decision before publishing.
Scope belongs in the same review. Separate the building work from planting, furnishings and later alterations when the records support that distinction. If a visible element's source is unknown, avoid taking credit for it. Your page can explain room relationships without claiming every element in the scene.
How do you choose views without exposing private details?
Give each proposed view a buyer question and a release decision. Ask whether the frame explains a room relationship that the text names. Then check the complete frame for information outside that purpose. Use only crops that remain accurate and have approval for public use.
- Select the room relationship from the completed matrix.
- Choose the approved drawing excerpt or photograph that explains it.
- Check that the image version matches the text source.
- Review the frame for private details and sensitive entry information.
- Confirm publication permission for the image or drawing.
- Write the caption and text alternative for that image's purpose.
- Read the finished section against the approved public boundary.
Do not publish a detailed route simply to prove that a connection exists. A reviewer can confirm the source internally while approving a less detailed public description. If the image reveals more than the approved story needs, hold it and request a suitable alternative.
For informative images, W3C advises text alternatives that convey the image's meaning. Its supplementary-image example considers what adjacent text already explains. Use that guidance to describe the selected view's purpose. It does not substantiate a courtyard's features or performance. See W3C's informative image guidance, Overview and Example 2.
The project gallery guide explains captions across a whole project. Here, keep the caption attached to one room edge, one supported relationship and one approved view.
What should a copyable courtyard page brief contain?
Copy this brief into the project's working content record. It is a proposed editorial format. The blank fields do not imply that a project has a particular feature. Keep the source record beside the draft so a reviewer can trace each public statement.
Courtyard project page brief
Approved public project label:
Page question:
Confirmed outdoor-space term:
Public drawing version:
Drawing publication permission:
Room-edge-to-view matrix location:
Confirmed surrounding room labels:
Confirmed relationships for publication:
Entrance description approved for public use:
Views approved for public release:
Scope labels and exclusions:
Private details excluded:
Technical claims omitted or separately reviewed:
Unknown facts and responsible reviewer:
Final caption and image approval:
Review date and next update trigger:
Write unknown beside an unresolved fact. Do not leave a blank that a later editor may interpret as permission to improvise. Separate a source question from a release question. The project team may know the entrance arrangement while choosing not to publish it.
Use the custom builder website page guide to connect the brief to your wider project content. A courtyard section can live within a complete project page when that gives readers enough context. A standalone story still needs an accurate relationship to the main project.
The Owned website stage explains how public pages sit within the website you control. Include this brief and its review status in the content handoff. Keep restricted source records in the appropriate project system.
Set an update trigger when you approve the brief. A new drawing version, replacement image or changed publication permission should prompt another review. The trigger gives the next editor a specific reason to reopen the matrix instead of treating published copy as permanent evidence.
What would a fictional courtyard page brief produce?
This example is fictional and unnamed. Assume an approved public drawing places living and dining rooms along separate edges of a courtyard. One reviewed image shows the living-room view. A connection is documented internally, but its detailed location is withheld from the public story. No performance evidence is supplied.
The courtyard organizes the relationship between the living and dining spaces in this example project. The approved drawing shows both rooms facing the outdoor area. The published photograph explains the living-room view. It does not show every surrounding room or entrance.
A connection to the courtyard is documented in the project record. Its detailed arrangement is outside this public brief. The supplied material does not establish daylight levels, temperatures, drainage performance or physical privacy. Planting scope and current project status remain unknown.
For this fictional brief, the dining-room edge has a drawing source but no approved image. The writer can describe the supported relationship without inventing a view. The reviewer can request another image later, subject to permission and the same public boundary.
Compare the screened porch project page guide when your story follows one indoor-to-outdoor route. The courtyard matrix serves a different question: how several room edges relate to one outdoor space.
What else should you check before publishing a courtyard story?
Does a room facing a courtyard necessarily have an entrance?
A courtyard view does not establish an entrance. Check the approved drawing and project review before describing access. Keep adjacency, view and access as separate entries in the page brief.
Can a courtyard floor plan support daylight or temperature claims?
Keep daylight and temperature claims out of a courtyard page supported only by a floor plan. Describe documented room relationships. Send performance questions to qualified project review with relevant evidence.
How much entrance detail belongs on the public page?
Publish only the courtyard entrance description approved for public use. Keep sensitive route details and security information out. Use a bounded text explanation when the available image exceeds the approved public story.
What happens when courtyard planting scope is unknown?
When courtyard planting scope is unknown, omit credit and inclusion claims about the planting. Explain the supported room relationships instead. Keep the scope question in the internal brief for the responsible reviewer.