WordPress.org

Making WordPress.org

Opened 22 months ago

Closed 18 months ago

Last modified 9 months ago

#1573 closed task (fixed)

Categories (née Tags)

Reported by: obenland Owned by: obenland
Milestone: Priority: high
Component: Plugin Directory Keywords:
Cc:

Attachments (2)

1573.diff (30.2 KB) - added by obenland 18 months ago.
image.png (252.5 KB) - added by samuelsidler 18 months ago.
Screenshot on iOS

Download all attachments as: .zip

Change History (48)

#1 @obenland
22 months ago

  • Description modified (diff)

#2 @obenland
21 months ago

@ipstenu mentioned an idea:

Curated categories: "Best of April", "Pick of the week"

#3 @samuelsidler
21 months ago

Fwiw, I wouldn't consider comment 2 as part of tags, but perhaps a separate view/filter/whatever that we'd have to build.

#4 @dd32
19 months ago

  • Type changed from enhancement to task

#5 @samuelsidler
19 months ago

As mentioned and discussed, we're moving from tags to categories.

For this ticket, we have a few things we'll need to do:

  • Create the categories, in a way that's localizable.
  • Output the categories on the plugin detail page (already done?).
  • Allow plugin authors to add categories to their plugins in the plugin admin (maximum of three).
  • As part of the migration script, map current tags to categories.

I think comment:2 (and the Featured "category") should be a separate taxonomy that doesn't display on the plugin detail page. Thoughts?

The other two proposed taxonomies will be completed in other tickets.

#6 @samuelsidler
19 months ago

  • Summary changed from Tags to Categores (née Tags)

#7 @samuelsidler
19 months ago

  • Summary changed from Categores (née Tags) to Categories (née Tags)

#8 @dd32
19 months ago

In 3225:

Plugin Directory: Rename Tags to Categories and add the extra taxonomies we plan on using.

See #1573

#9 @dd32
19 months ago

In 3226:

Plugin Directory: Add term translation.

See #1573

#10 @dd32
19 months ago

In 3228:

Plugin Directory: Update a missed taxonomy name and correct a typo.

See #1579, #1573

This ticket was mentioned in Slack in #meta by obenland. View the logs.


19 months ago

#12 @obenland
19 months ago

  • Priority changed from normal to high

This ticket was mentioned in Slack in #meta by netweb. View the logs.


19 months ago

This ticket was mentioned in Slack in #meta by obenland. View the logs.


19 months ago

#15 @obenland
19 months ago

  • Milestone set to Plugin Directory v3 - M5

#16 @obenland
19 months ago

  • Owner set to obenland
  • Status changed from new to accepted

#17 @obenland
19 months ago

  • Status changed from accepted to assigned

This ticket was mentioned in Slack in #meta by obenland. View the logs.


18 months ago

#19 @obenland
18 months ago

In 3322:

Plugin Directory: Update term name.

Per samuelsidler.

See #1573.

#20 @obenland
18 months ago

In 3323:

Plugin Directory: Disable unused taxonomy meta boxes.

For now only Plugin Cateogories are important, the other taxonomies will be
added at a later point in time.

See #1573.

#21 @obenland
18 months ago

In 3324:

Plugin Directory: Limit the amount of assignable categories to 3.

See #1573.

@obenland
18 months ago

#22 @obenland
18 months ago

@dd32: I added a suggestion as to how to handle tag to category conversion on import: 1573.diff.

Should we convert the category slugs to IDs in the map directly or continue with slugs and getting IDs?
Is that spot in the importer a good point to do the conversion or should it be done somewhere else?

#23 follow-up: @dd32
18 months ago

@obenland currently the sync script uses the same importer.
I'm curious if you think we should be coverting tags on each import, or if we should instead just do it once as a one-time migration?

I'm kind of thinking the add plugin form should ask the submitter to choose the categories, and we should only assign categories automatically for existing plugins.

#24 in reply to: ↑ 23 ; follow-up: @obenland
18 months ago

Replying to dd32:

I'm curious if you think we should be coverting tags on each import, or if we should instead just do it once as a one-time migration?

Not sure how much this would hold up each sync, but it should be enough to do it once. Should I just add the class and not hook it up for now?

