I'm not sure this is an actual portfolio.
I've browsed what appears to be a mix between a blog and a resume...
While the resume part is probably essential, regarding actual portfolio work, you should do more "show" than "tell".
It's ok to explain the premice, but displaying your blog posts to a potential recruiter or publisher (I assume this is the purpose of your current endaevour?) will only let them know you are opiniated, and won't do much in regards to explaining what your skills are.
If at all possible, I'd dedicate a section of videos with brief explanations of context and the logic behind how you've organized your work.
The video will display what you can do (results) and the paragraphs will explain, to a more technical audience, how you've achieved it (and whether they believe this is a good way to do it).
Lastly, I'd join effort with an artist, if only to skin your UI and add some visual. The reason for this is twofold:
- Part of the people that browse portfolios are not necessarily tech-savvy, and having some eye-candy might draw their attention before they send it over to the tech guys (for example, in a previous office, the HR in charge of recruiting programmers would look up and find suitable candidates before forwarding their work to our tech director, which would then pick the best).
- It will give you more experience with integration, iteration, etc.
- (Bonus) If the artist is also trying to build a portfolio, he'll be happy to do it for free because he'll be able to work with an actual programmer, giving him a serious edge over other potential competitors (artists) that are good "on paper" with no actual work to show for. It's better for you, and its better for him, so do it