Just a developer who likes to build things...like ProjectGallery.me!
You're currently viewing this on a v1/beta of my portfolio site, ProjectGallery.me.
Why?
Like other developers, I want to be able to showcase my work in a simple portfolio. But, man, portfolio competition is fierce out there. They range from either crazy flashy to simple elegant designs.
But some of us would rather spend time working on projects than spending cycles trying to figure out how to show those projects.
That's where ProjectGallery comes in.
The goal is to turn down the volume on the presentation by depersonalizing and allowing the work to speak for itself. And the best way to do that is to create a general use platform.
Why not Github, Linktree, or even a blog?
There are other solutions that do a great job. But they just slightly miss what I'm aiming for.
Github is great for showcasing your projects in their most raw form. You can even add context with a Readme. Discovery is the main issue here.
And Linktree is great for acting as an at-a-glance overview of any and every link you could want. But it's all redirection to content. But no actual content.
And a blog is great for expanding on specific topics, it's not the best format for showcasing a collection of work.
Why not "all of the above?"
With ProjectGallery, I'm aiming to take a little bit of each and sprinkle them together.
A user landing page presents the option to view your projects and your posts, as well as any links or arbitrary notes you'd like to present. From there, viewers can quickly drill down to the content they want to see, including more detail like project screenshots, links, and journal about specific projects.
Still evolving
When I initially started this project, I just wanted to test some specific tools. Which means that I started with some of the ugliest non-design. But at this point, I'm excited by the prospect of this being useful to others. While the portfolio landing pages have received a fair bit of makeover from their original form, the same can't be said for the rest of the platform. So, I've still got some work to do.
My current active project is ProjectGallery
Tasks
- Add drag/drop sorting for list items.
- Allow top-level Projects and Posts buttons to be sortable
- Update custom links to allow for either links or general markdown content
- Add editing for custom text content and links (recreating this for every edit sucks!).
- Finish reworking pages with old "design" (if you could call it that)
- Add custom text content to project pages
- Add onboarding
- Add contact form option
- Add drag/drop image upload to journal entries
- Figure out top-level organization to distinguish between project journal entries and personal/general journal entries
Longer Term Todos
- Implement sub profiles for more tailored presentation for different purposes.
- Export for self hosting
I've contributed to a handful of open source projects, notably a significant update for Odysee, a blockchain-based video service. This PR contains +3,518/−8,027 changes and 80 comments worth of discussion.
The goal of that final PR was to upgrade Webpack, aiming to transition from Flow to TypeScript. This serves not only as a technical sample, but also a sample how I tend to work on a team.
Backstory
In 2022 I was actively contributing to the project due to my bullishness on the model (I only stopped due to the project losing viability due to external factors. Though...perhaps that's about to change...?). Since they were on an old version of Flow, I was discovering a number of issues that would have been caught by either a newer version or a switch to Typescript.
I originally proposed the work as a question about whether they intended to stay with Flow or had interest with moving to Typescript. After confirming their interest, I devoted my free time to upgrading Webpack, a step towards this transition.