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

Recommended Content settings iteration #379

Open
1 task done
jeffpaul opened this issue Nov 17, 2022 · 1 comment
Open
1 task done

Recommended Content settings iteration #379

jeffpaul opened this issue Nov 17, 2022 · 1 comment

Comments

@jeffpaul
Copy link
Member

Is your enhancement related to a problem? Please describe.

The current Recommended Content block takes input from a user via several controls, two of which are the Categories and Tags multiselect boxes. Let's look into an iteration here that:

  1. Sets the Post type field to the same post type for the currently edited post type (e.g., if editing on a Page, then set the Post type to Page).
  2. Set the Categories and Tags to be the same as the currently edited post type (e.g., if editing on a Page that's set as Categories=Sports, Tags=[Soccer, Technology], then set those categories and tags as the default ones for the Recommended Content block).
  3. Add a Use this Post's Categories and Tags toggle that defaults to enabled and sets those fields based on Integrate Watson API for image recognition #2 above. This makes those fields uneditable (or alternatively hides them). Disabling this toggle makes the Categories and Tags fields editable.

Props to @jakemgold for the inspiration on this UX improvement.

Designs

Use This Posts Categories And Tags setting enabled and showing full view of pre-set fields:
UseThisPostsCategoriesAndTags_EnabledFullView

Use This Posts Categories And Tags setting enabled but hiding the pre-set fields / collapsing them away from view:
UseThisPostsCategoriesAndTags_EnabledCollapsed

UseThisPostsCategoriesAndTags_Disabled:
UseThisPostsCategoriesAndTags_Disabled

Describe alternatives you've considered

n/a

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jeffpaul jeffpaul added type:enhancement help wanted Extra attention is needed type:good-first-issue Good for newcomers. labels Nov 17, 2022
@jeffpaul jeffpaul added this to the 1.9.0 milestone Nov 17, 2022
@jeffpaul jeffpaul moved this to Incoming in Open Source Practice Nov 17, 2022
@jeffpaul jeffpaul moved this from Incoming to To Do in Open Source Practice Nov 17, 2022
@jayedul jayedul self-assigned this Feb 13, 2023
@jayedul jayedul moved this from To Do to In Progress in Open Source Practice Feb 13, 2023
@jeffpaul jeffpaul moved this from In Progress to In Review in Open Source Practice Feb 20, 2023
@jayedul jayedul moved this from In Review to In Progress in Open Source Practice Mar 20, 2023
@jayedul jayedul moved this from In Progress to In Review in Open Source Practice Apr 4, 2023
@dkotter dkotter modified the milestones: 1.9.0, 2.0.0 Apr 4, 2023
@dkotter dkotter modified the milestones: 2.1.0, 2.2.0 May 1, 2023
@dkotter dkotter modified the milestones: 2.2.0, 2.3.0 May 18, 2023
@dkotter dkotter modified the milestones: 2.3.0, 2.4.0 Aug 17, 2023
@jeffpaul jeffpaul modified the milestones: 2.4.0, Future Release Oct 20, 2023
@jeffpaul jeffpaul moved this from In Review to Backlog in Open Source Practice Oct 20, 2023
@jeffpaul
Copy link
Member Author

While we work on a replacement for Personalizer in #392 the work here can be put on hold until work wraps in 392.

@jeffpaul jeffpaul added BLOCKED and removed help wanted Extra attention is needed labels Oct 20, 2023
@jeffpaul jeffpaul removed this from the Future Release milestone Oct 16, 2024
@jeffpaul jeffpaul added this to the 3.4.0 milestone Oct 16, 2024
@jeffpaul jeffpaul modified the milestones: 3.4.0, 3.5.0 Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

3 participants