I'm kind of thinking the add plugin form should ask the submitter to choose the categories, and we should only assign categories automatically for existing plugins.

That sounds reasonable, I'll add it to the upload shortcode.

#25 in reply to: ↑ 24 @dd32
18 months ago

Replying to obenland:

Replying to dd32:

I'm curious if you think we should be coverting tags on each import, or if we should instead just do it once as a one-time migration?

Not sure how much this would hold up each sync, but it should be enough to do it once. Should I just add the class and not hook it up for now?

It's not a performance issue to run it every time, it's more of that we don't want to be overriding their category selection in wp-admin every time they commit a change :)
Perhaps we should only run it if the post doesn't have any categories assigned?

#26 @obenland
18 months ago

Yes, let's do that

#27 @obenland
18 months ago

In 3328:

Plugin Directory: Import tags and map them to categories.

Maps existing tags, that are part of the top 1000 most used tags, to their new
categories. Mapping only occurs for up to three categories and only if there
are no categories set yet.

H/t samuelsidler for putting together the tag/category spreadsheet.

See #1573.

#28 @obenland
18 months ago

In 3335:

Plugin Directory: Let plugin authors select categories on upload.

Also refactors create_plugin_post() to me more of a direct wrapper of
wp_insert_post(). Front-end needs styles.

See #1573.

#29 @obenland
18 months ago

In 3337:

Plugin Directory: Update category styles in meta widget.

See #1573.

#30 follow-up: @obenland
18 months ago

@samuelsidler @dd32: Can you think of more to do here?

Example: https://wordpress.org/plugins-wp/category/media/

#31 @obenland
18 months ago

In 3340:

Plugin Directory: Update category slugs to match built-in terms.

See #1573.

#32 in reply to: ↑ 30 @dd32
18 months ago

Replying to obenland:

Can you think of more to do here?


Category pages should be sorted by Most Active Installs first I believe, in fact all archives should be (unless they've got another pre-selected order).

Last edited 18 months ago by dd32 (previous) (diff)

@samuelsidler
18 months ago

Screenshot on iOS

#33 follow-up: @samuelsidler
18 months ago

Spacing is weird on mobile (see screenshot). Can we change to text to a sentence instead?

Showing plugins in the "Media" category:

Something like that?

#34 in reply to: ↑ 33 @obenland
18 months ago

Replying to samuelsidler:

Spacing is weird on mobile (see screenshot). Can we change to text to a sentence instead?

Showing plugins in the "Media" category:

Something like that?

I find it a little wordy and I'm not sure how scalable it will be given the amount of taxonomies we're planning on using.
What about Category: Media to make it less redundant?

#35 @obenland
18 months ago

In 3342:

Plugin Directory: Order archives by install count.

See #1573.

#36 @obenland
18 months ago

In 3343:

Plugin Directory: Allow users to browse their favorite plugins.

See #1573.

#37 @obenland
18 months ago

In 3345:

Plugin Directory: Updated styles for upload form.

See #1573.

#38 @obenland
18 months ago

In 3346:

Plugin Directory: Second pass at upload form styles.

This time, let's be less intrusive on other styles.

See #1573, [3345].

#39 @obenland
18 months ago

In 3351:

Plugin Directory: Add a plural form for when there are more than one category.

See #1573.

#40 @obenland
18 months ago

In 3353:

Plugin Directory: Minor style tweaks.

Improves display of global search bar, local search bar, and categories.

See #1573, #1719.

This ticket was mentioned in Slack in #meta by obenland. View the logs.


18 months ago

#42 @obenland
18 months ago

  • Resolution set to fixed
  • Status changed from assigned to closed

#43 @obenland
18 months ago

In 3404:

Plugin Directory: Make missing section titles available for i18n.

See #1573.

#44 @dd32
18 months ago

In 3578:

Plugin Directory: Track plugin tags in a taxonomy.

See #1573

#45 @dd32
18 months ago

In 3579:

Plugin Directory: Hide the plugin tag UI for non-super-admins for now.

See #1573

#46 @samuelsidler
9 months ago

  • Milestone Plugin Directory v3 - M5 deleted

Milestone Plugin Directory v3 - M5 deleted

Note: See TracTickets for help on using tickets.