Version 0.7.2 - Release Notes

Version 0.7.2 focuses on making the cube editor feel better at the exact moment a cube starts coming together.

The main theme is reducing friction: empty cubes should be easier to start, the card input should be clearer while it searches, and adding cards should feel much closer to instant.

This release also includes a new poll block for cube blog posts, an experiment around community cube discovery, and the first steps toward moving more card lookup work through CubeForge's own API.

🧱 Empty cubes are easier to start

The empty cube state in edit mode has been reworked.

Previously, an empty cube only showed a message telling you to use the search input above. That was technically true, but it was not very helpful. If a cube has no cards yet, the page should make the next action obvious.

Now the empty state includes the card input directly, along with an import button. You can immediately search for the first card or import a list without looking elsewhere on the page.

This should make newly created cubes feel less like a blank page and more like an editor ready for input.

🔎 The card input has been improved

The card input has received several small but meaningful improvements.

Search loading now keeps the spinner in the input while the dropdown shows result-shaped skeleton rows instead of the old "Searching..." text. This makes the waiting state feel closer to the final result list and avoids a text-only loading placeholder.

The input also now supports a Destination setting when adding cards from the cube editor. By default, selected cards go to the mainboard, but you can switch the destination to the sideboard-style Considering list before adding them.

That should make it easier to quickly collect ideas without committing every search result directly to the main cube list.

🗳️ Blog posts can include polls

Cube blog posts now have a simple poll block in the visual editor.

You can add a question, provide multiple answers, and let readers vote directly from the published post. After voting, readers can see the current results.

For now, polls are limited to cube blog posts and are not available in white papers.

⚡ Adding cards should feel more instant

Adding a card to a cube was already optimistic once the add operation started, but there was sometimes a delay before that operation could begin.

That flow has been tightened up, so selecting a result from the card input should now feel much closer to instant.

🖼️ A new default cover style

Cubes without cover images now use a new default cover treatment.

The old fallback was a bright blue-purple-pink gradient. It worked, but it was a bit aggressive and generic. The new version keeps the fallback mostly blue, using softer layered circles and a restrained blue-purple accent.

This should make image-less cubes look a little more intentional while still staying visually quiet next to real card art.

🌐 Trying image-less cubes on community pages

I am also trying an experiment: cubes no longer need a cover image to appear on community pages.

The requirement for community visibility is now based on the existing public/community rules and the minimum card count. The cover image requirement has been removed.

This may make community browsing more inclusive, especially for users who want to publish a cube before spending time on presentation. It might also make the community pages look worse if too many cubes are missing images, so this is something I may revisit or revert depending on how it feels in practice.

🛠️ Moving more card lookup work to CubeForge's own API

This release also continues the migration toward using CubeForge's own card API for more card lookup work.

The goal is to reduce pressure on Scryfall's public API and make CubeForge's card search experience more reliable over time. This is still work in progress, but 0.7.2 includes another step in that direction.

Scryfall remains an essential part of the ecosystem, and I want CubeForge to be a good API citizen. Moving more repeated lookup work behind CubeForge's own API and caching layer should help with that.

As always, if you notice anything off, please create a bug report here: Report a bug. You can also ask me directly in the CubeForge Discord.