Allow reusing custom legacy backend menu items in the admin
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.3k
- Forks
- 1.4k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 62
Description
Whenever a store defines additional menu items it should be possible to easily back port the customizations to SolidusAdmin.
Some documentation on how to do that should be provided.
Long term solidus_backend items should stop relying on partials and a mix of data and templates, and just data. That way we could use the data structure directly to generate also the SolidusAdmin menu and have a swift migration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The named entry points are solidus_backend and SolidusAdmin; start by tracing how custom legacy backend menu items are defined and how the admin menu is generated. Determine the smallest compatibility path, then document how a store can reuse its customization in SolidusAdmin. Treat the longer-term data-only migration as a separate design scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100