Skip to content
Sign inJoin waitlist

Goeboek documentation — HTML

Everything you need to go from the downloaded HTML folder to a published real estate site, in the order to read it.

Guide What it covers
Editing the site Opening the site, editing text, links and images, the blocks that repeat, adding and removing properties, posts, agents and pages
Pages Every kind of page, its sections with a map of each, the 55 addresses, and how the pages link to each other
Design Colours, the logo and icons, the fonts, the Tailwind classes, rebuilding the stylesheet, the style guide and motion
Forms Making the contact form, “Schedule tour” and Add property deliver to you
Editing without touching HTML Your options when someone else needs to edit the site without touching HTML
Publishing Pre-launch checklist, uploading, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers
  1. Open index.html in your browser. That is the whole site: no install, no build.
  2. Open the folder in a code editor (VS Code is a good free one).
  3. Replace the demo domain across all files with your editor’s find and replace in files (Editing the site), then search for “Goeboek” to put your agency’s name in the titles, the texts and the footer.
  4. Put your address, phones, e-mail and opening hours in the footer and contact.html, and your logo’s mark in assets/images/logo-mark.svg with your name in its two lines, and the icons icon.png and apple-icon.png (Design).
  5. Replace the photos in assets/images/: keep the file names and every page picks them up (Editing the site).
  6. Put your form endpoint in assets/js/config.js (Forms).
  7. Upload the folder to your host (Publishing).
  • One HTML file per page. 60 pages: Home, About, Contact and the forms in the root, and one file per listing, property, agent and post in type/, location/, property-category/, agent/, property/ and blog/ (Pages).
  • One stylesheet. assets/css/style.css, built from src/css/style.css with Tailwind CSS. You only rebuild it when you use a class that isn’t in the site yet, or change the theme (Design).
  • One script. assets/js/main.js runs the phone menu, the slideshows, the property cards’ photos on hover, the filter on phones, “Load More”, the three forms and the footer’s year. You rarely need to touch it: your settings go in assets/js/config.js.
  • Copies, not references. A block that shows on several pages (the header, the footer, a property’s or a post’s card, an agent’s card) is written into each of them. Change every copy, or use find and replace in files (Editing the site).
  • No framework, no dependencies at runtime. The pages work from any static host, and even straight from disk.

A property appears on many pages — the listings of its type, location, category and agent, other properties’ “More in” and “Related properties”, Home — so in this edition a new property is a good number of edits by hand. If you will list properties often, choose the Goeboek Astro or Goeboek Next.js edition instead: a new property or post is one entry in a data file, and every card, listing and sitemap line follows (Editing without touching HTML).