Maybe ask the authors of projects and pages to give references or expansions of things that you find unclear? I don't see that anybody has the time to decode everything that appears on HaD to maintain a glossary. Also some terms are obvious to some but not others. E.g. when I see IP I think Internet Protocol but some might not.
Footnotes? An after the fact addition to a page, similar to Wikipedia's layout, to help a reader find the correct resource for further learning. A confused reader could request 'citation, please' on a piece of text. The author, at his leisure, could write something helpful.
Applying the CMS (Chicago Manual of Style) isn't something I would want to attempt while I'm writing about taking control of someone's IP[1] by overwriting the IP[2] due to a misformed IP[3] datagram.
What if the glossary is a personal page? Each user could create their own list of things they may abbreviate while writing. An example is that I may write E in a project log, it was common vernacular way back when. (Electromotive force, BTW. I use V these days, however.)
The personal glossary could be a link on a project page to look up of a user's term or possibly composited in to the page when served. There could also be a 'please add to your glossary' request.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
Maybe ask the authors of projects and pages to give references or expansions of things that you find unclear? I don't see that anybody has the time to decode everything that appears on HaD to maintain a glossary. Also some terms are obvious to some but not others. E.g. when I see IP I think Internet Protocol but some might not.
Are you sure? yes | no
Footnotes? An after the fact addition to a page, similar to Wikipedia's layout, to help a reader find the correct resource for further learning. A confused reader could request 'citation, please' on a piece of text. The author, at his leisure, could write something helpful.
Applying the CMS (Chicago Manual of Style) isn't something I would want to attempt while I'm writing about taking control of someone's IP[1] by overwriting the IP[2] due to a misformed IP[3] datagram.
[1] intellectual property
[2] instruction pointer
[3] internet protocol
Are you sure? yes | no
I left out model numbers.
Are you sure? yes | no
What if the glossary is a personal page? Each user could create their own list of things they may abbreviate while writing. An example is that I may write E in a project log, it was common vernacular way back when. (Electromotive force, BTW. I use V these days, however.)
The personal glossary could be a link on a project page to look up of a user's term or possibly composited in to the page when served. There could also be a 'please add to your glossary' request.
Are you sure? yes | no
Quickly putting functions to the designations I encounter in these pages: part numbers, standards, apps, and sites.
Are you sure? yes | no
I don't know of an official one, what specifically are you searching for in a glossary?
Are you sure? yes | no