What content should a property development website include?
A development website should make a project understandable without turning provisional information into certainty. Give every content item a source, status and approval owner.
The short answer
Gather a checked project introduction, cleared visuals, property types, dated availability and an identified contact. Record the source and approver for each item. Bayhaven structures this presentation; missing facts need confirmation before publication, and options require an accepted scope.
Start with a reference brief
Create one project brief: name, location suitable for publication, project owner, introduction, contacts and milestones you want to explain. Distinguish confirmed facts, presentation ideas and provisional details. Attractive writing should not conceal a date or characteristic that has not been validated.
Use this brief as the reference for pages, translations and updates. If two documents disagree, name the person who resolves the conflict before drafting. The website presents a specific development; a corporate page covering a developer’s wider business serves a different purpose and cannot replace this project brief.
Organise visuals and documents
Group images by use: overview, surroundings, illustrative interiors, plans and useful details. Record origin, permission to publish and intended captions. Clearly identify renderings or illustrations when they do not show a completed place. Bayhaven demonstrations are fictional and do not represent available client developments.
For each file, check the approved version, date and any private information. Use a readable filename and explain the document in its link label. W3C recommends text alternatives suited to an image’s role. A useful description helps more than a filename or repeated search terms.
- Keep original files and identify public versions.
- Document origin and publication permission.
- Distinguish illustrations from real photographs.
- Prepare useful captions and descriptions.
- Have plans and files checked by their owners.
- Remove personal or internal material from public versions.
Structure property types and availability
Use a stable reference for every property type or unit, according to the agreed presentation. Gather checked characteristics, units and sources. A tracking table helps avoid copying a floor area or status from an outdated file. It also supports consistent French and English facts.
Availability changes during sales. Name who confirms it, when it was checked and how corrections are requested. If a price, plan or schedule is unconfirmed, flag it for preparation instead of inventing a value. The following table is a working checklist, not a list of units offered for sale.
| Item | Source to gather | Owner / status |
|---|---|---|
| Project introduction | Reference brief and approved text | Project owner / confirmed or review needed |
| Visuals | Files, captions and rights | Communications owner / public version |
| Types and floor areas | Consistent table and plans | Project manager / checked facts |
| Availability | Dated sales status | Sales team / verification date |
| Documents | Cleared version and date | Document owner / publication permission |
| Contact | Details and enquiry destination | Sales team / check planned |
Plan for visitor questions
Visitors should understand the project, find relevant information and know how to ask a question. Link enquiries to the development or property type where included in scope. Prepare public contact details and identify the team that will respond. A well-designed form does not establish operational receipt: checking delivery is a launch step to arrange.
Entirely fictional example: in “Demo Gardens”, a property type has reference T2-DEMO and availability remains unconfirmed. The internal brief flags this gap; the public page does not call it available. This illustrates validation without a real address, price, unit or schedule.
Approve the version and plan updates
Review the preview against your reference table. Check links, images, statuses and translations. Collect corrections, then approve the exact version for publication. Approval of the visual direction is distinct from approval of project facts. Domain and publication checks remain necessary after your agreement.
Finally, set an update rhythm and name who sends changes. Bayhaven is a managed website template for a development. Appointments, connections and other options are proposed according to need, with compatibility and launch preparation to confirm. This guide prepares content; project-specific contractual, legal or tax information needs review by its competent owners.
Sources and scope
An editorial preparation method based on Bayhaven and VITRIMO’s approval workflow. W3C provides the image text-alternative reference. This guide gives no tax advice or legal approval of a development.
Prepare a Bayhaven brief
Start with your project brief and confirmed content list. Flag outstanding details to define the work.