Skip to content
Sign inJoin waitlist

Making it yours — Goeboek AI Prompts

After the last prompt you have the Goeboek site with its demo text and grey placeholder photos. Everything a visitor reads lives in src/content/, so most changes are edits to text files — or a sentence to your AI tool.

What Where
Agency name (the “ | Goeboek” ending of the browser titles), Home’s browser title and description, site address src/content/site.json → site
The logo: its mark, its two lines (“Goeboek” / “properties”) and its name for screen readers src/content/site.json → site.logo
Menu, the header buttons (“Add Property”, “Contact us”), the phone menu’s “Menu” / “Close”, the contact details (address, phones, e-mail, opening hours), the social links, the footer src/content/site.json (navigation, headerActions, menu, contact, socials, footer)
Copy shared by several pages: the call to action “Ready to Make Your Move?” (Home and About), the listing filter, the property card’s labels (“For Rent”, “For Sale”, “m2”) src/content/sections.json (cta, filters, propertyCard, testimonial)
The copy of each page src/content/pages/<page>.json (home.json, about.json, contact.json, …); the five listing pages share properties.json, the two thank-you pages success.json
Properties, agents, locations, categories, posts, testimonials src/content/collections/<name>.json

Change the text between the quotes and keep the field names. Or ask your tool: “Change the agency name to Northgate Homes and the e-mail to hello@northgate.com in site.json.” Set site.url to your domain before you publish — the sitemap and share links are built from it.

The demo’s address, phone numbers and e-mail (hello@example.com) are placeholders: replace them in site.json → contact (the footer and the Contact page read them from there). The name Goeboek is in site.json (site, the logo, the footer text and the copyright line) and in many texts: ask your tool to search src/content/ for “Goeboek” to find them all. “Goeboek by Marcframe” in the copyright line can stay or go. The social links open the networks’ home pages: point them to your own profiles, and remove the ones you don’t use.

Each property in collections/properties.json has:

  • slug — its address (/property/marble-house), unique; title; propertyId — the reference shown on its page and filled in the tour form;
  • for — sell or rent; price — a number in US dollars (printed “$550,000”); duration — “/month” after a rent’s price on its page;
  • category, location and agent — the slug of an item in categories.json, locations.json and agents.json;
  • address — shown on its page and used for “Show on map” (a map search in a new tab);
  • image and gallery — the main photo and four more, each with its alt text;
  • excerpt — the card’s text and the page’s description for search engines;
  • description, features — text blocks; video — a YouTube link;
  • details (size in m2, bedrooms, bathrooms, floor, additional space, furnishing, ceiling height in m, construction year, renovation) and utility (heating, air condition, fireplace, elevator, ventilation, intercom, window type, cable TV, wifi) — the rows of the two lists on its page; “-” shows a feature it doesn’t have.

To add one, copy a property, give it a new slug and change the fields. It appears on Properties and on the listing of its type, location, category and agent, gets its own page and joins the sitemap. Delete an item to remove it. Ask your tool if you prefer: “Add a property called Harbour View Loft to properties.json, for rent in Brooklyn, with the same fields as the others.”

The collection’s order is the order of the lists. Home’s hero slides through the first four properties (hero.slideshow.count in pages/home.json) and Featured Properties shows the six after them (featured.offset 4, featured.count 6). A property page shows two more in the same location (“More in Queens”) and, under it, the others of the same category and type (Related properties).

  • Agents (collections/agents.json): slug (/agent/<slug>), name, image, address, phone, mobile, whatsapp, email and bio. A property names its agent by slug; the agent shows on its cards (on hover), on its page and on the agent’s own page with all the agent’s properties.
  • Locations and categories (locations.json, categories.json): slug and name. Each gets a page (/location/<slug>, /property-category/<slug>) and a chip in the filter.
  • The last item of each — No Name, No Location, Uncategory — is an empty default kept from the original design: its page exists but is hidden from search engines (noindex in pages/properties.json) and left out of the filter. Remove them, or keep them for properties you haven’t sorted yet.

