[Idea] Clarify use of Bulk Importer with UX tweaks and hints?

[kathep]

The problem

The Bulk Importer instructions are a bit frustrating and misleading for beginner Prestashop users as they are currently designed.

The solution

This could be easily improved with a few UX improvements and hints.

For example, the bulk importer only works when the top three toggles are at an 'off state' (on screen 1 of bulk import) AND the 'ID' category is set to ignored AND the root category is set to ignored (on screen 2 of bulk import). This example is for bulk importing categories, I'm sure there will be other columns in other bulk imports that need to be ignored for import to be successful. It is possible to find which columns these 'ignore necessary' columns are by a lot of searching of forums and Github issues, but it would be much kinder to users to list at least some of the common ones in the interface itself.

Screen 1 bulk import UX improvement
Perhaps the top three toggles could be removed, or a hover-over note, or instruction below could suggest something like "Recommendation: leave off unless you know what you are doing."

Screen 2 bulk import improvement
Perhaps when the data for a bulk import is previewed in the second screen, a note could be added to indicate the import is much more likely to be successful when certain columns are changed to 'ignored'. This could be something like: "Set ID and Root columns to 'ignore' unless you know what you are doing."

I am happy to contribute to this feature being added. Please note though that I am a beginner at using Github. I am not confident at pull requests etc. So if this is required of me, I will need a little guidance and/or patience from my collaborators.

Alternatives

No response

Additional context

No response

Do you plan to work on this subject?

• I'm willing to contribute a formal specification.
• I'm willing to provide any wireframes or design assets required for this feature.
• I'm willing to submit a Pull Request that implements this feature.
• I'm willing to help verify that the implemented feature works as intended and produces no unintended side effects.