Fork website
uplbtools/website is the org landing page — a static Astro
site that lists your tools, team, press, and community links. Forking it is the
easiest part of standing up a campus org.
A live example: bulsutools/website
(bulsu.tools), deployed on Cloudflare Pages.
What to change
Section titled “What to change”| Thing | Where |
|---|---|
| Tool listings (name, URL, description, screenshot) | src/data/tools.ts |
| Site name, description, socials | src/lib/site-meta.ts |
| Press/team content | src/data/press.ts, src/pages/people.astro, src/pages/press.astro |
| Legal pages (privacy, terms, transparency) | src/pages/privacy.astro, terms.astro, transparency.astro |
| Brand assets, screenshots, OG image | public/ (brand/, *-screenshot.png, og.png) |
| Canonical URL | astro.config.mjs site |
| Favicon/icons | public/favicon*, icon-*.png, apple-touch-icon.png |
Also update README.md — stack, dev commands, deploy section — so the next
contributor isn’t reading UPLB instructions.
One-click option: create your repo from
bulsutools/website-template
(Use this template), then git clone it.
Fork option:
gh repo fork uplbtools/website --org <your-org>git clone git@github.com:<your-org>/website.gitcd websitenpm installnpm run dev-
Edit the files in the table above.
npm run generate:ogregenerates the OG image after branding changes. -
Pick a deploy target:
Cloudflare Pages (what bulsutools uses):
- Create a Pages project, connect the repo
- Build command
npm run build, output dirdist - Add a GitHub Action like
bulsutools/website’s.github/workflows/deploy-cloudflare.ymlwithCLOUDFLARE_API_TOKENandCLOUDFLARE_ACCOUNT_IDsecrets for CI deploys + PR previews - Attach your domain (
you.tools,you.github.io, etc.)
Vercel (what uplbtools uses for
uplbtools.me):- Import the repo, framework preset Astro, defaults work
- Add env vars if the site uses any
-
Optional:
public/_redirectshandles path redirects on Cloudflare Pages;workers/in the upstream repo holds Cloudflare Worker subdomain redirects (e.g.messenger.uplbtools.me) — copy the pattern if you wantapp.you.tools-style subdomains.
- Remove UPLB press photos and team sections you can’t replace — an empty section looks worse than no section.
- Keep
CODE_OF_CONDUCT.md,CONTRIBUTING.md,LICENSE— they’re generic. - If your campus org has a different name casing (
bulsutoolsvsBulSU Tools), decide once and use it consistently insite-meta.ts, the README, and the repo description.