PTENES
MODULE 6.4 โ€” LAST COURSE MODULE

๐Ÿ“ฃ Improve and share

Deployment was the beginning, not the destination. Learn to iterate quickly, create releases, build an impressive portfolio, and keep the project alive over time.

6
Topics
~35
Minutes
๐ŸŽ“
Wrap-up
๐Ÿš€
Strategy
1

๐Ÿ”„ Iterate after deployment

The cycle never stops โ€” feedback โ†’ improvement โ†’ deploy โ†’ repeat

๐ŸŽฏ Deploy isn't the end

The first version always has bugs, confusing UX, and missing features. That's normal โ€” and it's exactly where Claude Code shines most: iterate quickly. What would take days of manual refactoring, Claude handles in minutes.

v0.1 first deploy v1.0 bugs fixed Improved UX v2.0 new features real feedback complete docs ALIVE ๐ŸŒฟ community contributors regular releases strong portfolio PROJECT MATURITY

Each iteration moves you up a level. Consistency over time > a single launch sprint.

โœ“ Healthy iteration

  • โœ“Small, frequent commits (every day or week)
  • โœ“Open issues to track upcoming improvements
  • โœ“Feedback from real users guides priorities
  • โœ“Claude Code implements improvements in minutes

โœ— Abandoned project

  • โœ—Last commit 6+ months ago
  • โœ—Open issues with no response
  • โœ—Outdated dependencies with vulnerabilities
  • โœ—README outdated compared to the current code
๐Ÿ“Š
SemVer
major.minor.patch
๐Ÿ“‹
Roadmap
What comes next
๐Ÿ”ง
Hotfix
Urgent critical bug
๐Ÿ“
Changelog
Change history
2

๐Ÿท๏ธ Releases and tags

Formal versions โ€” communicate progress to users and recruiters

1

Create a tag and release via gh CLI

# Criar tag local e push
$ git tag v1.0.0
$ git push origin v1.0.0

# Criar release no GitHub com notas automรกticas
$ gh release create v1.0.0 \
  --title "v1.0.0 โ€” Lanรงamento inicial" \
  --generate-notes

# Listar releases
$ gh release list

# Ver release especรญfica
$ gh release view v1.0.0
2

Versioning convention (SemVer)

v1.0.0 โ†’ First stable version, public API defined

v1.1.0 โ†’ New feature compatible with the previous version

v1.1.1 โ†’ Bug fix, with no behavior change

v2.0.0 โ†’ Breaking change โ€” API changed

๐Ÿ’ก --generate-notes is gold

O gh release create --generate-notes automatically reads the PR and commit history since the last release and generates a formatted changelog. No manual effortโ€”perfect for maintaining consistency.

๐Ÿท๏ธ
git tag
Mark the commit
๐ŸŽ
gh release
Public page
๐Ÿ“„
Release notes
Generated automatically
โšก
Pre-release
Beta/RC before stable
3

๐Ÿ’ผ Build a portfolio

Your projects as a showcaseโ€”what recruiters really look for

๐Ÿ™ GitHub Profile README

Create the special repo usuario/usuario with a README.md. It appears on your GitHub profile as a custom page.

$ gh repo create usuario --public
$ # Crie README.md com seu bio,
# habilidades e projetos

๐ŸŒ Portfolio website

Repo usuario.github.io becomes your personal website. Claude Code can generate the entire page with cards for your projects.

โœ“ Professional photo/avatar

โœ“ Project grid with screenshots

โœ“ Link to GitHub, LinkedIn

๐Ÿค– Let Claude generate your portfolio

Ask: "Analyze my GitHub repositories and create a responsive HTML portfolio page with cards for each project, my bio, and contact links." Claude lists repos, reads READMEs, and generates the complete page.

1

Pinned repositories

On your GitHub profile, "Pin" up to 6 repos. Choose the ones that best represent your skillsโ€”not the oldest ones or the ones with the most stars.

2

Contribution graph

The green contribution graph on your profile is visible to everyone. Regular commits show consistency โ€” more valuable than a single sprint.

๐Ÿ“Œ
Pinned repos
Showcase on your profile
๐ŸŸฉ
Contribution
Visible activity
๐ŸŒ
Personal website
usuario.github.io
๐Ÿ“
Profile README
Bio + projects
4

๐Ÿ“š Document well

Your future self will thank you โ€” and so will recruiters

Documentation is what turns a repository into a project. Without it, even you will be asking yourself in 3 months, "How does this thing work again?"

