Private working copy
Not shown in public archives. Use it while gathering content and images.
This is the complete day-to-day guide for adding and updating projects, articles, events, media, reviews and promotions—without changing the website design.
All admin links use the current website domain and will continue to work after the domain migration.
Try “gallery”, “category”, “YouTube”, “expiry” or “restore”.
Use the WordPress dashboard for content. Keep design, templates, menus and curated pages out of the day-to-day editing workflow.
This sequence prevents nearly every avoidable mistake. A Draft is private. Publish makes an item eligible to appear on the live website immediately.
They were captured during a controlled end-to-end test. All example items, categories, tags and test uploads were removed afterwards. The staging hostname shown in a few images will change during migration; use the root-relative links below instead of typing that hostname.
Not shown in public archives. Use it while gathering content and images.
Eligible for the public archive, filters and detail page according to that content type.
Removes the public item but keeps it available in Trash for restoration.
Irreversible. Never permanently delete shared Media Library files without checking usage.
Projects power the Portfolio archive and individual project pages. They do not automatically replace the curated project cards on the homepage.
The site contains a large legacy/migration draft inventory. Many drafts have incomplete galleries or no Featured Image. Review each one individually.
| Field | What to enter | Where it appears |
|---|---|---|
| Tags | Comma-separated text. Put the broad type first: Residential, Landed or Commercial. | All pills on detail; first two on cards; search and Similar Projects. |
| Housing Type | For example: 4-Room BTO, Executive Apartment, Condominium. | Project facts and Portfolio search. |
| Homeowners | Short description such as “Family of 4” or “Couple”. | Project facts and search. |
| Price Range | Follow the established format, for example “~ $100,000”. | Project facts and search. |
| Subtitle / Pull Quote | One concise sentence that introduces the design. | Main project heading and search description. |
| Hero Description | Plain text. Separate paragraphs with a blank line; do not add HTML. | Project story and Portfolio card/search copy. |
| Project Gallery | Choose and order the final project images. | Masonry gallery and lightbox. |
Residential, Balinese, Modern, ResaleThey are comma-separated words stored on each project. A new word becomes searchable but does not automatically create a visible filter button. Filters are single-select, not additive. Request a developer for a new permanent chip.
Posts create the Blog archive, article pages, category archives and editorial content.
Place each prefix at the beginning of its own plain paragraph. The exact patterns below become designed highlights, takeaways and FAQs.
| Prefix | Use | Example |
|---|---|---|
| H: or HIGHLIGHT: | Highlighted pull quote. | H: Good design begins with how you live. |
| K: | Key Takeaways card. Keep consecutive K: paragraphs together. | K: Plan storage before choosing finishes. |
| F: then Q: | FAQ question followed immediately by its answer. | F: How long does renovation take? Q: Timelines vary by scope and approvals. |
The public search checks article titles and body copy. A search replaces the normal Featured Article with matching results and keeps the search term when moving between result pages. Categories remain the fastest one-tap filters.
Categories create visible Blog filters. Tags organise content and create direct archives, but are not shown in the current Blog design.
Do not rename established slugs casually. Existing links may need a redirect. Category filters appear only after at least one published post uses them; Uncategorized is intentionally hidden.
Use a Blog Tag for a cross-cutting topic that does not need a visible Blog filter, such as a neighbourhood, material or campaign. Its archive is /tag/tag-slug/. Do not confuse Blog Tags with the Portfolio project’s comma-separated Tags field.
The Event Date controls Upcoming versus Past placement. The detail page uses the website’s built-in registration form.
| Field | Front-end behavior | Client guidance |
|---|---|---|
| Event Date | Controls Upcoming/Past and sort order using Singapore time. | Always set it. Blank can incorrectly remain Upcoming and display TBA. |
| Event Time | Displays on archive and detail. | Include AM/PM or a clear time range. |
| Location / Venue | Displays on archive and detail. | Use “Venue | address” consistently. |
| RSVP Button Label | Changes archive button text. | Examples: Register now, View details. |
| RSVP Button URL | Saved but not used by the designed pages. | Do not rely on it. The card opens Event detail; detail uses the built-in form. |
Past cards are muted and lose the archive action button, but the detail page can still show its registration form. Unpublish it or request backend help if registration must close.
Use Media Items for YouTube videos, press features and tours on the public Media archive. This is different from WordPress’s image/file Media Library.
Media Items are public video/press/tour cards. Media Library stores uploaded images and files. Check the URL: Media Items use post_type=media; the file library uses upload.php.
Cards are designed to open the external video. If the URL is blank or invalid, the public single URL safely returns visitors to Our Media instead, so always test the intended video before publishing.
Reviews create testimonial cards on the Reviews archive. The cards intentionally do not link to individual Review pages.
Verified five-star Google reviews use the actual reviewer name, the full written review as the body, and GOOGLE REVIEW as the Topic. Never create another Review post type. Use the numbered pagination at the bottom of Reviews to check older cards after a large import.
Publishing a Review updates the Reviews archive only. It does not automatically insert the Review into the homepage Client Stories marquee.
Featured Image, Excerpt, Categories and Tags are not used by the designed Reviews archive. Focus on Title, body testimonial, Reviewer Name and Topic.
Promotions create offer cards and designed offer pages. Dates are display text only; publishing and expiry are managed manually.
| Field | Use | Important behavior |
|---|---|---|
| Chip Label | Short status or offer type. | Appears on archive and detail. |
| CTA URL | Detail-page button destination. | Blank falls back to Contact; archive “View offer” always opens Promotion detail. |
| Period Start / End | Display-only offer dates. | No automatic start, expiry or scheduling. |
| Subtitle | One-line offer explanation. | Used on detail and description, not archive card. |
When one ends, change it to Draft or Move to Trash. Updating Period End does not unpublish it. New Promotions also appear at the bottom because the archive currently uses oldest-created first.
The Media Library stores reusable images and files. Uploading a file does not automatically place it on any page or content item.
Chosen once per post/project. It is not automatically the first gallery image.
Removing an image from a gallery does not delete it from the Media Library.
An attachment can be reused across Home, project galleries, Posts, Events and Promotions. Permanent deletion can break every reference. Removing it from one gallery is safer.
The main Pages are managed deployments. The normal WordPress Page editor is not the source of their visible design.
Home, About, Contact and other managed Pages use isolated Reputifly deployments. Normal body edits may do nothing or create an unstyled page. Navigation and page-design changes remain developer-managed.
| Action | Archive/detail update? | Homepage update? |
|---|---|---|
| Publish Portfolio Project | Yes: Portfolio archive and project page. | No: project cards are curated. |
| Publish Blog Post | Yes: Blog and article page. | No: Journal cards are curated. |
| Publish Review | Yes: Reviews archive. | No: Client Stories are curated. |
| Publish Event / Media / Promotion | Yes: its own archive/detail behavior. | No unless a developer places it. |
Send the developer the exact public item link, section name, what should be replaced and desired order. For example: “On Home → Journal, replace card 3 with [article URL]. Keep the current design and order.”
Section: Home → Our Portfolio
Replace: card 4
With: /portfolio/project-slug/
Keep: current image crop, card design and mobile orderThe composition uses a deliberate card count, order and testimonial sequence. Automatically inserting the newest item would change that design, so new content is not pulled into Home without explicit selection.
Check status, practical fields and the correct public location before changing anything else.
Confirm the comma-separated Tags spelling and capitalisation. New Tag text becomes searchable but does not create a visible chip. Send the desired chip and at least one project link to the developer.
A non-empty Blog Category should create a filter automatically. Confirm at least one Published Post uses it, that it is not Uncategorized, and that you are viewing page one of Blog. Refresh once.
Check Event Date. Upcoming/Past is calculated from that field using Singapore time—not the WordPress publish date. Correct it, Update and verify Events again.
This is expected because Period Start and End are display text. Change the Promotion to Draft or Move to Trash, then verify the archive. Do not permanently delete it if the record may be needed.
Send the exact admin edit link, public URL, screenshot, device/browser and expected result. Never send passwords, one-time codes or private customer information.
Use this final check every time. Selections stay only in this browser and are not submitted anywhere.
Content is managed in WordPress; design, templates, navigation, permanent Portfolio filter chips and curated homepage placements stay developer-managed.























