MDN Changelog for June 2018

| July 6, 2018 | WEB DESIGN AGENCY MIAMI | No Comments

Editor’ s note: A changelog is “ the log or record of all significant changes made to a project. [It] usually includes records associated with changes such as bug fixes, brand new features, etc . ” Publishing the changelog is kind of a custom in open source, and a long-time practice on the web. We thought visitors of Hacks and folks who make use of and contribute to MDN Web Documents would be interested in studying more about the work of the MDN anatomist team, and the impact they have within a given month. We’ ll furthermore introduce code contribution opportunities, fascinating projects, and new ways to take part.

Done in 06

Here’ s so what happened in June to the code, data, and equipment that support MDN Web Documents :

Here’ ersus the plan for July:

Shipped 100+ HTML Interactive Illustrations

In June, we all shipped over 100 HTML online examples, adding quick references plus playgrounds for our HTML element documents.

On the left, the particular HTML is displayed, and a tabs would show the CSS. At the right, the rendered HTML of the hamster image with a caption beneath.

HTML Interactive Example regarding < figcaption>

Schalk Neethling fixed the remaining blockers, like applying an result class as a design target ( PAGE RANK 961 ), and incorporating some additional size options ( PR 962 ). wbamberg wrote instructions pertaining to adding the examples to MDN, and SphinxKnight and Irene Smith pitched in to deploy them in under 24 hours. MDN visitors have fun, educational examples on JS, CSS, and today HTML reference pages.

Irene Smith joined the MDN writer’ s team in 06 as a Firefox Developer Content Supervisor. She started work right away, which includes helping with this project. Welcome to the particular team, Irene!

Delivered Django 1 . 11

We deployed Django 1 . eleven on June 6th. There are simply no visible changes, but also no mistakes for MDN visitors. Sometimes the engineering project is successful if you bad back to where you started.

Falcon Heavy rockets moments from landing

Like the Falcon rockets, we journeyed far to return to the same location.

We do most of the planning work in growth environments. On June 1st, we all shipped Django 1 . 11 to the staging environment ( PR 4830 ). This particular exposed a few issues that were fast to fix, such as the logging configuration ( PR 4831 ) and client-side translation catalogues ( PR 4831 ). Tests in the production-like staging environment ensured the last insects were fixed before MDN’ h visitors saw them.

We’ re looking ahead to the next construction update. Django 1 . 11 may be the last to support Python 2 . seven, so we’ ll need to in order to Python several. 6 . We’ ve additional a Python 3 build to TravisCI , and will ratchet up compatibility with time ( PR 4848 ). Anthony Maton began the Python 3 changes in the Mozilla All-Hands, updating tests to anticipate random dictionary order, a security feature enabled within Python 3. 3 ( PR 4851 ). We expect a lot more changes, and we plan to switch to Python 3 with Django 1 . eleven by the end of the year.

The next Django Long-Term Support (LTS) release will be 2 . 2, scheduled for Apr 2019 . The work will be like the last upgrade, updating the program code to be compatible with Django 1 . eleven through 2 . 2 . Ryan Johnson started the process by converting towards the new-style middleware , required in 2 . zero ( PR 4841 ). We plan an easy switch to Django 2 . 2 simply by June 2019.

Delivered Tweaks and Fixes

There were 252 PRs merged within June:

32 of those were from first-time contributors:

Other significant PRs:

Planned for July

July is the start of the second 1 / 2 of the year, and the team is considering what can be done by the end of the year. We’ re planning on finishing the suitability data migration this year, and growing interactive examples to another documentation area.

Decommission Zones

Zones are a wiki motor feature that moves a shrub of pages to a different URL, plus applies additional CSS for those web pages. Zones also add complexity to every ask for, require additional testing, and are the frequent source of bugs and interpretation problems. Zones have more enemies compared to fans on the MDN staff.

We’ ve been deprecating zones for a few years. We stopped making use of new zones as a design device. In final year’ s site redesign , we de-emphasized the style distinctions between zones and “ standard” wiki content ( PR 4348 ). Whenever migrating MDN to a new information center, we added a redirects framework that can elegantly handle the particular custom URLs. We’ re looking forward to the final steps.

In the Mozilla All-Hands, Ryan Johnson plus wbamberg prepared to remove zones. The task took the entire week. On the motor side, custom URLs need diverts to the standard wiki URLs, and a few zone styles need to be preserved ( PR 4853 ). Zone sidebars need to be reimplemented as KumaScript sidebars, along with snel ( PR 711 ). Finally, content must be changed, to add the KumaScript sidebars and to use standard wiki CSS. While the changes are large, the result is subtle.

On the particular Progressive Web Apps MDN web page, the zone style has an symbol next to the tile, that it will forfeit without zone styles.

The particular subtle differences between zone designs and without zone styles

After the work week, we all reviewed and refined the program code, double-checked the changes, and cleared up the plan. We’ ll ship the particular code, update the content, and remove zones in July.

Focus on Performance

We’ re wrapping up the performance review of MDN in July. We’ ve picked some key efficiency metrics we’ d like to monitor, and the headline metric is just how long it takes for the interactive example to become ready on CSS, JS, plus HTML reference pages. Schalk Neethling is implementing the timing dimensions ( IE PAGE RANK 967 , Kuma PR 4854 , and others), using the PerformanceTiming API so the dimensions will be available in browser tools. All of us also track timing in Google Analytics, to get real-user metrics from MDN’ s global audience, unless the consumer has requested that we don’ t monitor them .

We’ ve found several performance bottlenecks, and we’ re prioritizing these to pick the quick wins and the high impact-resistant changes. We’ ll ship enhancements in July and beyond.

John is a web developer focusing on the engine of MDN Internet Docs

More articles by David Whitlock…

If you liked MDN Changelog for June 2018 by John Whitlock Then you'll love Web Design Agency Miami

Related Posts

About The Author

John Whitlock

Add a Comment

Your email address will not be published. Required fields are marked *

Shares