How to use
Dev to Hero

A complete guide to getting the most out of Dev to Hero β€” from installation to advanced features.

1

Installation

Dev to Hero is a free Chrome extension. Here's how to install it in under a minute.

1
Go to the Chrome Web Store Click the "Add to Chrome" button on this page or search for "Dev to Hero" in the Chrome Web Store.
2
Click "Add extension" Chrome will ask for confirmation. Click "Add extension" β€” no account or login required.
3
Pin it to your toolbar Click the 🧩 puzzle icon in Chrome's toolbar, find Dev to Hero and click the πŸ“Œ pin icon to keep it visible.
4
Visit any supported documentation page Go to MDN, W3Schools, javascript.info or DevDocs β€” the badges appear automatically!
βœ“ No setup required. Dev to Hero works immediately after installation. No API key, no account, no configuration needed.

2

Understanding the badges

Each section heading on a documentation page receives a colored badge indicating its difficulty level. The badge is determined by analyzing the section's title, content, code examples, and its position in the learning chain.

🟒 Beginner
Read this now Fundamental concept with no prerequisites. If you're just starting, this is your path. These sections are safe to read at any stage.
🟑 Intermediate
Come back later Requires solid foundations in JS basics. Read the beginner sections first, then return to these once you feel comfortable.
πŸ”΄ Advanced
Not yet β€” and that's fine Complex patterns, edge cases, low-level details. There's no value in stressing over these at the start of your journey.
ℹ️ Structural sections like "Syntax", "Specifications" or "Browser compatibility" intentionally have no badge β€” they don't represent learning content and are relevant to everyone equally.

3

Reading the prerequisites

Below each badge, Dev to Hero shows a list of concepts you should already understand before diving into that section. Prerequisites are split into two categories:

πŸ“Œ Recommended prerequisites:
β˜… Functions β˜… Callbacks β—‹ Classes β—‹ Error handling (try/catch) β˜… Variables βœ“
  • β˜… Required (yellow) β€” you genuinely need these to understand the section. Don't skip them.
  • β—‹ Optional (grey) β€” useful context that enriches understanding, but not strictly necessary.
  • βœ“ Mastered (green, strikethrough) β€” concepts you've already marked as learned.

Click any prerequisite chip to toggle it as mastered. Your choices are saved automatically and will be remembered the next time you visit any page with the same prerequisite.


4

Tracking your progress

Every section heading has a ☐ Mark as read button next to its badge. Click it to mark the section as read β€” it turns into a green βœ….

Your reading progress is reflected in two places:

  • The page summary banner at the top of each page shows πŸ“– X/Y (Z%) β€” how many sections you've read out of the total.
  • The progress bar in the banner fills up as you mark sections as read. It updates instantly without reloading.
βœ“ Tip: Your progress is saved per section title across all sessions. If you leave and come back, your completed sections will still be marked.


6

Focus mode

Enable Focus mode in the popup to automatically hide all πŸ”΄ Advanced sections. The heading remains visible but faded, so you know the content exists β€” you just don't see it.

This is particularly useful when you're starting a new topic and want to read without being intimidated by content that isn't relevant yet. Focus mode is saved between sessions and applies to all supported sites.


7

Exporting your study plan

Each page has an "Export study plan" button in the summary banner. Clicking it downloads a .txt file containing:

  • All sections organized by difficulty level (🟒 β†’ 🟑 β†’ πŸ”΄)
  • Your reading status for each section (βœ… Read / ⬜ Not read)
  • All prerequisites with their mastery status (βœ“ mastered / to learn)
  • Estimated reading time for the page

The plan is generated fresh each time, so it always reflects your current progress. You can paste it into Notion, keep it as a reference, or share it with a study buddy.


8

Reporting an incorrect badge

Every badge has a small ✎ button next to it. If you think a section has been classified at the wrong level, click it to suggest a correction.

  • A small menu appears with the two other possible levels.
  • Select the level you think is more appropriate.
  • The button turns blue showing your correction is saved.
  • You can review all your corrections in the popup under "Corrections signalΓ©es".
ℹ️ Corrections are stored locally for now. They help you keep track of disagreements and will be used in future versions to improve the classifier.

9

Keyboard shortcut

You can toggle Dev to Hero on and off without opening the popup using the keyboard shortcut:

Alt + Shift + M

This is useful when you want to quickly compare a page with and without badges, or temporarily disable the extension without losing your settings.

To customize the shortcut, go to chrome://extensions/shortcuts in your browser.


10

Supported sites

Dev to Hero currently works on the following documentation sites:

MDN Web Docs
Full support β€” badges, prerequisites, banner, study plan, suggestions, and vote. Supports French and English.
W3Schools
Full support on all tutorial pages (JS, CSS, HTML, Python, PHP, SQL and more). English only.
javascript.info
Full support on course pages. Multilingual β€” detects your language automatically (FR, ZH, DE, and more).
DevDocs
Badges, prerequisites, mark as read, and vote. The page banner is not available due to DevDocs' SPA architecture. English only.

11

FAQ

Is Dev to Hero really free?
Yes, completely free, forever. No account, no API key, no subscription, no ads.

Does it work offline?
Yes. The classifier runs entirely in your browser. No network requests are made.

Will it slow down my browser?
No. The extension is lightweight and only activates on the four supported documentation sites.

Where is my progress stored?
Everything is stored locally in Chrome's extension storage on your device. Nothing is sent anywhere. If you uninstall the extension, your data is cleared.

A badge seems wrong β€” what should I do?
Use the ✎ vote button next to the badge to suggest a correction. You can also open a GitHub issue if you'd like to discuss it.

Can I use it on other sites?
Not yet, but more sites are planned. If you'd like to see a specific site supported, let us know at contact@devtohero.com.

Is it open source?
Yes β€” the source code is available on GitHub.