Redesign pages using the W3C Jekyll theme

[vivienlacourba]

Addresses #27

New URIS:

• /translations/ replacing https://www.w3.org/Translations/
• /translations/contribute/ replacing https://www.w3.org/Consortium/Translation/
• /translations/authorized/ replacing https://www.w3.org/Translations/authorized.html
• /translations/matrix/ replacing https://www.w3.org/Consortium/Translation/matrix.html
• /translations/feed/ replacing https://www.w3.org/Translations/feed.xml (note that this new URI will require a specific redirect to work)

[vivienlacourba]

@deniak this is ready for review but there are a few things for which I'll need your help:

• Pages have a description property which AFAIK is not currently used by the W3C Jekyll theme.
• Same for the feed page property.

[vivienlacourba]

@deniak, also for the matrix page (/translations/matrix/) I'd like this table to be wider and ideally responsive.
See current page as comparaison: https://www.w3.org/Consortium/Translation/matrix

• Table headings are supposed to be sticky when scrolling but this stopped working as soon as I enabled the "table-wrap" div container for making this table responsive.
• Still on the matrix table you will also notice a display issue as almost half of the headings text is hidden behind the <thead> <tr> line.

Feel free to test and push directly to this branch.

[deniak]

@deniak this is ready for review but there are a few things for which I'll need your help:

• Pages have a description property which AFAIK is not currently used by the W3C Jekyll theme.
• Same for the feed page property.

I opened a PR add use these properties if they are provided in the page.

[deniak]

@deniak, also for the matrix page (/translations/matrix/) I'd like this table to be wider and ideally responsive. See current page as comparaison: https://www.w3.org/Consortium/Translation/matrix

• Table headings are supposed to be sticky when scrolling but this stopped working as soon as I enabled the "table-wrap" div container for making this table responsive.
• Still on the matrix table you will also notice a display issue as almost half of the headings text is hidden behind the <thead> <tr> line.

Feel free to test and push directly to this branch.

I've tweaked the CSS for that matrix page to try to fix the sticky headers and increase the width of the table.
I learned that overflow (added by the class .table-wrap) doesn't work well with sticky elements so the only way I found to fix the issue is to specify a max-height to the container. This is enforcing the size of the table and causing the scrollbars to appear but at the same time, it may also help with the exploration of the table since we cannot display it completely.

[vivienlacourba]

@deniak, also for the matrix page (/translations/matrix/) I'd like this table to be wider and ideally responsive. See current page as comparaison: https://www.w3.org/Consortium/Translation/matrix

• Table headings are supposed to be sticky when scrolling but this stopped working as soon as I enabled the "table-wrap" div container for making this table responsive.
• Still on the matrix table you will also notice a display issue as almost half of the headings text is hidden behind the <thead> <tr> line.

Feel free to test and push directly to this branch.

I've tweaked the CSS for that matrix page to try to fix the sticky headers and increase the width of the table. I learned that overflow (added by the class .table-wrap) doesn't work well with sticky elements so the only way I found to fix the issue is to specify a max-height to the container. This is enforcing the size of the table and causing the scrollbars to appear but at the same time, it may also help with the exploration of the table since we cannot display it completely.

Thanks I made a few additional CSS tweaks (in particular increasing the table height) I think it is good enough.

[dontcallmedom]

thanks, this looks very good to me overall; my main question is about information architecture: as we're shuffling where these resources are located (both from an URL and breadcrumb perspective), I wonder if it should better reflect that most pages are only about translations of standards (and so maybe should leave under /standards), with the exception of "contributing" whose scope is a bit more ambiguous (and may need to be disambiguated or may need to live somewhere else, e.g. under /get-involved).

It may be useful in particular to hear from @remibetin and @xueyuanjia given their direct involvement in a lot of the translation-related work.

[vivienlacourba]

thanks, this looks very good to me overall; my main question is about information architecture: as we're shuffling where these resources are located (both from an URL and breadcrumb perspective), I wonder if it should better reflect that most pages are only about translations of standards (and so maybe should leave under /standards), with the exception of "contributing" whose scope is a bit more ambiguous (and may need to be disambiguated or may need to live somewhere else, e.g. under /get-involved).

It may be useful in particular to hear from @remibetin and @xueyuanjia given their direct involvement in a lot of the translation-related work.

Here are some other comments I had while working on those those pages:

• The list of translation and the contribute page both mention "Technical Reports" while we moved away from this term since the Website redesign. For example the /TR page uses "W3C standards and draft". Should this be clarified on the new pages?
• Authorized Translation policy:
  • It mostly refers about W3C Recommendations, it should now list Statements as well.
  • Some legacy terms are still present "W3C Host", "W3C Activities", or "QA activity."
• The page listing authorized translations is not linked from the main list of translations. It only appears to be linked from:
  • https://www.w3.org/blog/2019/restarting-w3c-translations-program/
  • https://www.w3.org/WAI/translations/#other-wai-translations-listings
• I also plan to move the "Policy for Authorized W3C Translation" from the CVS date-space https://www.w3.org/2005/02/TranslationPolicy.html to the CMS https://www.w3.org/policies/autorized-translations/

[vivienlacourba]

FYI this MR has been deployed on: https://vivienlacourba.github.io/translations/

[remibetin]

Thanks @dontcallmedom @vivienlacourba I know we will want to update those pages and the related structure in the coming future. However, I do not know in which direction yet.

I do not wish to be a blocker. Please let me know if you prefer to move those pages shortly while knowing we could substantially change the structure and content soon; or if it is makes more sense to wait.

[Update] To clarify, my personal preference would be to wait.

[vivienlacourba]

Thanks @dontcallmedom @vivienlacourba I know we will want to update those pages and the related structure in the coming future. However, I do not know in which direction yet.

I do not wish to be a blocker. Please let me know if you prefer to move those pages shortly while knowing we could substantially change the structure and content soon; or if it is makes more sense to wait.

[Update] To clarify, my personal preference would be to wait.

I'll be off for 2 weeks let's resume the discussion then.

[xueyuanjia]

Here are some other comments I had while working on those those pages:

• Authorized Translation policy:

  • It mostly refers about W3C Recommendations, it should now list Statements as well.
  • Some legacy terms are still present "W3C Host", "W3C Activities", or "QA activity."

The Authorized Translation policy is planned to be updated (ETA is Q2 2025, according to @remibetin and @shawna-slh).

• The page listing authorized translations is not linked from the main list of translations. It only appears to be linked from:

  • https://www.w3.org/blog/2019/restarting-w3c-translations-program/
  • https://www.w3.org/WAI/translations/#other-wai-translations-listings

+1 to link authorized translations from the main list of translations

• I also plan to move the "Policy for Authorized W3C Translation" from the CVS date-space https://www.w3.org/2005/02/TranslationPolicy.html to the CMS https://www.w3.org/policies/autorized-translations/

The pro I see is that there could be translated versions of the policy available on the Chinese and Japanese websites respectively.

Additional question: Are we considering publicly archiving the existing (will-be-old) Authorized Translation policy page for historical reference purposes? If the updated policy is substantially different, I feel it might be useful to make it possible to check the old policy, as a number of translations were developed under it.