Following on from my previous post (devpad #5 - Visual Update), I've made significant progress in both design & functionality of the application. Since finishing University, I've been able to dedicate a lot more of my time outside of work to this project, however I'm also currently doing a study program that focuses on interview skills.
Design
While building the project, I've slowly had to start moving a lot of what were once SSR astro components, to client-loaded SolidJS components. This is mostly for the task cards themselves and the sorting interface. This is quite a bit more complex than the original inspiration sites that I listed in my last post. I think I have managed to hit 4 out of 5 of the design features that I identified from those inspiration sites, the only one missing is using different fonts for different sections. I will keep this one in the back of my mind and hopefully as I come closer to finishing this project I can find some suitable use-cases for this.
Screenshots
Below are some screen shots showing where the design is currently at (these are mostly for future me's reference)
Landing Page
Task List
Project List
Project Editor
Todo Diff
Future
One of the things that is still left to do is add an interface for declaring the technologies used for each application. I currently hard-coded this onto my website, so it would be nice to have this data within the devpad API itself. The interface for handling the todo updates also needs a bit of work, currently the approve/reject buttons for each individual item don't do anything.
Once the project manager is done and the tasks feel good to progress/complete, I'll release it to the main site (devpad.tools). After the release there are a couple features I feel are necessary:
- Calendar View
- Command Pallete (cmd+k)
- Goals & Milestones
Within "Goals & Milestones" I want to have essentially roadmaps that are project-independent. For my own use case, I want to layout my game development adventures in a sort of roadmap, as I have multiple games planned, each of these being their own projects, but connections between them. For example, I want to convert one of my projects from my earlier minecraft coding days into it's own standalone game, but there's many mechanics within that which I need to practice & refine if I want to make them into a standalone game. So my idea is that each of these mechanics could become their own "micro-games", essentially a game built around a mechanic, the mechanic being a building block for a future project. This idea could also be used to represent studying or professional job workflows, which I would 100% use myself in order to track updates to my progress.