BUGFIX

The About you field now holds you to the same limit the server does, two paragraphs of 250 characters, and says what to change instead of failing with no explanation.

Stripe needs an email on the paying customer before it will confirm a subscription, so Upsoma now supplies the learner's address and a card payment settles in place instead of stopping at Confirm.

The header trail now reads Paths, the path, then the tab or the layer and chapter you are on, and Back to roadmap opens the roadmap every time.

Upsoma tightened its public, protected, admin, changelog, and generation wait states so the MVP is easier to evaluate end to end and learners see useful recovery or progress instead of blank or clipped layouts.

The About you field now holds you to the same limit the server does, two paragraphs of 250 characters, and says what to change instead of failing with no explanation.

Stripe needs an email on the paying customer before it will confirm a subscription, so Upsoma now supplies the learner's address and a card payment settles in place instead of stopping at Confirm.

The header trail now reads Paths, the path, then the tab or the layer and chapter you are on, and Back to roadmap opens the roadmap every time.

Upsoma tightened its public, protected, admin, changelog, and generation wait states so the MVP is easier to evaluate end to end and learners see useful recovery or progress instead of blank or clipped layouts.

While your paths load, the Paths page shows its tabs and placeholder cards instead of a loading sentence, so nothing jumps when they arrive.

Upsoma tightened its public, protected, admin, changelog, and generation wait states so the MVP is easier to evaluate end to end and learners see useful recovery or progress instead of blank or clipped layouts.

Admin analytics controls now sit with the analytics page identity while account actions stay isolated on the right, matching the catalogue header pattern.

The admin analytics page now uses the same connected header stack as the catalogue console, with Analytics as the single page label.

The About you field now holds you to the same limit the server does, two paragraphs of 250 characters, and says what to change instead of failing with no explanation.

Stripe needs an email on the paying customer before it will confirm a subscription, so Upsoma now supplies the learner's address and a card payment settles in place instead of stopping at Confirm.

The header trail now reads Paths, the path, then the tab or the layer and chapter you are on, and Back to roadmap opens the roadmap every time.

Upsoma tightened its public, protected, admin, changelog, and generation wait states so the MVP is easier to evaluate end to end and learners see useful recovery or progress instead of blank or clipped layouts.

When a fresh lesson is still generating, learners now see the stage they are in - mapping the skill to the path, drafting the unit, then running content checks - instead of sitting on a generic loading state.

Admin analytics controls now sit with the analytics page identity while account actions stay isolated on the right, matching the catalogue header pattern.

The admin analytics page now uses the same connected header stack as the catalogue console, with Analytics as the single page label.

When a fresh lesson is still generating, learners now see the stage they are in - mapping the skill to the path, drafting the unit, then running content checks - instead of sitting on a generic loading state.

Opening a fresh chapter no longer holds the request hostage while lessons generate - the platform answers instantly, generates in the background, and your screen picks the content up the moment it is ready, ending the 504 timeouts on hosted environments.

Upsoma tightened its public, protected, admin, changelog, and generation wait states so the MVP is easier to evaluate end to end and learners see useful recovery or progress instead of blank or clipped layouts.

When a fresh lesson is still generating, learners now see the stage they are in - mapping the skill to the path, drafting the unit, then running content checks - instead of sitting on a generic loading state.