Pathauto Project - Update Categories

Created on 27 April 2022, over 2 years ago
Updated 12 May 2023, over 1 year ago

See instructions on the Parent Issue 📌 [Meta] Pathauto Project updates for Project Browser Closed: outdated

Proposed Resolution

  1. Path Management
  2. Site Navigation
  3. Utility
📌 Task
Status

Postponed

Version

1.0

Component

Contrib changes

Created by

🇬🇧United Kingdom ChrisDarke London

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States leslieg

    Postponed until a new smaller list of Categories is finalized.

  • Status changed to Needs work 7 months ago
  • 🇺🇸United States leslieg

    Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.

  • 🇺🇸United States tishmg

    I am working on this issue. #Portland2024

  • Status changed to Needs review 7 months ago
  • 🇺🇸United States tishmg

    I have reviewed Pathauto's description and think these categories are the best fit:

    • Automation: because paths are autogenerated based on user-defined patterns
    • Site structure: because having clearly defined paths provides structure to the website, thereby helping users navigate the website.
  • 🇺🇸United States kbeck303

    I'd like to propose adding "Search Engine Optimization (SEO)" and "Accessibility" to the list because better URL structure is important for both of these categories.

    1. Administration Tools
    2. Content Editing Experience
    3. Search Engine Optimization (SEO)
    4. Accessibility

  • 🇺🇸United States bsnodgrass

    We have a maximum of 3 categories to be assigned to a module with the new module category list.

    I agree with Search Engine Optimization (SEO) in clearly defining a human-readable URL alias that can be given a logical hierarchy for the path to match site structure and/or navigation. This I think is the number one choice.

    I think administration tools are appropriate as they give site administrators no-code tools to configure URL alias patterns, which is a big plus for maintaining site structure.

    I would propose these two over automation tools (it is automatic once patterns are setup, you can also bulk update URL alias if patterns change, but the process is manually initiated.

    AFAIK there is nothing in accessibility guidelines for URL Alias patterns.

    Editing Issue Summary, keeping the status at Needs Review.

  • 🇺🇸United States r.aubin

    I agree with SEO and Administration tools. It looks like "Site Structure" is struck out currently, but I think keeping that as the 3rd category (or maybe even ranked 2nd) makes sense. It's an extension of your content model, defining how it gets exposed to end users by URL.

    1. SEO
    2. Site Structure
    3. Administration tools

  • 🇮🇪Ireland lostcarpark

    Agree with bsnodgrass.

    SEO is clearly the main function of the module.

    Administrative tools is also a good fit.

    I was wavering on Automation Tools. Ultimately, it is automating the process of generating URLs for pages. However, I'm skeptical that someone is going to be thinking of automating URL generation when they look in the automation category, so I can't see it being useful to add it there.

  • Status changed to RTBC 5 months ago
  • 🇺🇸United States leslieg

    Agree with comments in #16. Moving to RTBC and removing two extra categories from Proposed Resolution

  • Status changed to Fixed about 2 months ago
  • 🇺🇸United States leslieg

    Currently set to SEO and Auti=omation. While people could generally look for cool things under admministration tools, we decided to leave what the maintainer has.

    Assigned credit and marked as fixed.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024