Feature: Improve UX for parse ingredients

[CloCkWeRX]

First Check

• I used the GitHub search to find a similar requests and didn't find it.
• Checked the tasks tagged issues and verified my feature is not covered

Please provide a concise description of the problem that would be addressed by this feature.

When editing a recipe's ingredients; I found it difficult to locate the Parse control after using settings to enable detailed ingredients.

Step 1:

Here, I am manipulating overall recipe settings. I thought that "parse all ingredients" might be in close proximity to this.

Step 2: Scrolling through all of the ingredients to locate the parse button

Unlike add or bulk add, parse isn't an action to append to the list, it feels more like a secondary action similar to "save all ingredients"

Step 3: in parsing mode

I work my way through reviewing and adjusting; having to return to "save" at the top of the form.

Please provide a concise description of the feature that would resolve your issue.

Recipe edit page:
Locate parse button closer to settings control.

Ingredient parser page:
Position: sticky for the save controls, so they are on screen as I scroll through the list (or shift to bottom of form)

Please consider and list out some caveats or tradeoffs made in your design decision

Unsure if there is a current UX style guide or similar being followed/this violates those rules.

Additional Information

• If this is accepted I'm willing to submit a PR to provide this feature
• If this is accepted I'm willing to help maintain this feature
• I'm willing to sponsor/pay a developer to do this work

[CloCkWeRX]

Related #2532

[michael-genson]

Yup I agree this workflow can use some work. Even on Desktop having the "parse" button being far from the settings options is unintuitive

[CloCkWeRX]

Recipe edit > Ingredients

Mucking about in desktop view:

Or moving everything in mobile view:

(I feel like "add" / "bulk add" still live at the bottom logically, for an empty list they would "start" at the top/don't have the same issue)