MDN/Development/CompatibilityTables/Data Requirements: Difference between revisions

Jump to navigation Jump to search
Line 48: Line 48:
The possibility to filter content based on compatibility data can be express in three ways
The possibility to filter content based on compatibility data can be express in three ways


; Filter at the page level : If the user choose a given browser and version, all page not relevant to such browser and version could be marked as "irrelevant" (by adding a flag, fading links to that pages, changing the layout or the style, etc.). This could be helpful for people looking for specific information about a given browser. It will spare the user the need to always check at the compatibility table or marker to ensure that what is reading is relevant to his needs.
; Filter at the page level : If the user choose a given browser and version, all page not relevant to such browser and version could be marked as "irrelevant" (by adding a flag, fading links to that pages, changing the layout or the style, etc.). This could be helpful for people looking for specific information about a given browser. It will spare them the need to always check at the compatibility tables or markers to ensure that what they are reading is relevant to their needs.
; Filter at the content level : The same as the above but directly into the content. This is something [https://support.mozilla.org/en-US/kb/how-to-use-for SUMO is doing]. However, the range of platform we want to cover on MDN is quite wider and such a mechanism on MDN could make things unnecessarily difficult to maintain.
; Filter at the content level : The same as the above but directly into the content. This is something [https://support.mozilla.org/en-US/kb/how-to-use-for SUMO is doing]. However, the range of platform we want to cover on MDN is quite wider and such a mechanism on MDN could make things unnecessarily difficult to maintain.
; Filter at the compatibility data level : In this scenario we want to let the user decide which compatibility data he wants to see. In this case, the content and the page remain untouched, only the displayed data are shown or hidden. The examples of filter upon compatibility tables (see above) is a good use cases.
; Filter at the compatibility data level : In this scenario we want to let the user decide which compatibility data he wants to see. In this case, the content and the page remain untouched, only the displayed data are shown or hidden. The examples of filter upon compatibility tables (see above) is a good use cases.
Confirmed users
630

edits

Navigation menu