Update broken link in create.md to collections

[elvey]

No description provided.

[netlify]

✅ Deploy Preview for open-terms-archive-docs ready!

Name	Link
🔨 Latest commit	a4d6904
🔍 Latest deploy log	https://app.netlify.com/projects/open-terms-archive-docs/deploys/6a68f435b9f0600008b4a2bd
😎 Deploy Preview	https://deploy-preview-221--open-terms-archive-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[elvey]

Just a simple fix to a broken URL.

PS: Coming to OpenTermsArchive (OTA) fresh, it's easy to get lost/not know where to start. Hashing out a rough idea: main...elvey:docs:patch-2
Maybe with a link to https://docs.opentermsarchive.org/terms/how-to/track-terms-using-ui/ ? Or not - I see per https://github.com/OpenTermsArchive/contribution-tool that it's not ready for public use...
And the URL therein - https://contribute.opentermsarchive.org/?destination=OpenTermsArchive/sandbox-declarations doesn't work.

Surmising from https://opentermsarchive.org/en/collections/contrib/ that contrib is the main collection, and that tosdr relies on and tosback (toward the end, it seems dead) relied on OTA. Yes?

P.P.S.: There's a warning at https://dir.floss.fund/view/projects/@opentermsarchive.org - If it is not fixed, the listing will be removed from the portal!

[MattiSG]

Good catch, thank you! 😃

[MattiSG]

@allcontributors add @elvey for doc

[allcontributors]

@MattiSG

I've put up a pull request to add @elvey! 🎉

[MattiSG]

contrib is the main collection, and that tosdr relies on and tosback (toward the end, it seems dead) relied on OTA.

Yes, that is correct 🙂 👍

There's a warning at dir.floss.fund/view/projects/@opentermsarchive.org

Thanks for the heads up! The warning dates back to 21 Jan 2026 and seems to simply not have been updated (it mentions a timeout on GitHub's side, which happens quite often these days). floss.fund has not really shown any value so far, so I don't see us investing more time to investigate that bit.

---

Thank you @elvey for these contributions! Would be happy to hear more about your use case and discovery path for Open Terms Archive 🙂 either here or over email contact@opentermsarchive.org

Please note that most of the team is on summer break and we're slower than usual to reply (as not exemplified by this PR 😄).

[elvey]

Email sent to contact@. Thanks so much for the way you handled this. Too kind.

FYI: I started down the road of creating folders so I could then run npm install, npm test, ... open pull requests.
But then I saw that video on the contribution tool.. then I found it's not available.

Also, would help to give a bit of a history/status of preceding/related efforts - and maybe even a roadmap?
It's confusing that there's tosback - in fact >= 3 versions...

This comment and initial #221 (comment) above relate to #67