Unveiling the new Admin Dashboard (preview)

[waiting-for-dev]

We're releasing the first alpha version of solidus_admin. Our new admin dashboard still needs to be completed, but it's 100% usable and adds value by itself. We don't want to work on it behind closed doors and then show you what we think you want. Instead, we'd like everyone to try it out, listen to your feedback and create the solution you and your clients actually need.

In this initial launch, we present you with a fresh and revamped product listing with excellent UI and UX and new features like live search and bulk actions. You can also start exploring the new components-based architecture, making it easier to implement forward-compatible customizations.

solidus_admin_demo.webm

Switching Between Old and New Admin

During this development phase, where only some sections have been reworked, the new admin dashboard will transparently fall back to the old solidus_backend you are familiar with.

Operators can also explicitly opt-out by using a toggle switch on the menu's left side.

Trying the new admin

We encourage you to check the new admin dashboard out and have your voice heard with any new ideas or concerns. You have two options:

1. Try the new admin in an isolated environment
2. Try the new admin in your store

Its source must be the admin/alpha/v1 branch in the solidusio/solidus repository on GitHub.

Try the new admin in an isolated environment

• Clone the Solidus repository: git clone https://github.com/solidusio/solidus.git.
• Navigate to the generated directory: cd solidus.
• Checkout the tag: git checkout admin/alpha/v1.
• Build and start the sandbox application: bin/rails server.
• Open your browse and visit http://localhost:3000/admin. You should see the new admin once you click on the "Products" menu item.

Try the new admin in your store

• First, you must upgrade your store to fetch the main branch of the solidusio/solidus repository. We recommend following the upgrade instructions up to Solidus v4.1 and then update your Gemfile, splitting how solidus dependencies are fetched:

git "https://github.com/solidusio/solidus.git", branch: "admin/alpha/v1"  do
  gem "solidus_core"
  gem "solidus_api"
  gem "solidus_backend"
  gem "solidus_admin"
end

• Run bundle update
• Run bin/rails g solidus_admin:install
• Run bin/rails server
• Visit http://localhost:3000/admin in your browser. You should see the new admin once you click on the "Products" menu item.

🚧 WARNING 🚧

Notice that any customization you made on the legacy admin will not automatically be transferred to the new admin dashboard. We'll publish detailed instructions on customizing the new admin and port legacy patches as soon as possible.

🚧 WARNING 🚧

Troubleshooting

If you encounter any issues during installation, please make sure to follow the instructions we provided above.

For further assistance, we can help troubleshoot your issue.

Feedback

We appreciate any feedback on the alpha version of Solidus Admin! Please comment on a GitHub discussion or open an issue if you find any bugs. Thanks!!

[tvdeyen]

Great work! This looks amazing. Will try it out in the next couple of days and will try to provide (valuable) feedback.

First thing I noticed in the video above is that the icon used for the quick filter is a "sort list" icon. Any particular reason why you have not used a search icon instead?

[waiting-for-dev]

Thanks, @tvdeyen! ❤️

Not sure that conveys sorting, as that's the "filter-line" icon from remix: https://remixicon.com/icon/filter-3-line 🤔

[waiting-for-dev]

Other than that, it was the one given to us in the design, but of course we can talk to change it if we feel its confusing!

[peterberkenbosch]

Excited about this! Playing with it a little bit more next week, wanted to share first thing I ran into though. The Give Feedback link is 404-ing (https://solidus.io/feedback?category=solidus-admin).

[waiting-for-dev]

Thanks for reporting! The link is fixed now 🚀

[zachfeldman]

Awesome can't wait to try it!

We tried putting it at /new_admin but it seems like some of the paths are maybe hardcoded to /admin. Could you all make sure it can be hosted at other URLs just so we could deploy it alongside existing admin? Thank you!

[waiting-for-dev]

Update: it's been already backported to the admin/alpha/v1 branch. Please, update your bundle and try once more 🙏

[zachfeldman]

Nice thanks @waiting-for-dev . It is now loading, but I'm not seeing the new look on the Products admin. Maybe @elia could take a look at my open PR on our project to get a sense for what's wrong? I tagged him there. Appreciate all of your help.

[waiting-for-dev]

That's weird... To confirm, did you try playing with the left sidebar toggle switch, right?

A couple of ideas come to my mind for debugging it:

• Make sure you have the mount SolidusAdmin::Engine line before the mount Spree::Core::Engine one.
• Could you confirm the value of the solidus_admin cookie every time you click on the toggler?

By the way, Elia is enjoying some days off, so feel free to contact me for anything.

[zachfeldman]

I can't tell you why, but I created a new branch from @filippoliverani 's 4.1 branch and now it's working locally - awesome!

I'm trying to get a Review App up on Heroku so I can show the internal team here at @FrameworkComputer, but bin/rake assets:precompile fails on Heroku build with the following error:

       Running: rake assets:precompile
       
       Rebuilding...
       
       Done in 626ms.
       Specified input file /tmp/build_1582f9c9/app/assets/stylesheets/application.tailwind.css does not exist.
       rake aborted!
       Command failed with exit 9: /tmp/build_1582f9c9/vendor/bundle/ruby/3.1.0/gems/tailwindcss-rails-2.0.30-x86_64-linux/exe/x86_64-linux/tailwindcss
       /tmp/build_1582f9c9/vendor/bundle/ruby/3.1.0/gems/tailwindcss-rails-2.0.30-x86_64-linux/lib/tasks/build.rake:7:in `system'
       /tmp/build_1582f9c9/vendor/bundle/ruby/3.1.0/gems/tailwindcss-rails-2.0.30-x86_64-linux/lib/tasks/build.rake:7:in `block (2 levels) in <main>'
       /tmp/build_1582f9c9/vendor/bundle/ruby/3.1.0/gems/sentry-ruby-5.10.0/lib/sentry/rake.rb:26:in `execute'
       Tasks: TOP => assets:precompile => tailwindcss:build
       (See full trace by running task with --trace)

 !
 !     Precompiling assets failed.
 !
 !     Push rejected, failed to compile Ruby app.
 !     Push failed

I can file an issue in the project if you'd like.

[waiting-for-dev]

Thanks for reporting, @zachfeldman. It looks like deploying fails because the build directory is no longer there. We'll investigate how to work around that.