solidusio / roadmap Goto Github PK

All officially supported payment extensions should work out-of-the-box with Solidus; now that the old Frontend is deprecated, they need to be adjusted and tested on the Starter Frontend.

The old implementation of solidus_stripe has a few issues.
We are now building a new extension, which will be compatible with the Starter Frontend, and will use Stripe Elements.

Managing permissions and roles via code is suboptimal as it requires intervention by developers.
Building an UI for this is not a great effort and it is something that many users have been longing for.

All officially supported payment extensions should work out-of-the-box with Solidus; now that the old Frontend is deprecated, they need to be adjusted and tested on the Starter Frontend.

Paperclip is deprecated and unsupported, with ActiveStorage being the recommended substitute.
Although some shops won't have issues in the short term, they will eventually face problems when updating the stack since Paperclip does not support newer versions of Ruby and Rails.
Our major concern is providing users with a solid migration path; however, we cannot see a zero-effort migration.

solidusio/solidus#5033

The current promotion system is not intuitive and presents a few issues, notably performance.

There are other problems, as noted in this PR: solidusio/solidus#4296 , which highlights a few solid points and aims at building a new system that we may swap in place of the old one, in time.
The idea here is to build an extension, then extrapolate the current system into its own extension, then finally swap the new extension in for the old one.

Currently, figuring out what Solidus needs to evolve is made harder because there are not enough data.
In addition to recurring user interviews, we plan to add telemetry (product analytics) to Solidus, to better understand how users engage with the software.

Product Analytics must be:

• Anonymous. We don't care about the who, only the what.
• Optional. Users need to be informed and can opt out if they don't wish to share any information to improve the product.

There are some challenges to face and choices to be made, e.g., where are data stored, who can access them, etc.

This is just a proposal, for now.

As part of the rebranding and the rework on the Admin UX, we start with restyling the navigation sidebar.