Why you need a site when you already have GitHub
GitHub shows code, but it does not tell a business what problem you solve. The owner of an Uzum store or a clinic that wants online booking will not dig through repositories. They need a page in plain language: who you are, what you work on, how a project runs, and how to reach you.
Your own site also gives you what social networks and freelance boards cannot: control over presentation, the address, and the analytics. Someone who finds you through search or a referral lands on one page, not on a feed full of other people’s posts.
What a developer portfolio website needs on the homepage
Visitors decide within seconds whether to stay, so the first screen has to say who you are and why you are useful. The order of blocks can vary, but the set is usually the same:
- A positioning headline. “Backend developer building Click and Payme integrations for online stores” beats a bare “Full-stack developer”.
- A short “What I do” block: three or four types of tasks and your core stack, not everything you have ever touched.
- Three to five projects, described by outcome and not only by name.
- How you work: freelance, project team or full-time, plus languages and hours when you are reachable.
- Contacts: Telegram, email, GitHub link and, if needed, a PDF résumé.
- Testimonials or references, if you are allowed to publish them.
How to describe your projects
The weakest part of many portfolios is a project card made of a screenshot and a list of technologies. A client cares about a different chain: what the problem was, what you personally did, and what changed for the business. For a Telegram bot that takes orders for a café, “orders stopped getting lost in private messages and the manager sees everything in one chat” says more than “Python, aiogram, PostgreSQL”.
If a project is under NDA, describe the type of task without naming the client. Do not invent numbers: if growth was never measured, say honestly what was built. A live link or a short screen recording is more convincing than any paragraph.
Keep the technical side simple
A portfolio does not need complex architecture. A static site on a framework you know, or a light CMS if you will add projects often, is enough. The choice itself sends a message: a heavy site that loads slowly says less about your skill than a lean page that opens instantly.
In Uzbekistan a large share of visitors come from phones, sometimes on an unstable connection, so check the mobile layout and page weight. Think about languages: Russian and English are close to essential, and an Uzbek version helps if you want local business clients. Connect a domain, enable HTTPS and write clear page titles for search.
How the site turns into client requests
A website does not bring orders by itself; people have to see it. Put the link in your Telegram and Instagram profiles, your GitHub bio, your email signature and your proposals on freelance platforms. For search, build separate pages for real queries, such as “Telegram bot development in Tashkent”, if that is what you do.
Before you promote anything, define your metrics: how many enquiries you want, from which sources, and what counts as the target action — a click on the Telegram button, a form submission, a résumé download. Without basic analytics you cannot tell whether the site works or simply exists. Add a counter and set goals for every contact button.
Common mistakes
The same problems show up again and again, and almost all of them can be fixed in one evening:
- A generic headline such as “Developer” with no specialisation.
- A list of twenty technologies instead of clear tasks.
- Projects that do not say what your role was.
- No fast way to reach you: a form nobody answers or an outdated Telegram username.
- A template with placeholder text that has not changed in years.
- A site that looks bad on a phone or opens slowly.
When it makes sense to bring in a team
A developer can certainly build their own portfolio. But if you need positioning, copy in several languages, an SEO structure and working analytics, and you lack the time, it is reasonable to hand part of the job to specialists. The markdev team builds turnkey websites in Uzbekistan, from structure and design to launch and measuring results. If you would like to talk through your own portfolio site, send us a message and we will look at the task together.
FAQ
Does a developer need a website if they have a GitHub profile?
Yes, if you want clients from the business side. GitHub speaks to other engineers, while a company owner needs a plain explanation of what you solve, how you work and how to contact you.
How many projects should a portfolio show?
Three to five strong ones, each with your role and the outcome, work better than a long list with no context. Pick projects close to the kind of work you want to receive.
Which languages should the site be in?
For the Uzbek market most developers start with Russian and English. An Uzbek version is useful if you target local businesses or want to cover more search queries.
How do I know the portfolio is working?
Decide on the target action in advance: a Telegram click, a form submission, a résumé download. Connect analytics and watch which sources produce those enquiries.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.