Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make clear that the API fields are optional #72

Open
GrimLink opened this issue Apr 13, 2022 · 0 comments
Open

Make clear that the API fields are optional #72

GrimLink opened this issue Apr 13, 2022 · 0 comments
Assignees
Labels
backend ux The Magento 2 backend UX is unclear enhancement New feature or request In next major version Marked for next major release

Comments

@GrimLink
Copy link
Contributor

Currently when making a new website for the WPCI content you have 5 options;

  • Name
  • Base Url, of CMS content site
  • API username
  • API password
  • Enabled

Screenshot 2022-04-13 at 15 00 25

The current UX is unclear what the fields require from you as a maintainer of the store.

At least put the API fields onder an optional section (like a magento tab) for extra config options,
or add a label onder the API fields marking them optional.

Because now everything looks required.

@GrimLink GrimLink added enhancement New feature or request backend ux The Magento 2 backend UX is unclear labels Apr 13, 2022
@GrimLink GrimLink added the In next major version Marked for next major release label May 30, 2022
@GrimLink GrimLink self-assigned this May 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend ux The Magento 2 backend UX is unclear enhancement New feature or request In next major version Marked for next major release
Development

No branches or pull requests

1 participant