Add Nsumit28: document tooling study (use case) and built-with-superdocs badge + gallery (extension)

[Nsumit28]

Sumit Negi

Two builds, both from the SuperDocs Round 2 task.

use-cases/Nsumit28/document-tooling-study — a measurement of what people are actually stuck on when software has to touch a Word document, and a technical note written from what it found. I queried Stack Overflow, GitHub and Hacker News through their public APIs for fifteen document problems, took their own engagement counters, and measured the fifteen most relevant pages.

The result that surprised me: the eight Stack Overflow questions in the set are all answered — they're about converting formats and extracting tables, and they've been read 652,284 times between them. The four GitHub items are all open, all from 2026, and all about editing inside a document: tracked changes, comments, tables surviving a format change, AI editing inside Word.

• Study: https://nsumit28.github.io/docx-notes/what-people-are-stuck-on/
• The note it produced: https://nsumit28.github.io/docx-notes/tracked-changes-lost-in-conversion/

extensions/Nsumit28/built-with-superdocs — a "built with SuperDocs" attribution badge for project READMEs, the gallery it links to, and the written rules for who gets listed. The badge is a single self-contained SVG with the text converted to outlines, because GitHub's image proxy blocks web fonts. The gallery is generated from a reviewed manifest and makes no external requests.

• Gallery: https://nsumit28.github.io/built-with-superdocs/
• Repo: https://github.com/Nsumit28/built-with-superdocs

SuperDocs was used on both: chat editing and export on the article, and on the curation rules document. Where I kept what it wrote and where I didn't is written down in each folder's README.