915760 - Extend topic filters to use official list of options

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Search, defect)

Description

[Jannis Leidel [:jezdez]]

The list of tags to implement can be found here: https://developer.mozilla.org/en-US/docs/Project:MDN/Contributing/Tagging_standards#Tagging_and_search_filters

There are a few exceptions there, e.g. the "Add-ons & Extensions" option that is equivalent to a list of tags, not just one. There are also some filters that aren't implemented by tags but other custom queries. Those won't be able to be defined in the admin but will be hardcoded (at first).

This also requires the filters to have non-tag verbose names, that need to be translatable. The tags to filter for need to be translatable, too. In other words, this won't be able to be done with constance but needs an own data model.

Comment 1

[John Karahalis [:openjck]]

Sounds like these filters would go above and beyond the filters that Holly asked us to implement. I would like to check with her before we decide to do this.

Comment 2

[Eric Shepherd [:sheppy]]

(In reply to John Karahalis [:openjck] from comment #1)
> Sounds like these filters would go above and beyond the filters that Holly
> asked us to implement. I would like to check with her before we decide to do
> this.

That list actually comes directly from the list I got from Holly. If it has anything at all extra, then her list has shrunk since the copy I was sent, because I specified it as given.

Comment 3

[John Karahalis [:openjck]]

Ah, okay. I was mistaken. Thanks Sheppy.

Proceed, Jannis. :-)

Comment 4

[Jannis Leidel [:jezdez]]

Thanks all! :)

Comment 5

[hhabstritt]

Hey guys, this looks like the super list, which is great to see, but we won't be launching with all of these. 

For launch, we will stick to TOPICS and LANGUAGE selection only. Later, we can consider adding Doc Type and Skill Level when we can be sure they will return a comprehensive set of results. 

I was told that we will ultimately be collapsing DOM and API into one. Should we do so now into one line item/filter?
DOM & API

It also seemed valuable to have the following additional topics (thoughts?):
Canvas
Mobile
Tools


Tomorrow I am meeting with Jannis, Luke, Sean and David to get on the same page about UI of search and filtering. We will discuss an alternative search UI that in it's mvp version will be easier to implement and more flexible to work with the progress that has happened with the new MDN visual design. It's final version will be more in line with our audience and the search tool UI/interaction they like on GitHub and DDG. (a preview for the curious, but please reserve comments to email and not this bug thread: http://cl.ly/0s0B0s383v43)

Comment 6

[Eric Shepherd [:sheppy]]

(In reply to hhabstritt from comment #5)
> Hey guys, this looks like the super list, which is great to see, but we
> won't be launching with all of these. 
> 
> For launch, we will stick to TOPICS and LANGUAGE selection only. Later, we
> can consider adding Doc Type and Skill Level when we can be sure they will
> return a comprehensive set of results. 
> 
> I was told that we will ultimately be collapsing DOM and API into one.
> Should we do so now into one line item/filter?
> DOM & API

Yes. I would call it "APIs and DOM", and it should use the tag "API". I've updated the list.

> It also seemed valuable to have the following additional topics (thoughts?):
> Canvas
> Mobile
> Tools

I've added "Canvas".

How is "Mobile" different from "Firefox for Android", which we already have? And we already have "Tools."

Comment 7

[hhabstritt]

Sheppy, assumed mobile would offer docs that pertain to Android, iOS, Phonegap, FxOS, etc. Anything mobile, not constrained to Android. Are we only tagging Android related docs as "mobile"?

In the doc linked above we have Tools as a doc type. We won't be releasing with doc types, so I'm suggesting putting it among the topic filters in the initial release of filters. What do you think?

Comment 8

[Eric Shepherd [:sheppy]]

(In reply to hhabstritt from comment #7)
> Sheppy, assumed mobile would offer docs that pertain to Android, iOS,
> Phonegap, FxOS, etc. Anything mobile, not constrained to Android. Are we
> only tagging Android related docs as "mobile"?

That's a good point. We haven't to date done anything not related to Firefox on mobile, so all our Mobile docs are Firefox for Android. But that won't always be true. So you're right!

I've updated the table to cover that.

> In the doc linked above we have Tools as a doc type. We won't be releasing
> with doc types, so I'm suggesting putting it among the topic filters in the
> initial release of filters. What do you think?

Yeah, that's fine.

Comment 13

[Jannis Leidel [:jezdez]]

Merged in https://github.com/mozilla/kuma/commit/7cfb7301ed4272ce5e6802065354dd6e11c7726a \o/