Practice & Assessment
Test your understanding of Standing Out: GitHub Profile and Online Presence
Multiple Choice Questions
6How do you create a GitHub profile README that appears on your public profile page?
According to the Conventional Commits standard, which commit message is correctly formatted?
Why is a merged pull request in an open source project stronger portfolio evidence than a solo project?
What is the correct LinkedIn headline format for a developer actively seeking roles?
What is the recommended update cadence for a developer portfolio to signal active development?
In a cold outreach email to a recruiter, what should lead the message body?
Coding Challenges
1Build a GitHub Profile README With Dynamic Stats
Create a GitHub profile README repository (same name as your GitHub username). The README must include: (1) your name and one-line brand statement, (2) shield.io badges linking to your portfolio and LinkedIn, (3) a 'What I'm working on' section listing your current flagship project with a GitHub link, (4) the github-readme-stats widget showing your stats with hide_border=true, and (5) two to three pinned repositories selected in your GitHub profile settings. The README must render correctly on your public GitHub profile at github.com/yourusername. Input: none. Output: live GitHub profile with complete README. Estimated time: 20–25 minutes.
Mini Project
Complete Developer Online Presence Audit and Update
Treat this as a professional audit and update sprint: (1) Build and publish your GitHub profile README with all required sections and at least two pinned repositories with clean READMEs; (2) Rewrite your LinkedIn headline using the role + stack + what you build formula, update the About section to end with a contact CTA, and add your portfolio URL as the first Featured item; (3) Review your commit history across all pinned projects and rewrite any non-conventional commit messages using git commit --amend or interactive rebase — all future commits must follow conventional commit format; (4) Find and open one pull request to an open source project, even if only a documentation fix; (5) Add your portfolio URL to every public profile, your GitHub bio, and your email signature. Document all changes made in a PRESENCE_AUDIT.md file committed to your portfolio repo.