I spent the first two years of my career poking around WordPress theme dashboards trying to get my website to do simple things, when what I really needed was to get to the code.
Unfortunately, things have only gone further since then with the growth of the no-code movement, which makes building websites easier in the short-term, but at the expense of cookie-cutter sites, expensive fees, and most importantly - the inability to build with code.
Modern frontend development doesn't help much in this regard either. Countless students are churned through coding bootcamps every year, spending only a few weeks on these fundamental languages before learning the libraries and tools which seem to appeal to hiring managers. And as a result, many developers only learn how to do things with specialized tools without understanding the basics enough to know how to use them.
But there's still a gap when it comes to read-only websites, the kinds of websites that most people need. This area is filled with a host of cookie-cutter monthly services which effectively rent out websites, or WordPress. WordPress is great, but only because Drupal's a pain. WordPress' developer experience, server-reliance, and security vulnerabilities are probably far outweighed by its benefits for most of the organizations using it, but for many of them (and many more who just can't use it) they're prohibitive.
Primo is our attempt to build an intermediary tool - a fully approachable (any device, any technical background), enjoyable, and productive open-source tool for building and publishing common websites like blogs, landing pages, brochures, etc. Our hope is that it opens up the door for more people to start coding and publish their first live website within minutes without code, the command line, or documentation, creating a gradual learning curve towards modifying code and building full-stack applications.
Built the frontend as components in Fractal that they put together into the main site and other departments' websites on subdomains. Seeing them take those base components and build out other sites was a large inspiration for thinking about how components work in Primo.
Created official mobile app for iOS and Android using React Native & a WordPress instance as a headless CMS.
Collaborated on frontend and handed off for integration with WordPress.
The precursor to Primo which started as a way to put up a curriculum page for my code bootcamp students at a custom domain without having to pay for hosting. I was close to monetizing it as a cheaper/simpler site builder, but seeing its potential as a dev tool encouraged me to expand its scope into Primo.
My first Svelte project - an app that allowed my students to quietly tell me if I had belabored too much on a topic (bored), or if I was going too fast (confused), as well as ask questions. It was working well, but then COVID hit.
The podcast app I always wanted to exist - with shows split up into subgroups (called "stations") that would shuffle all the latest episodes from each. Built in React Native, but abandoned when I started teaching (and frankly because React Native is pain and there were 2^42 podcast apps by then).