Closed Bug 877221 Opened 12 years ago Closed 5 years ago

MDN-flavored theme for Markdown docs in Jekyll / Github Pages

Categories

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

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: lorchard, Unassigned)

References

Details

(Whiteboard: [specification][type:feature])

What problems would this solve? =============================== Docs written in Markdown and published with Jekyll / Github Pages could use an MDN-flavored theme to achieve better visual coherence with the code MDN site Who would use this? =================== Authors managing docs outside the MDN wiki. Users reading Mozilla-related docs. What would users see? ===================== Docs would be styled in a way that is visually consistent with code MDN What would users do? What would happen as a result? =================================================== Authors would grab a copy of the MDN-flavored Jekyll theme and use it in their projects. Readers would visit these docs and see the MDN visual identity Is there anything else we should know? ======================================
Blocks: 877189
Component: General → Editing
I am working on a Jekyll-powered site for the local Mozilla community. It won't be too difficult for me to create something similar with the MDN layout in mind.
Has there been any progress on it? It'd be really lovely to have a MDN theme for Github Pages docs. It's worth noting since this ticket was filed that Google is now using Github Pages docs for their Developer docs, and its quite nice: https://developers.google.com/web/updates/2016/02/css-variables-why-should-you-care
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.