Each post in collections/posts.json has slug (/blog/<slug>), title, category (a text: “Improvement”, “Development”, “Design”), date (2024-05-16, shown as “May 16, 2024”), author, image with its alt text (the card’s photo, the page’s cover and its share picture), excerpt and body. The Blog page lists every post, newest first; Home shows the four newest (blog.count in pages/home.json). A post page shows the three newest posts and the first property in its sidebar, and up to four other posts of its category under it. There are no category pages.

The bodies of posts and a property’s description and features are blocks: { "type": "paragraph", "text": "…" }, { "type": "heading", "level": 3, "text": "…" } and lists ({ "type": "list", "ordered": false, "items": [ … ] }). In any text, **…** is bold.

Each testimonial in collections/testimonials.json has slug, name, photo, rating (a number such as 4.4, shown beside a star) and quote. Home’s hero steps through the first five (hero.testimonials.count); About lists them all, six at a time with “Load More” (four below 1200 px).

The pack uses placeholders; each shows the size its photo is designed for (for example 1024 × 644). Put your photos in public/images/ with the same file names and they replace the placeholders:

Photos Files Designed size
A property’s main photo property-<slug>.jpg 300 to 1400 wide, about 3 : 2
A property’s gallery property-<slug>-2.jpg … -5.jpg 300 to 1200 wide
An agent’s portrait agent-<slug>.jpg 400 × 504
A post’s cover post-<slug>.jpg 1400 wide
A testimonial’s photo (round) testimonial-<slug>.jpg 70 to 200 px
About: the hero and the two story photos about-hero.jpg, about-1.jpg, about-2.jpg 1920 × 1280, 1200 × 800, 1200 × 1800
The call to action cta.jpg 1920 × 1282

Photos fill their frame and are cropped, so keep their proportions close to the placeholder’s. A new photo can have any name: refer to it in the content as /images/<file>, with its alt text. In a chat builder, upload the photos and tell the tool which file names to give them. Good free sources: Unsplash, Pexels.

  • Property pages: each property’s video is a YouTube link, shown in a 16 : 9 frame. Put your own tour video’s link there.
  • Contact: the map shows the address in pages/contact.json → map.query; change it and the map moves. “Show on map” on a property page searches its address.

The logo is the round mark (public/images/logo-mark.svg) beside the name in two lines, “Goeboek” / “properties”, drawn as text so you can change it without a design tool. Change the mark’s file with site.logo.mark, the two lines with site.logo.first and site.logo.second, and site.logo.label for screen readers. Ask your tool to use your own logo instead: “Use public/my-logo.svg as the Logo, at the same height.”

The browser tab icon is public/icon.png (192 × 192) and the home-screen icon public/apple-icon.png (180 × 180), both the round mark: replace them with yours. The site has no share image of its own: a property and a post share their main photo and an agent page the agent’s portrait; the other pages share none. Ask your tool to add one if you want (public/opengraph-image.png, 1200 × 630).

The thank-you pages show success-tour.svg and success-property.svg from public/images/. The icons are in public/icons/: 22 Phosphor icons (the star, the map pin, the bed, the bath, the plus, the caret and the icons of the property details and utilities).

Prompt 1 set up the design tokens: colours (--color-ink, --color-soft, --color-grey, --color-accent, --color-line, --color-snow, the translucent blacks …), the fonts, text styles and spacing. Goeboek is black text on white with soft grey panels, black buttons that turn orange (Accent) on hover: change a token and the whole site follows — “Change –color-accent to #2F6FEB.” Keep enough contrast between the text and the page. Keep the text styles’ sizes per breakpoint unless you want a different rhythm.

The fonts are Plus Jakarta Sans (400 to 700) for every text and Inter for the upper-case buttons, chips and labels. Another font works the same way — ask the tool to load it and use it in --font-sans (or --font-ui).

To remove a page, delete it and ask your tool to take it out of the menu (navigation in site.json), the footer (footer.columns) and the sitemap. To add one — an Agents page or a privacy policy, for example — write a prompt in the style of the page prompts: list its sections and reuse the components (“a page title, then Agent cards in three columns, then the footer”), so it matches the rest, and add it to the menu and the sitemap.

The header and the footer are shared: a change to them shows on every page.