META: Improve quant_purger UX

Created on 30 July 2023, over 1 year ago
Updated 5 March 2024, 9 months ago

Problem/Motivation

For better onboarding, note down UX improvements here and make child issues for each.

Steps to reproduce

Proposed resolution

As items are found, note them here and add a child issue as improvements will be worked on.

Remaining tasks

  • Note possible improvements
  • Work on improvements
  • Close this out once the most important UX improvements are done

User interface changes

Per child issues.

API changes

Data model changes

πŸ“Œ Task
Status

Postponed

Version

1.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Kristen Pol
  • Issue was unassigned.
  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    Unassigning for now.

  • Assigned to Kristen Pol
  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    Given this one is almost done, assigning to me.

  • Issue was unassigned.
  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    Didn't get to this so unassigning until the next batch of issues gets worked on. It's on the list for the next release:

    πŸ“Œ Possible targets for next release Active

  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    After recent client questions on using the purger, here are some thoughts on improvements:

    • Adding drush commands would be very helpful:
      • show path blocklist
      • show path allowlist
      • show tag blocklist
      • show tag allowlist
      • clear purger registry
      • show tags from purge table for a specific url
      • show urls from purge table for a specific tag
      • check queue for a specific url (not purger related but maybe helpful)
      • check quant logs for logs related to a specific node/term? (not purger related but maybe helpful)
    • Need more information on when the purger registry needs to be cleared
    • Create one or more tutorials (and/or update the docs) that steps through the process of changing configuration to handle a real-world use case such as a footer menu
    • After the above, update docs to include drush commands and add any additional information
    • Possibly add another message on the Purger tab explaining that all content must be reseeded when purger configuration changes
  • Status changed to Postponed 9 months ago
  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    Postponing for now. If you are interested in this issue, please leave a comment.

Production build 0.71.5 2024