Why code ownership matters#
A website is more than a page you look at. Behind it sits code, the files that tell the browser what to show, how the menu works, and where the pictures come from. Whoever holds those files controls the site. If the files sit only inside someone else's account, the site depends on that person staying available and staying willing to help. Most owners never think about this until a change is needed.
This matters most when a shop changes its helper. A freelancer may move on, a small agency may close, or a working relationship may simply end. When that happens, the question is not only who will fix the next problem. The question is whether the owner can still reach the site's own files at all. Owning the code directly removes that uncertainty, because the files belong to the shop from the start.
What the export contains#
DISPO, made by SISO Labs, can export a site into the owner's own GitHub and Cloudflare accounts. The export includes the site's assets, the credits that name the people and tools involved, and a README file that explains how the project is arranged. Because the code lives in the owner's GitHub account, the owner decides who can see it and who can change it. Cloudflare is where the site is served, so the owner also holds the hosting side of the arrangement.
A README matters more than it might seem. It is the note a future developer reads first. A clear README tells the next person where things are, what each part does, and how to publish a change. Without one, even a complete set of files can take a long time to understand. Including it in the export means the handover is not left to memory.
Keeping control over time#
Owning the code is not a one-off step. It helps when the owner knows where the repository is, who has access to it, and which accounts are tied to the hosting. Checking these things from time to time, especially after any change of staff or helper, keeps the arrangement clear. An owner who can log in to their own GitHub and Cloudflare accounts can always see the state of the site without asking anyone for permission.
It is also worth knowing what you would need if a change happened. A short note listing the accounts, the repository name, and the person who holds the login details can make a later handover much easier. Store that note somewhere safe and up to date. The aim is simple: whoever helps you next should be able to pick up the work without starting from nothing.
Rules and getting advice#
This post explains how code and hosting work. It does not explain what a shop may publish on its website, and it is not legal advice. Thai rules limit how cannabis may be advertised, so check your plans with a lawyer.
The technical side of owning your code is something you can manage yourself, with a clear repository and a current list of accounts. Questions about content and the law need a qualified professional to confirm before anything goes live.