FAQ and Limitations

Is StarryBio a hosted service?

No. StarryBio is source code for a single static link-in-bio site. You own and deploy a copy. There is no StarryBio account, hosted admin dashboard, multi-user tenant system, or managed profile editor.

Can visitors sign in or create accounts?

No. The stock project has no authentication, registration, sessions, roles, or user management.

Does it use a database or Cloudflare storage?

No. The stock build needs no D1, KV, R2, Durable Objects, queues, storage bucket, or Worker binding. Content is configured at build time and served as static assets.

Can I edit the site without redeploying?

No. Edit config/starrybio.config.ts or source/assets, build, and deploy. There is no runtime content API or web editor. This is also why visibility windows become effective only after a new build/deployment.

Can I host multiple profile pages from one stock installation?

Not through the supplied configuration. The current application renders one homepage and a custom 404 page. Multiple profiles, dynamic paths, or per-user content require source changes and likely a different data/routing design.

Can I add a contact form, newsletter signup, or payment flow?

Not as a built-in feature. Add a link to an external service, or modify the application and Cloudflare configuration to introduce the required backend/integration. Avoid presenting a static HTML form as functional without an external endpoint.

Can I create new pages through configuration?

No. Links may point to external, relative, root-relative, hash, email, or telephone destinations, but the stock configuration does not generate new Astro pages or anchor targets. Adding a new page is a development task; see Architecture and Customization.

Can I use my own domain?

Yes. GitHub Pages, Cloudflare Workers, Vercel, and Netlify all support custom domains and HTTPS. Follow Domains and DNS and the selected provider guide. The stock site does not perform hostname redirects itself.

Do I need environment variables or secrets?

No, not for stock StarryBio. The project ignores .env files as a repository hygiene measure, but it does not read StarryBio settings from them. Keep no secrets in the configuration: client-visible analytics IDs/tokens are not private deployment credentials.

What analytics providers are available?

None by default; Google Analytics 4, Cloudflare Web Analytics, Plausible, Umami, and a custom HTTPS script are supported when configured. StarryBio does not provide click events, consent management, or a first-party analytics backend. See SEO and Analytics.

Are remote images supported?

Yes, via HTTP(S) URLs, but HTTPS is strongly recommended. Remote assets are not copied into your deployment; their performance, availability, and privacy are controlled by the external host. Local public/ assets are the more self-contained choice.

Can I schedule links or announcements?

Sections, links, and featured cards have build-time visibleFrom/visibleUntil fields. They will not change on an already deployed static site until you build and deploy again. Announcements have no time window; enable or disable them in a new deployment. Status schedules are different: they run in each visitor’s browser and update every minute. See Availability and Announcements.

Is the profile status based on my real calendar or online presence?

No. It is a configuration-defined schedule evaluated in the visitor’s local time. It does not connect to a calendar, Discord, presence service, timezone-aware backend, or live availability API.

What happens to an announcement after a visitor dismisses it?

The visitor’s browser stores a seven-day SameSite=Lax first-party cookie. It is not a durable account preference, and changing the announcement text or URL creates a new dismissal key.

Can I remove the “Powered by StarryBio” link through configuration?

No. footer.copyright only changes the copyright text. Removing the attribution needs a source change in src/components/ProfileCard.astro; evaluate the project license and your distribution obligations before modifying it.

Can I use Vercel, Netlify, GitHub Pages, or another static host?

GitHub Pages, Vercel, Netlify, and Cloudflare Workers are first-class supported targets. Follow Deployment Overview. Other static hosts can publish the same dist/ output, but must translate the _headers policy and configure 404.html according to their own conventions. GitHub Pages does not apply _headers or custom response-header rules.

Does StarryBio back up my data?

No. Your Git repository and committed source/assets are your backup. Cloudflare Worker versions can help with short-term deployment rollback, but they are not a replacement for version control. See Operations and Updates.