How This Site Was Made

This section was created as an experiment and as a training example: how far can one person get without a professional team, working together with artificial intelligence? The answer: pretty far. You just need to know what you want – and check everything.

The architecture in plain words

• The site runs on Cloudflare Workers – a small JavaScript program that runs “in the cloud”, close to the reader. There is no server of its own that needs restarting on a Sunday morning.
• The public part (“About Bulgaria”) is built entirely into that program. The texts are kept as ordinary text files – one per section and language – and become part of the code when it is assembled.
• The family part is separate and requires a login. It uses a database (Cloudflare D1) and a photo store (Cloudflare R2). It is not part of this section, and nothing from it is shown publicly.
• Three languages – Bulgarian, English and German. The address decides the language: no prefix is Bulgarian, /en is English, /de is German.

The workflow

1. Idea and questions. It all starts with one sentence: “I want a section about Bulgaria – language, literature, history, geography, travel.” The AI asks clarifying questions: how big, what tone, where should it live.
2. Research. Facts that change – the euro, the population, literary prizes, tourism websites – are checked online against official and reliable sources.
3. Writing in Bulgarian. The Bulgarian version comes first, section by section, in a single format: title, short introduction, text, and “Between us” notes.
4. Translation. The English and German versions are produced in parallel by several AI agents, each translating its own section. The humour is adapted, not translated word for word.
5. Human review. The author reads, corrects and adds: that is how the “Fun Facts” part and the neighbourly wars Sliven–Yambol, Lovech–Pleven and Varna–Dobrich came about.
6. Automated checks. Before uploading, every page is generated locally in all three languages, every internal link is checked, and the pages are photographed in a browser at desktop and phone size.
7. Upload. The finished worker.js file is pasted into the Cloudflare dashboard and “Deploy” is pressed. If anything goes wrong, the previous version is back within a minute.

If you want to try it yourself

• Start small. One page, one language. Then add.
• Keep content separate from code. Text files are easy to edit, even for people who don't program.
• Check the facts. AI writes confidently – both when it is right and when it isn't. Dates, names and numbers always need checking.
• Keep the previous version. Each upload in its own folder. It saves nerves.
• Leave room for the human. The best ideas in this section came from the author, not the machine.