Open the wizard
Choose + New project on your dashboard or on My projects, or Add project in the footer. The wizard opens in a window over the page you're on.
A preview on the side shows how the project will look as you fill it in, with a tip for each step.
The six steps
Step 1: Basics: type, title and summary
Pick Personal for something you built on your own time, or Professional for work for an employer or client. A professional project lets you connect the work email you used there (see Verify a work email).
Then give it a title and a one-line summary. The summary shows on your project card.
Step 2: Proof: link the repository and the demo
Pick the project's repository from your GitHub account. If you haven't connected GitHub yet, choose Connect GitHub here. You come back to this step with your answers intact.
Add a live demo link if the project runs somewhere people can open it. Both are optional, but they're what make a project discoverable and trusted.
Step 3: Description: say what you built
Simple is one free-form write-up. Advanced (recommended) asks the questions recruiters scan for, so nothing important is left out. The questions change with the project type; they're listed below.
Choose Copy all questions to draft your answers somewhere else, then paste them back.
Step 4: Details: category, tools and tags
Pick one category, then the tools you used and any tags. Search filters run on these three, so a missing detail is a missed match.
Step 5: Media: add a cover
The main image is cropped to 4:3 and used everywhere except search. Drag and zoom to choose the area to keep.
The search thumbnail is optional and shows only in search results. It can be any width; a very tall image is cropped to the height the grid shows.
No image yet? The project gets a woven cover, made from its title, until you add one.
Step 6: Review: choose who sees it
Check the preview, then pick Keep private (only you can see it) or Publish (visible in search, on Discover and on your profile).
Choose Publish project or Create project. The window closes and the project saves in the background, so you can keep browsing.
The guided questions
In Advanced mode, each answer can be up to 2,000 characters, and your answers appear on the project page under clear headings.
Personal projects
- What did you build, and why did you decide to build it?
- What problem does the project solve, and who is it for?
- What parts of the project did you personally own?
- What important technical or product decisions did you make?
- What was the most difficult challenge, and how did you solve it? Optional
- What was the result, and what did you learn?
- Did anyone else contribute to the project? Optional
Professional projects
- What business or customer problem was the project intended to solve?
- What was your role on the project?
- What did you personally own or deliver?
- What important technical or product decisions did you influence?
- What constraints did you work within? Optional
- What measurable result or impact did your work produce?
- Who did you collaborate with, and how did you work together? Optional
Fields and limits
| Field | Limit |
|---|---|
| Title | Up to 120 characters |
| One-line summary | Up to 280 characters |
| Simple description | Up to 5,000 characters |
| Each guided answer | Up to 2,000 characters |
| Category | One, from the list |
| Tools | Up to 30, from the list |
| Tags | Up to 30, from the list |
| Images | PNG or JPG, under 3 MB each |
Make it easy to find
- Name it by the system, not the brand. People search for “mobile banking system” far more than a product name.
- Say what it does in the summary, in plain words. It's the line people read before they open it.
- List the tools you really used. The score checks them against the repository.
- Use a cover that shows the work itself: a screen, a flow, the thing running.