Phase 6 · Career Prep

Building Your IT Portfolio

Your portfolio is your proof of skills. In IT support, a well-documented portfolio of hands-on projects, lab work, and contributions speaks louder than any certificate.

8 Modules
~18 hours estimated
Hands-on focus

🎯 Learning Objectives

MOD 1 Documentation Best Practices
⏱ 2 hours

Why Documentation Matters

In IT support, documentation IS the job. Every ticket you resolve, every system you configure, every process you improve should be documented. It proves your skills and helps others.

  • Follow the Problem -> Solution -> Lesson framework for every write-up
  • Use headings, bullet points, and screenshots to make docs scannable
  • Include before/after states so readers see the transformation
  • Version your documentation: note what changed and when
  • Write for your future self: assume you'll forget details
  • Use markdown (.md files) for all your documentation
🔧 Hands-On Practice

Document a recent technical problem you solved (real or simulated). Write it using the Problem-Solution-Lesson framework and save it as a markdown file in your GitHub repo.

📋 Documentation Template

# [Project/Ticket Title]

## Overview
What was the issue or goal? (2-3 sentences)

## Environment
- OS:
- Software versions:
- Tools used:

## Problem Description
Detailed description of the issue or requirement.

## Solution
Step-by-step actions taken to resolve the issue.

```bash
# Include relevant commands or scripts
```

## Results
What was the outcome? Include evidence (screenshots, metrics).

## Lessons Learned
What would you do differently? What did you learn?

## References
Links to documentation, forums, or resources used.
MOD 2 Creating a GitHub Portfolio
⏱ 2.5 hours

Setting Up Your Profile

  • Create a professional GitHub profile photo and bio
  • Pin your most important repositories to your profile
  • Use a README.md on every repository to explain the project
  • Organize repos into collections (e.g., "home-lab", "scripts", "labs")
  • Add a main README.md at the root of your profile
  • Use topics/labels to categorize your projects

Repository Structure

  • One repo per project with a clear purpose
  • Include a detailed README for each project
  • Use meaningful commit messages
  • Add issue templates for bug reports and feature requests
  • Include a CONTRIBUTING.md for collaborative projects
🔧 Hands-On Practice

Create a GitHub account, set up your profile README, and create your first repository with a proper README documenting an IT support project from your home lab.

📋 Repository README Template

# Project Name
A one-line description of what this project does.

## What's Inside
Brief description of the project scope.

## Prerequisites
- List of software/tools needed
- Hardware requirements (if any)

## Setup Instructions
Step-by-step setup guide with code blocks.

## Usage
How to use or interact with the project.

## Screenshots
![Screenshot](./screenshots/demo.png)

## Learnings
What I learned from building this project.

## References
Resources used during development.
MOD 3 Home Lab Documentation
⏱ 2.5 hours

What to Document

Your home lab is your strongest portfolio asset. Document it thoroughly:

  • Lab Architecture: Network diagram showing your VMs, routers, switches
  • Each Service Deployed: What it does, how you configured it, why
  • Problems Encountered: Things that broke and how you fixed them
  • Hardware List: What physical/virtual hardware you use and costs
  • Cost Breakdown: Total investment vs. what it taught you
🔧 Hands-On Practice

Take screenshots of your home lab setup. Draw a simple network diagram (use draw.io or Excalidraw). Write a comprehensive lab overview document covering architecture, services, and lessons learned.

📋 Home Lab Overview Template

# My Home Lab
*A hands-on learning environment for IT support skills*

## Lab Overview
Purpose: [why you built this]
Started: [date]
Last Updated: [date]

## Hardware
| Component | Model | Purpose | Cost |
|-----------|-------|---------|------|
| Server | | | $ |
| Router | | | $ |
| Switch | | | $ |

## Virtual Machines
| VM Name | OS | Purpose | Specs |
|---------|-----|---------|-------|
| | | | |

## Services Running
1. **[Service Name]** - What it does, how it helped you learn
2. **[Service Name]** - ...
3. **[Service Name]** - ...

## Key Projects
1. [Project title] - Brief description and link to repo
2. [Project title] - ...

## Lessons Learned
- What went wrong and how you fixed it
- What you'd do differently
- Skills gained
MOD 4 Project Showcase Templates
⏱ 2 hours

Showcasing Your Work Effectively

Every project in your portfolio should tell a story. Use this template for each project showcase:

  • The Challenge: What problem were you solving?
  • Approach: How did you think through it?
  • Implementation: What did you actually do? (with evidence)
  • Results: What was the outcome? Quantify if possible.
  • Reflection: What would you improve next time?

Ideal Portfolio Projects for IT Support

  • Active Directory domain setup with group policy enforcement
  • Home NAS with backup automation
  • Network monitoring dashboard (PRTG, Zabbix, or similar)
  • Print server setup and troubleshooting scenario
  • VPN configuration for secure remote access
  • Automated system health checks via script
  • Multi-OS troubleshooting lab (Windows/Linux/macOS)
