So basically, the "plaintext" look, but with a tad of HTML for titles and important labels?

 

Sure that could work!

Or maybe like a nice GitHub Readme.md page? Good backend developers always have very readable documentation on APIs for example. This way you can use markdown to highlight and categorize

I guess the HTML version could match what you were trying to propose?

artemix.org/portfolio.html

Note that the txt version is made to be sent over e-mail, directly embedded as text message.

Yes that looks much better!

Try combining that with any new UX concepts you are learning about plus the suggested grouping.

Totally agree with @Kostas.
Also add links to the git repo, and make sure that each project is well documented and have clean code, even if is not a very complicated project. There is a good article here about how to make readme files.

code of conduct - report abuse