Back office
Enter the passcode from site-config.js.
Back office
Everything you can change without touching code. Each section hands you a finished file to drop into the site zip before you re-upload.
What lives where
| Books, covers, buy links | assets/js/books.js — edit at /editor |
| Brand, emails, socials | assets/js/site-config.js — edit in Site settings |
| Colors and fonts | assets/css/booklyn.css — the variables at the top |
| Prices and page copy | the HTML file itself, or src/content.py in the brand kit |
| Form delivery | Cloudflare environment variables |
Identity
Contact
Social links
An empty box hides that link everywhere on the site.
Technical
/api/contact unless you use Formspree or similar.Turning the inbox on
- Cloudflare dashboard → your Pages project → Settings → Functions → KV namespace bindings.
Create a namespace and bind it with the variable name
SUBMISSIONS. - Settings → Environment variables: add
ADMIN_TOKENand paste in a long random string. That is what this page asks you for. - Redeploy. Every form submission is then stored and appears here.
Email delivery is separate and can run alongside this: set
RESEND_API_KEY, NOTIFY_EMAIL and FROM_EMAIL and messages are
both emailed to you and kept here.
Make your changes
Catalog at /editor, everything else in Site settings. Each screen ends with a Download button.
Put the files back in the site folder
books.js and site-config.js both go in assets/js/, replacing
the versions already there. Cover images go in assets/covers/.
Re-zip and upload
Zip the contents of the site folder, not the folder itself — index.html must sit at
the top of the zip. Cloudflare Pages → your project → Create deployment → drop the zip in.
Hard-refresh once
The site installs a service worker for offline use, so your browser may hold the old version for a minute. Ctrl+Shift+R (Cmd+Shift+R on a Mac) clears it.
About this passcode
The passcode on this page only hides the screen. Anyone determined can read it in the source. It stops casual visitors, nothing more — and it does not matter much, because nobody can change your live site from here. Every change has to go through you re-uploading a file.
The one thing that is genuinely protected is the submissions inbox: the
token is checked on Cloudflare's server, not in the browser. If you want the whole page locked properly,
add a Cloudflare Access policy on /admin and /editor in your Pages project
— free for up to 50 users, and it puts a real login in front of both.