No category base — What about “no tag base” ?

  • This is not (yet) a concrete proposal, rather an open-end question, as I have not made up my mind on this yet. Curious for input!

    • The purpose of this your plugin is clear to me.
    • Your FAQ also list Won’t this conflict with pages? and answers it clearly that this ain’t a problem as long as one avoids name conflicts between the page namespace and the category namespace. So far so clear.

    What about tags? Could your plugin also include a setting “tag base”? It would be ON by default (WordPress standard) and can be toggled OFF on demand.

    • I imagine the consequences of “tag base: off” to be the following:
    • You can have top level slugs for tags like /tag1 and /tag2.
    • As long as they don’t conflict with pages or categories this would work friction free. Would it?
    • Independent of not having a tag base and/or category base one could still have an index page for all categories and all tags, at e.g. at /categories and /tags respectively.

    What do you say?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Marios Alexandrou

    (@marios-alexandrou)

    If you’re asking if it’s possible, the answer is yes.

    If you’re asking if this is something I’m going to work on, the answer is no. I’m not currently working on or thinking about extending this particular plugin’s features.

    Thread Starter abitofmind

    (@abitofmind)

    Ok and ok. Beyond that (the open discussion part): What’s your take on it? Could this be useful in practise? Which use cases do you see? Which problems do you see? SEO-wise, usability-wise, staff-wise, 3rd plugins stability wise (hardcoded assumptions). Curious on your take.

    By tendency:

    Categories are few, well named, rarely changed. On some sites possibly under editorial control, not extend-able by every little contributor.

    • ? So a good candidate to make an exception for and allow for a namespace overlap with pages.

    Tags are created frequently and by every contributor, possible even redundant among themselves

    • ? Not a good candidate to mix into the global namespace.

    But there are also some neutral aspects:

    • ?? Tag base does not serve as a URL component for blogposts, so one consequence less.
    • ?? There could be scenarios where it is a primary goal that categories and tags are valid top level candidates. Be it SEO or also as a simple means for using tags as landing pages to topical clusters, etc. If that’s a primary goal, then the discipline needed to avoid name conflicts may be worth to achieve that primary goal.

    But I did yet not see any concrete need. So at the moment very fuzzy/theoretical. Hence curious on your take!

    • This reply was modified 9 months, 2 weeks ago by abitofmind.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘No category base — What about “no tag base” ?’ is closed to new replies.