Lejiend's website is currently a fast, static experience on Cloudflare Pages. The next architectural step is to give incoming conversations a backend designed specifically for them.
We plan to introduce api.lejiend.com as a separate Cloudflare Worker service. Its first responsibility will be deliberately narrow: receive customer and client enquiries from Contact Us, and receive the email address, phone number and consent submitted by people who want Lejiend's promotional updates.
Keeping that responsibility separate from the website allows the public pages and the backend to change at their own pace. The website remains focused on publishing and discovery. The Worker becomes the controlled boundary for validating and routing information people choose to send us.
From the current path to the latest plan
Today, both forms submit asynchronously through FormSubmit and arrive at tech@lejiend.com. That has been useful for launching quickly. The latest plan replaces that external hand-off with a Lejiend-controlled API boundary.
Current architecture. The contact form and News signup send submissions through FormSubmit to tech@lejiend.com.
Planned architecture. The contact form and News signup send information to api.lejiend.com. A Cloudflare Worker validates the submission, applies abuse protection and records consent before separating customer enquiries from consented email and phone records for promotional communication.
Two inputs, two clear purposes
Customer and client enquiries
The Contact Us form will send the person's contact details, enquiry type and message to the API so the Lejiend team can respond appropriately.
Permission-based marketing signups
The News form will send the person's email address, WhatsApp number, originating page and explicit consent record for promotional email and occasional WhatsApp communication.
What the Worker will be responsible for
The planned Worker will validate expected fields, reject malformed requests, apply abuse protection and route each submission according to its purpose. It will also give us a better place to add operational controls such as rate limits, bot protection, structured logging and secure environment secrets.
The API will not turn every contact enquiry into a marketing subscriber. An enquiry and promotional consent are different purposes. Marketing communication should only use details submitted through an explicit consent flow, with an understandable unsubscribe path.
Why we are sharing this now
Building in public is most useful before a diagram becomes invisible infrastructure. Publishing this decision records why we chose a separate backend, defines its initial scope and gives us a clear reference when the implementation evolves.
The latest diagram is not a promise that every box is already running. It is a practical map for the next build: protect the information people entrust to Lejiend, preserve the purpose attached to it and make follow-up more reliable.