FAQ and support

Common questions

Can I use Polaris for a client?

Yes. One license covers one website, either your own or one you build for a client. Buy one license per site. The full terms are in the license guide.

Can visitors book and pay on the site?

No. This is the theme edition: visitors send an enquiry and you reply. There are no payments and no online booking. Online booking, payments and an admin area are a separate edition that is not included. See Enquiries.

How do enquiries reach me?

You choose one of four ways with booking.send in site.config.ts: WhatsApp, email, Web3Forms or Formspree. See Enquiries.

Do I need to know how to code?

No. Everyday changes are made in site.config.ts and Markdown files, which are plain text, and new pages are built by copying blocks from the block library. Changing the design needs basic HTML and CSS.

Can I use it for stays or camps only, with no trips?

Yes. The demo has a second home page for stays and camps (/home-stays/). Copy it over src/content/pages/index.md to use it as your home page. See Site settings.

Why are the demo photos missing?

The demo uses free-licence photos from Unsplash. They are not included in the download, so it contains placeholders with the same file names, drawn by scripts/placeholders.mjs. Replace them with your own photos. See Colours, fonts and photos.

Does Polaris use cookies?

Polaris itself sets no cookies. Light or dark mode is saved in the visitor’s browser storage, which isn’t sent anywhere. The map loads from OpenStreetMap only when a visitor clicks Show map. A form service you choose may set its own cookies.

Is the demo company real?

No. The demo uses a fictional company, with made-up trips, people and reviews. Replace all of it with your own.

Fixing problems

npm run dev shows an error about a page

Polaris checks every content file. The message names the file and the field, such as sections.2.variant, which means the third block’s variant (counting starts at 0). Common causes: a misspelt setting, a variant that doesn’t exist for that block, or wrong indentation.

A trip or stay says a destination can’t be found

The destination of a trip or stay must be the file name of a destination in src/content/destinations/, without .md. Check the spelling, for example ladakh.

A departure date is rejected

Departure dates must be written as YYYY-MM-DD, for example 2027-06-12.

A photo shows a placeholder

Check the file is in src/assets/images/ and that the name in the page matches exactly, including .jpg and capital letters. A misspelt name gets a drawn placeholder.

Search says it isn’t ready

Search is built with the site. Run npm run build and npm run preview to try it. See Search.

The enquiry form doesn’t send

Check that booking.send matches what you set up: a whatsapp number for WhatsApp, an email for email, booking.web3formsKey for Web3Forms, or booking.formspreeId for Formspree. Then send a test enquiry. See Enquiries.

After sending, Formspree shows its own page

Returning to your site is a paid-plan feature of Formspree. Set the redirect to https://your-domain/enquire/?sent=1 in your form’s Settings on formspree.io, or use Web3Forms.

Past departures are still showing

Upcoming and past departures are worked out when the site is built. Rebuild the site, or schedule a daily rebuild. See Deploying.

Changes don’t appear

Save the file, and check the terminal running npm run dev for an error. If you changed content.config.ts or added a folder, stop the preview with Ctrl+C and start it again.

Support

Support is the same for every theme. See the support guide for how to reach us and what to include.