For developers

A link in bio for developers

A link in bio for developers is the page you keep current after the portfolio repo goes quiet. It holds the repo, the post, and the project you want opened, and you change it without a commit just to fix one URL.

A person working at a laptop on a wooden desk at night, with a mug and a closed notebook. — A mug and a shut notebook sit beside a laptop that is still open on a wooden desk at night.

The portfolio repo goes quiet

The portfolio started as a weekend. A year later a dependency bump is why you have not opened it, the blog is one post, and the homepage still points at a job you left. Changing one URL is a commit, a build, and a deploy you keep moving to tomorrow.

A GitHub bio does not need that site. It needs the repo, the thing you shipped, and a way to write to you. Line those up in a draft before you pay. Other people can open yourspage.com/yourname only after you publish. How one address works, for any job, is on the general guide.

What belongs on the page

Keep the top row short: GitHub, X, LinkedIn, and email. Put a heading under it, Now, if that is the honest tense, and highlight the ship log rather than a second copy of the whole profile. A card earns the space when an npm package or a post needs a title and one line. Stats are numbers you type. Four products, one open contract, zero investors. Nothing fetches them.

A launch demo can be a YouTube player on the same page. The contribution graph is its own block, the public graph for a personal GitHub username, covering the last twelve months. Organization logins do not have that graph. The sample under this section does not draw it, because the preview has no calendar data. Claim your page and highlight the ship log, the link a README would put first.

Dev Patel on the Terminal theme: GitHub, X, LinkedIn, and email icons, a heading that says Now, a highlighted ship-log link, a GitHub link, a card for the npm package tiny-diff, stats reading 4 products, 1 open contract, and 0 investors, and a line of text. The contribution graph is not drawn in this picture.

The look, then the bill

Terminal is green type on black, the one aimed at builders. Ink is dark and quiet. Blueprint is a blue drafting grid. Nine themes exist, and the rest of the set is on themes. A small “Made with Page” badge sits at the bottom until you turn it off. The switch is on the plan you already pay for, not a higher one.

Linktree’s public prices, checked September 2026, list Starter at $8 a month or $72 a year, Pro at $15 or $144, and Premium at $35 or $360. Those figures are from https://linktr.ee/s/pricing. Their free plan keeps branding. Removing it is Pro and up. Their help says custom domains are not offered. The full comparison is on the Linktree comparison. Prices are on pricing. Every paid plan is the same kit.

Where you paste the URL

GitHub puts a website field on the profile, under your name. GitHub’s guide to the profile website field describes that slot. A README is a different paste, at the top of the repo people clone. Use the same published URL in the X bio, the LinkedIn website line, and the last slide of a talk. Then you are not making a commit just to change a link.

After you publish, analytics is views, which block was tapped, the referrer, the country, and the device. Not the visitor’s name. A custom domain you already own is one DNS record, with SSL included when you publish. Registration stays at the registrar. You still pay them for the name. Until that record exists, the address is yourspage.com/yourname.

Set up a link in bio for developers

Claim a name and build the draft. Other people can open yourspage.com/yourname only after you publish.
Paste GitHub, the blog, and the project, and put the one you want opened first.
Write a short bio, about the length of a GitHub profile, not a résumé.
Pick Terminal, Ink, or Blueprint.
Publish, then paste the URL into the GitHub bio and the README.

Questions

What is a link in bio for developers?

It is one public URL for the repo, the post, and the profiles, so you stop maintaining a portfolio site just to change a link. The blocks and themes are the same on every paid plan. Prices are on the pricing page.

Will this work in a GitHub README?

Yes. A Markdown link in a README opens the published page the same way any other URL does. Paste it there, and also into the GitHub profile website field, which is the one under your name. Those are two different places. You update each of them yourself.

Can the page show my contribution graph?

Yes, for a public personal username. The block shows that account’s contribution graph for the last twelve months. Organization logins do not have the graph. It is a real block on the published page. The sample picture here does not draw it, because the preview has no calendar data.

How much is it if I only need it for a launch week?

Prices are on the pricing page. A launch week is not a cheaper kit. Monthly includes the same blocks, themes, and domain connection as the other plans. Stop paying after the month if you want.

Can I point my own domain at it?

Yes. Add one DNS record at your registrar. SSL is included when you publish, on the same plan, not as an add-on. Registration stays at the registrar, and you still pay them for the name. A username URL such as yourspage.com/yourname works the day you publish if you skip the domain.

Why not just use Linktree?

Their free plan keeps branding. Removing it is Pro and up, at $15 a month or $144 a year, checked September 2026. Their help says custom domains are not offered. Here the badge comes off on the plan you pay, and a domain is one DNS record. We do not process the payment.

Freelancers, Artists, Musicians.

A link in bio for developers is the list you can change without opening the portfolio repo. Publish it, paste the URL into the GitHub bio and the README, and leave the old site until you actually want to write there. Claim your page and put the ship log first.