8000 docs: canonical blog URL should not be the auto-generated Vercel hostname · Issue #19 · dominikake/personal_blog · GitHub
[go: up one dir, main page]

Skip to content

docs: canonical blog URL should not be the auto-generated Vercel hostname #19

Open

Description

@dominikake

The canonical blog URL currently used in the repo homepage field and in the GitHub profile blog field is:

https://personal-blog-sigma-seven.vercel.app/

That is Vercel's auto-generated project name (the random three-word suffix is assigned at project-creation time). It reads as an unfinished default, and anyone landing on the profile has no signal that it is the real home of the blog.

Note: the repo README.md itself does not link to the URL at all, so this is about the metadata fields plus the README.

Problem

  • personal_blog repo → About → Website
  • GitHub profile → blog field
  • README.md → no canonical link present

All three currently either point at the generated Vercel URL or have no link at all.

Options

  1. Attach a custom domain (e.g. a .dev or .page handle) to the Vercel project and use it everywhere. Requires a registered domain.
  2. Accept the Vercel URL and make it deliberate — document it in the README and profile bio so it reads as a choice rather than a default.

Acceptance criteria

  • Canonical blog URL decided
  • Applied to the personal_blog repo description / website field
  • Applied to the GitHub profile blog field
  • Applied to the personal_blog README

Notes

There is no vercel.json or domain configuration committed to this repo, and origin is the only remote — the Vercel project appears to be managed entirely through the Vercel web dashboard. Whichever option is chosen will need to start there, not in this repository.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0