Add initial shipments documentation for end users #2784
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tvdeyen
reviewed
Oct 5, 2018
benjaminwil
force-pushed
the
user_guides/settings/shipping
branch
from
f7029f8 to
adec11c
Compare
|
Fixed! Sorry about that. |
benjaminwil
force-pushed
the
user_guides/settings/shipping
branch
from
adec11c to
3ec9897
Compare
ericsaupe
suggested changes
Oct 15, 2018
benjaminwil
force-pushed
the
user_guides/settings/shipping
branch
from
3ec9897 to
ddb3676
Compare
----------------------------------------------------------------------- This commit improves the user experience of the "Stores" page in the admin interface in the following ways: - It clarifies what the "Code" field does. - It renames the the code field "Slug" in the UI only. This is less ambiguous for users who are creating a new store and don't know what to put in this field. - It ensures that all of the fields on the page have the same capitalization style. Note: The UX is still pretty bad. We do not want admins to think making changes to stores is trivial. We should rethink this page and make more major changes to it. Mark "Name" as required for new shipping methods ----------------------------------------------------------------------- When a store admin creates a new shipping method, the "Name" field should be marked as required. This commit also cleans up some extra spacing in the new shipping method form and fixes the data hook for `admin_name`, which was mis-named to say `internal_name`. Update locales strings ----------------------------------------------------------------------- This commit removes unused locales strings. It also changes the capitalization of some existing locales strings so that the stock locations form has consistent capitalization.
This commit adds information about everything store administrators need to get started with the `solidus_backend` interface at the URI `/admin/settings/shipping`. - Tweak product SEO docs; add links to stores docs - Add all settings article stubs - Add shipping settings docs for end users - Adds information about shipping calculators and stock locations.
benjaminwil
force-pushed
the
user_guides/settings/shipping
branch
from
ddb3676 to
2b952f5
Compare
jacobherrington
approved these changes
Nov 23, 2018
2 tasks
|
Closing, I'm reopened this into #3092. Thanks anyway @benjaminwil! |
|
No problem. Didn't intend to abandon this, and I fixed that YML – why couldn't we merge it? |
|
There was a conflict in the yml file yet so it couldn't allow me to merge. No worries, you have the owership of the commits in the PR I just open, so it does not change much. Thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds documentation about the Solidus shipping interface for end users. The audience for this documentation is store administrators or anyone who has to touch the
solidus_backendas a business person.It also changes some of the English translation strings for the backend interface, which is a minor UX improvement.