FAQ
Why can the site build but still fail at runtime?
Static build success only validates Astro compilation. Runtime failures usually come from missing Pages bindings
(d1_jb, r2_jb) or missing required payment environment variables.
Why do demos look different from the official website?
Upstream demos were originally independent static files. This project normalizes them by injecting a shared theme stylesheet and localization script so they align with the website visual language.
How is download security implemented?
Downloads require delivery tokens stored in D1 with expiration metadata. The download endpoint validates tokens server-side and fetches package objects from R2 without exposing raw storage paths to clients.
Can this documentation be expanded to multi-language?
Yes. The current information architecture is language-ready and can be extended by route-based localization
(for example /en/docs/* and /zh/docs/*).