โœ“ Minimal documentation

  • โœ“README with installation and basic usage instructions
  • โœ“CHANGELOG.md with version history
  • โœ“Comments in non-obvious functions
  • โœ“LICENSE (MIT for open source projects)

๐Ÿ“ˆ Advanced documentation

  • โ†’CONTRIBUTING.md to attract contributors
  • โ†’ADR (Architecture Decision Records)
  • โ†’GitHub Wiki for long-form docs
  • โ†’Docusaurus for large projects

๐Ÿค– Claude automatically documents code

Ask: "Add JSDoc comments to all functions in this file" or "Generate the CONTRIBUTING.md explaining how to set up the environment and open PRs". Claude reads the code and generates accurate, consistent documentation.

๐Ÿ“„
README.md
Project input
๐Ÿ“‹
CHANGELOG
Version history
๐Ÿค
CONTRIBUTING
How to collaborate
โš–๏ธ
LICENSE
Terms of Use
5

๐Ÿ“ข Ask for feedback and share

Build an audience for the project โ€” real feedback > assumptions

1

Communities to promote in

โœ“ Reddit: r/webdev, r/programming
โœ“ Dev.to (article + link)
โœ“ Twitter/X with #buildinpublic
โœ“ Show HN (Hacker News)
โœ“ LinkedIn (technical post)
โœ“ Product Hunt (launch)
2

Ask for structured feedback

GitHub Discussions is great for asynchronous feedback. Issues with the "feedback" or "question" label make it clear that you want to hear from users.

$ gh issue create \
  --title "[FEEDBACK] O que vocรช achou?" \
  --label feedback \
  --body "Conte o que funcionou e o que falta"

โœ“ Build in public works

  • โœ“Sharing the process builds an audience before launch
  • โœ“Early feedback prevents building the wrong thing
  • โœ“Progress logs become a learning portfolio

โœ— Common errors

  • โœ—Waiting for "perfect" to share itโ€”it never comes
  • โœ—Ignore the first users (they're gold)
  • โœ—Share without a direct link to test
๐Ÿš€
Product Hunt
Public release
๐Ÿ—๏ธ
#buildinpublic
Share progress
๐Ÿ’ฌ
Discussions
Asynchronous feedback
โญ
Stars
Traction metric
6

โ™ป๏ธ Keep the project alive

Consistency > intensityโ€”the secret to projects that last

๐ŸŒฟ Living project vs. archived project

A living project doesnโ€™t need marathon sprints. It needs consistency: one small improvement per week is more valuable than 3 months of silence followed by a major update. Recruiters look at the contribution graph.

๐Ÿค–

Dependabot โ€” automatic updates

Activates automatically on GitHub. Creates PRs to update dependencies with vulnerabilities. Configure it in .github/dependabot.yml:

version: 2
updates:
  - package-ecosystem: npm
    directory: "/"
    schedule:
      interval: weekly
๐ŸŒฑ

Good First Issues โ€” attracting contributors

Issues marked with good first issue appear in GitHub search results for people looking to contribute for the first time. A great way to grow the community.

$ gh issue create \
  --title "Melhorar mensagem de erro do login" \
  --label "good first issue"

โœ“ Weekly maintenance ritual

  • โœ“Review open issues (respond or close)
  • โœ“Merge approved Dependabot PRs
  • โœ“At least 1 small improvement commit
  • โœ“Update README if anything changed

๐Ÿ“ฆ When to archive

  • โ†’Project replaced by something better
  • โ†’Outdated technology without maintenance
  • โ†’Use Settings โ†’ Archive repository to flag
  • โ†’Let the README explain why
๐Ÿค–
Dependabot
Automatic updates
๐ŸŒฑ
Good first issue
Attract contributors
๐Ÿ—บ๏ธ
Milestones
Public planning
๐Ÿ“ฆ
Archive
End with dignity
๐Ÿ†

Congratulations! You completed the course.

Claude Code โ€” From Zero to Project

What you learned in this track

  • โœ“Git: init, add, commit, log, branches, .gitignore
  • โœ“GitHub: repos, remote, SSH, gh CLI, PRs, README
  • โœ“GitHub Pages: free deploy with HTTPS and CDN
  • โœ“Releases, portfolio, documentation, and community
  • โœ“Keep projects alive consistently

What you can do now

  • โœ“Using Claude Code as a real development partner
  • โœ“Create projects from scratch with intelligent automation
  • โœ“Publish and keep websites online for free
  • โœ“Build an impressive technical portfolio

You completed all 6 tracks. Now the best way to continue is build. Pick a real project, open Claude Code, and get started.