Skip to main content
The Review Editor handles one page. The Website Editor handles the site those pages live in.

Site theme

The Style tab is your site’s look — your profile theme. It sets the default for every public page you own: your homepage, your standalone pages, and every review page you have not styled individually. Nine groups, in this order: The rows under Global in the left panel are shortcuts into this one tab — clicking Typography or Colours opens the Style tab with that group already expanded, rather than leaving you to scroll for it.
This tab is deliberately identical to the Review Editor’s Style tab: same groups, same order, same names. The only difference is scope — here you are setting the default for your whole site, there you are overriding it for one page.
Page style is the one control whose effect you will not see on the canvas beside it. Only review pages read it, so it sets the layout your reviews start from and leaves your homepage alone.
Changing anything here moves every page that has not been styled individually. A review with its own overrides keeps them — and its editor will tell you as soon as it stops matching this theme. See Review Editor.
This is where your site theme is edited, and the only place it can be changed. It saves as you edit — there is no save button. Styling a review in the Review Editor never touches it. If one page looks different from what you see here, that page has its own style overrides: open it in the Review Editor and choose Reset to site theme.
Your header and footer are set once here and appear on every public page: your homepage, every review page, every standalone page, and your 404 page. This is worth stating plainly because it used not to be true. If you build a header, publish, then click into one of your own reviews, you will see the same header. That is the intended behaviour. Menu links can point at:
  • A section of your homepage
  • One of your review pages
  • One of your standalone pages
  • An external address
  • Or be generated automatically from what you have published
If a link points at something you later delete or unpublish, Guino removes the link rather than leaving a dead one on your site. A menu item that goes nowhere is worse than a missing menu item.

Brand marks

Upload a logo and a favicon. The favicon is the small icon that appears in a browser tab. Guino processes both on upload, which checks they are genuinely images and keeps them a sensible size. After you replace a logo, the new one appears straight away rather than your old one sticking around in browser caches.

Standalone pages

Beyond reviews and your homepage, you can create ordinary pages: About, Contact, and the privacy and disclosure pages an affiliate site is expected to have. Guino ships starter templates for privacy and terms.
The templates are a starting point, not legal advice, and they say so in the page text. Guino treats an unedited template as a blocker and will tell you before you publish. A privacy policy nobody has read is worse than no privacy policy, because it makes a promise you have not checked.
Some addresses are reserved and cannot be used for a standalone page, reviews among them, because your review pages already live there.

Newsletter signup

If you add a newsletter block, addresses visitors enter are captured and you can export the list as a CSV file. An email list you cannot export is not really yours.

Your site address

Your site lives at a guino.app address by default. You can change the name portion, and Guino keeps the old address working so links you already shared still resolve. If you own a domain, see Custom domain.

Exporting your site

You can export every published page as HTML in a zip file.
The export links images by their web address rather than bundling the image files. It is a readable archive of your content, not a copy you can drop onto another host and run offline. The README inside the zip says the same thing.