What’s changed on fueko.net

Over the past few weeks, my site has gone through its biggest update in years. It began with the move to Polar ↗ as my primary sales platform. Polar now handles payments and purchase management. That change opened the way for a customer account and a broader rebuild of how the site handles documentation, updates, and support.

The new customer account is one of the most practical results. After signing in, you can find your license keys, Perks status, and update notification settings in one place. From there, you can also open your Polar customer portal for invoices, order history, and purchased products.

I’ve wanted to do something for people who regularly support my work. Perks gives that idea a first form: after verifying your license and the site using the theme, you’ll receive a discount code for your next purchase. It’s a starting point I can build on.

I also added Loop to make the work on each theme easier to follow. It shows recent updates, the theme I’m working on now, what comes next, and themes maintained outside the current update cycle. Loop isn’t a roadmap. Ghost may require an urgent update, or a particular theme may need attention sooner than planned. That’s why it shows where things stand without promising specific features, scope, or release dates.

The move to Polar also meant accounting for purchases made through ThemeForest. There are now two purchase paths, so I’ve separated documentation, support, and policies wherever those paths work differently. If you bought a theme on ThemeForest, you can migrate at no additional cost. The migration verifies your purchase and lets you claim a new Polar license. It does not transfer or change your original purchase: your Envato license remains valid under the same terms. The new license gives you access to the customer account, Perks, and the new features.

Purchases through Polar now have their own sales terms. Development and staging environments do not count toward the license limit, and multilingual versions of the same site count as one project. Those purchases are also covered by a money-back guarantee. I’ve rewritten the support and update policies to make it easier to see what comes with a theme.

Documentation is now part of the site, so I can maintain it alongside the themes. Theme pages are changing too. They include more detail about features, technical information, licensing, support, and who each theme is for. Notes belongs to this shift as well: it gives me room to explain decisions that don’t fit on a product page.

The rebuild isn’t finished. The account and policies are in place, while other pages are still evolving.