The last thing an IT Portfolio should be is overly complex.
Or overly pretty.

To understand, you should ask why you need a portfolio in the first place:

• Is it to impress a company in showing your keen eye for design?

or

• Is it to quikly and easily show your competence?

If the IT job you want is a developer job, then front end design makes sense.

But if the IT job you want is an IT job, your focus should be on showing IT competence.
And doing it as clearly as possible.

Imagine a recruiter scanning 100s of resumes per day.
They find yours and think, "Neat a portfolio."

You're already a step ahead.
You actually have a portfolio.

They then open it and think, "I don't even know where to start."

While your portfolio doesn't have to be overly pretty, it should also be easy to review.
NOT COMPLEX.
Someone looking to hire doesn't have time for that.

There are some good portfolios online that people have built.
But a lot of them are designed by software engineers for software engineer jobs.

When building yours, think designed by an IT professional, for an IT job.

That's how I built my portfolio. And it's how I've templated it for the IAM Portfolio Cohort.

Yours truly,
CyberAndChill