🔧 Hands-On Practice

Choose 2-3 projects from your home lab or past experience. Write a project showcase for each using the challenge-approach-implementation-results-reflection format. Save as individual markdown files.

MOD 5 LinkedIn Optimization for IT Roles
⏱ 1.5 hours

Profile Elements That Matter

  • Headline: Not just "Looking for jobs" - use keywords like "IT Support Specialist | CompTIA A+ | Azure Fundamentals"
  • About Section: Tell your story: why IT support, what you've built, what you're passionate about
  • Experience: Include home lab work, volunteer IT help, and any relevant non-IT experience
  • Featured Section: Pin your best project write-ups and GitHub repos
  • Skills & Endorsements: Add all relevant skills; get endorsements from peers
  • Certifications: Add every certification with credential IDs and URLs
  • Recommendations: Request recommendations from colleagues, mentors, or lab partners
🔧 Hands-On Practice

Review your LinkedIn profile against the checklist above. Update your headline, about section, and add at least 3 featured items from your portfolio work.

MOD 6 Blog & Writing About Your Journey
⏱ 2.5 hours

Why Writing Matters

Writing about what you learn reinforces your knowledge, demonstrates communication skills, and builds visibility with employers. Even short posts count.

  • Start a dev.to or Medium blog, or use your own site
  • Write about obstacles you overcame and how you solved them
  • Share "day in the life" of your study routine
  • Post tutorial-style content ("How I set up my home lab")
  • Share exam preparation tips and resource reviews
  • Comment thoughtfully on others' posts to build community presence

📋 Blog Post Structure

Title: Catchy and keyword-rich (e.g., "How I Built a Home Lab for Under $200")

Introduction: Hook the reader, state what they'll learn
Body:
  - Use subheadings (H2, H3)
  - Include screenshots where helpful
  - Add code blocks for technical steps
  - Keep paragraphs short (2-4 sentences)
Conclusion: Summary + call-to-action (comment, share, follow)

Tags: # compTIA # homelab # it.support # learning
🔧 Hands-On Practice

Write and publish your first blog post about something you learned recently. It could be about your home lab, an exam topic, or a troubleshooting story. Aim for 500-800 words.

MOD 7 Open Source Contribution Basics
⏱ 2 hours

Getting Started with Open Source

Contributing to open source shows collaboration skills and genuine interest in technology. Start small:

  • Good First Issues: Look for issues labeled "good first issue" or "beginner friendly"
  • Documentation: Fix typos, improve examples, translate docs - low barrier entry
  • Bug Reports: Learn to write clear, reproducible bug reports
  • Answer Questions: Help others in issue threads and discussions
  • Follow Contribution Guidelines: Always read CONTRIBUTING.md before submitting

Projects Worth Looking At

  • IT-support-adjacent tools: WSL docs, Docker tutorials, networking guides
  • Home lab community projects (OpenMediaVault, CasaOS, etc.)
  • Documentation improvements for major tech companies
  • Automation script repositories on GitHub
🔧 Hands-On Practice

Find a GitHub repository related to IT support or networking. Read its CONTRIBUTING.md, find a "good first issue," and submit a pull request (even if it's just a documentation fix).

MOD 8 Personal Tech Website
⏱ 2.5 hours

Building Your Online Presence

A simple personal website acts as your digital business card. You don't need fancy hosting - GitHub Pages is free and looks professional.

  • Use GitHub Pages (free, connects to your GitHub profile)
  • Consider static site generators: Hugo, Jekyll, or even simple HTML
  • Include: About page, portfolio/projects, blog, contact info
  • Keep it clean and fast-loading - no heavy animations needed
  • Use a custom domain if you want to invest ($10-12/year)

Essential Pages

  • Home: Who you are, what you do, a brief bio
  • Projects: Your best 3-5 IT support projects with descriptions and links
  • Blog: Your written journey and insights
  • About: More detail on your background and goals
  • Contact: Email, LinkedIn, GitHub links
🔧 Hands-On Practice

Create a simple personal website using GitHub Pages. Include an About page, a Projects section linking to your GitHub repos, and a Contact section. Deploy it and share the URL on your LinkedIn profile.

✅ Module Completion Checklist

Completed Documentation Best Practices module
Created GitHub profile with README
Documented home lab setup with architecture diagram
Created 2+ project showcase pages
Optimized LinkedIn profile for IT roles
Published first blog post
Made first open source contribution (any size)
Launched personal tech website
Linked portfolio everywhere (LinkedIn, resume, social)

📖 Resources & References

🚀 Next Steps

  1. Review all your portfolio work - is it cohesive and professional?
  2. Move to the Resume & Interview Preparation guide to pair your portfolio with a strong application package
  3. Link your portfolio URL on your resume, LinkedIn, and all job applications
  4. Share your best project write-up on LinkedIn for visibility
  5. Keep adding to your portfolio regularly - it grows over time