Re: [Content] - Compatibility Tables everywhere?

I just implemented this at the hackathon.

It is now possible to add "Imported compatibility tables" to pages. You
just specify the page you want to lift the compatibility table from, and a
reference to it is automatically included in the page. You can choose to
import multiple compatibility tables.

*This is now the preferred way of handling compatibility on
tutorial/guide/concept/etc articles*. The canonical compatibility
information should exist on the specific reference articles, and then be
included via this mechanism into related tutorial pages.

The usability around this in the form is TERRIBLE right now; it's very
unclear what the difference is between imported and non-imported compat
tables, and when you should use either.  If anyone has any ideas on how the
editing experience should be I can implement it in the form definition[1].

--Alex

[1] http://docs.webplatform.org/wiki/Template:Compatibility_Form_Section

On Fri, Oct 19, 2012 at 4:00 PM, Janet Swisher <jswisher@mozilla.com> wrote:

>  This would be really helpful for translation, so that the table is
> maintained only once.
>
>
> On 10/19/12 4:52 PM, Alex Komoroske wrote:
>
> In an ideal world I think we'd have some way of grabbing a compatibility
> table from one article and transcluding it in another. That would allow us
> to have the canonical data on the specific reference page for each feature
> and then just dynamically include it on other articles where it's relevant
> (like on articles). This should theoretically be possible with semantic
> media wiki queries and properties.
>
> On Fri, Oct 19, 2012 at 2:40 PM, <jonathan@garbee.me> wrote:
>
>>  Do we want the compatibility tables [1] to be anywhere or do we want
>> them to be centralized in an area (such as the elements page)?
>>
>> I think we should centralize them in order to create less maintenance
>> later on.  If we have tables in any page for elements listed then it isn't
>> going to be easy later on to update them if needed and could cause
>> confusion on where to get the information.  I am thinking we should
>> centralize them under the element itself [2] to solve these possible
>> issues.
>>
>> [1] example table:
>> http://docs.webplatform.org/wiki/guides/html_text#Compatibility
>>
>> [2] example element: http://docs.webplatform.org/wiki/html/elements/em
>>
>>
>>
>> Thoughts?
>>
>> -Garbee
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
> --
>  Janet Swisher <jREMOVEswisher@mozilla.com>
> Mozilla Developer Network <https://developer.mozilla.org>
> Technical Writer/Community Steward
>