Challenges and approaches taken with the Opera Extension Docs
summary
Opera switches extensions to the Chromium/Blink platform and the docs team rebuilds tutorials rather than rewrite API reference, focusing on concise, copy-paste-safe examples and workflows. Tools include markdown and Jekyll-like jaal site generation and GitHub for issues and contributions. Main wins are unified architecture pages, step-by-step sample extensions and multiple feedback channels; pain points are SEO, translations and surprisingly low contribution volume — only one external GitHub pull request so far despite a popular extensions ecosystem. Also cites a large personal install figure 3.5 million downloads as context.
AI-written summary · about
chapters (30)
- 0:00Intro
- 0:38Give it a choice
- 1:00Simple choice
- 1:14Difficulty
- 1:50Switch to Chromium
- 2:21New Extensions Platform
- 3:01The Choice
- 3:47Opera vs Chrome
- 4:18Architecture
- 4:37Main aim
- 5:47Google Docs
- 6:30Unified Architecture
- 8:24Sample Extensions
- 8:40Use Cases
- 9:46Jekyll
- 11:08Creative Commons
- 11:33Sample Code
- 13:36Feedback
- 14:10Internal Feedback
- 15:17Multiple Feedback Channels
- 16:40Writing Documentation
- 17:14Improving Documentation
- 19:19Key Points
- 21:06How are you soliciting feedback
- 22:13How do you manage different translations
- 23:41Should you use boilerplate
- 25:30Experience with Jekyll
- 26:35Opera in Russia
- 27:40Russian translations
- 30:47Translation and English only
related talks
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs
45mDocs That Scale: Strategies for Sustainable Documentation in Open Source Projects
40mDocs Tools for OSS Maintainers
47mThe Art of Documentation and Readme.md
49mSupporting extensions, but really now
56mEffective Documentation: The Key to Open Source Growth
58mTrying to build an Open Source browser in 2020
46mContribute to Docs Like A Microsoft Insider