Implementing my own Improved Polywork Style Portfolio
Firstly, I want to express my respect and appreciation for the hard work put in by the Polywork team on their product. Despite developing my own version, it doesn't mean I won't continue using their platform. They generously sent me unsponsored merchandise for being an active early adopter.
Polywork initially caught my attention with its general timeline feature, which I had implemented for myself back in 2019. They officially launched in 2020 as a generalized version of LinkedIn, accommodating both my craft beer enthusiasm and software development skills. However, the latter is more suited to Github as a specific platform.
Quickly adding my previous accomplishments to their platform, I aimed to integrate into Polywork and avoid the time-consuming updates needed on my self-hosted platform. My platform required constant attention to stay up-to-date, relevant, efficient, and SEO-optimized, disregarding security implications due to my previous approach being Static SSR.
However, on September 8th, 2023, Polywork announced changes that significantly reduced my appeal, except for the SEO element. I hope they reconsider some features, like clubs, feeds, and opportunities, mentioned in their previous posts.
Polywork seemed only marginally better than the simplified timeline Github Repo I created before their launch. Still, I continued hosting my blog on my domain. As a coder by nature, I had countless possibilities, especially when I was self learning in the free time that I had to assist INEVITABLE.
Having a self-hosted blog since 2018, and a preference for Nuxt as a Static SSR framework, I searched for open-source repositories as a baseline for my new portfolio. I found Fayaz Ahmed's portfolio on Github, an excellent starting point to re-implement my timeline feature using Nuxt Content.
If you're interested in a technical blog post, open-sourcing this, making a PR into Fayaz Ahmed's Github repo, or anything else, feel free to reach out below.