Efe Tarhan

Blog admin — one-time setup

A web CMS for the blog at https://tarhanefe.github.io/admin/. Sveltia uses a personal access token to call GitHub on your behalf — no OAuth App, no proxy, no server. The token lives in your browser’s localStorage; clearing site data signs you out.

You only do this setup once per device.

1 · Generate a fine-grained PAT

Open https://github.com/settings/personal-access-tokens/new.

Field	Value
Token name	`tarhanefe.github.io CMS`
Expiration	90 days (or longer; you can rotate)
Resource owner	tarhanefe
Repository access	Only select repositories → pick `tarhanefe.github.io`
Repository permissions	Contents: Read and write, Metadata: Read-only

Click Generate token, then copy the token (it starts with github_pat_…). GitHub only shows it once.

Open https://tarhanefe.github.io/admin/. Click Sign In with Token. Paste the PAT. You’re in.

(On phone: add the page to your home screen — it behaves like an app.)

3 · Write

Drafts (private previews) → writes to _drafts/. Reachable at /blog/drafts/<slug>/. Not listed, noindex,nofollow. Use these to preview before publishing.
Posts (published) → writes to _posts/. Appears on /blog/, in the RSS feed, in the sitemap.

Inside an entry: type into the markdown editor; drag-and-drop images to upload (they land in images/blog/); flip the live preview to see formatting; click Save to commit + push. The site rebuilds in ~1 min.

To promote a draft to a published post: open the draft, copy its body, create a new entry in the Posts collection, paste, fill in the date, save, then delete the draft. (Sveltia doesn’t have a one-click move between collections yet.)

Notes

Token security. The PAT only has access to this one repo with Contents read/write — so if it leaks, the worst case is someone editing your blog. Revoke it any time at https://github.com/settings/personal-access-tokens.
The CMS only handles blog content. Everything else on the site — index.html, layouts, CSS — stays under your editor + Claude flow.
No new file format. Drafts and posts are still plain Markdown with the same YAML front-matter you’ve been using. The CMS is just a nicer way in.
The OAuth App you created earlier (Ov23liOQtJUL…) is unused now; you can leave it or delete it at https://github.com/settings/developers. Either is fine.

If you ever want to disable the CMS

Delete the admin/ folder. The CMS only exists where the files live; nothing else on the site touches it.