{"id":20551697,"url":"https://github.com/do-community/developer-glossary","last_synced_at":"2025-08-14T08:08:05.168Z","repository":{"id":46580948,"uuid":"300767508","full_name":"do-community/developer-glossary","owner":"do-community","description":"A community-built glossary of technical terms.","archived":false,"fork":false,"pushed_at":"2021-10-04T21:04:19.000Z","size":251,"stargazers_count":25,"open_issues_count":4,"forks_count":37,"subscribers_count":11,"default_branch":"main","last_synced_at":"2025-03-06T05:47:36.726Z","etag":null,"topics":["hacktoberfest"],"latest_commit_sha":null,"homepage":"","language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/do-community.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"code_of_conduct.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2020-10-03T00:50:12.000Z","updated_at":"2025-02-03T15:21:25.000Z","dependencies_parsed_at":"2022-07-20T06:32:21.286Z","dependency_job_id":null,"html_url":"https://github.com/do-community/developer-glossary","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/do-community/developer-glossary","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/do-community%2Fdeveloper-glossary","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/do-community%2Fdeveloper-glossary/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/do-community%2Fdeveloper-glossary/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/do-community%2Fdeveloper-glossary/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/do-community","download_url":"https://codeload.github.com/do-community/developer-glossary/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/do-community%2Fdeveloper-glossary/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":270385467,"owners_count":24574556,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-14T02:00:10.309Z","response_time":75,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["hacktoberfest"],"created_at":"2024-11-16T02:33:07.952Z","updated_at":"2025-08-14T08:08:05.142Z","avatar_url":"https://github.com/do-community.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cbr\u003e\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"https://i.ibb.co/nnKZtGP/dev-glossary.png\"\u003e\n\u003c/p\u003e\n\u003cbr\u003e\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"https://i.ibb.co/str4chy/open-book-wave-logo.png\"\u003e\n\u003c/p\u003e\n\u003cbr\u003e\n\nA community-built glossary of technical terms. \u003cbr\u003e\nSee it live at [www.glossary.dev](https://www.glossary.dev). \u003cbr\u003e\nKindly refer to our Code Of Conduct [here](https://github.com/do-community/developer-glossary/blob/main/code_of_conduct.md) before contributing.\n\n\u003cbr\u003e\n\u003cbr\u003e\n\n## General Contributions\nIf you see that the glossary is missing a term, we would love your help in adding it!\n\n\u003cbr\u003e\n\n### How to Contribute Terms\n\nNew terms should be added to the `content/terms` directory as new markdown files, where\nthe name of the markdown file is the term, **lowercased and hyphenated.** So a definition for \"Command-Line Interface\" would go in a file named `command-line-interface.md`. Examples should include the terms in a sentence, and be relevant and appropriate.\n\n\u003cbr\u003e\n\nFollow this template for the structure of your new definition:\n\nTEMPLATE:\n```markdown\n---\ntitle: \"\u003cYour Term Here\u003e\"\ndate: 2020-10-02\npart-of-speech: \u003cnoun|verb|adjective\u003e\nsynonyms: [\"\u003cOptional Synonyms\u003e\"]\nabbreviation: \u003cOptional Abbreviations or Acronyms\u003e\n---\n\nWrite out a definition of the term in markdown here.\n\n## Example\n\n\u003e Use your definition in a sentence.\n\n## Further Reading\n- [Link Title](https://www.link.com)\n```\n\n\u003cbr\u003e\n\n\nFor example, for the term `Command-Line Interface` the file path would be `content/terms/command-line-interface.md` and the contents might be:\n\n```markdown\n---\ntitle: \"Command-Line Interface\"\ndate: 2020-10-02\npart-of-speech: noun\nsynonyms: [\"Command Line\"]\nabbreviation: CLI\n---\n\nRefers to the text-input interface commonly used by developers to interact with computers and the services or processes running on them. A command-line interface accepts text input (commands) which execute processes and typically result in text output.\n\n## Example\n\n\u003e System administrators use the command-line interface to SSH into virtual machines running in datacenters.\n\n## Further Reading\n- [Command-Line Interface on Wikipedia](https://en.wikipedia.org/wiki/Command-line_interface)\n```\n\n\u003cbr\u003e\n\n### How to Submit a PR from Github Desktop\n\nGo to [content/terms](https://github.com/do-community/developer-glossary/tree/main/content/terms) and click the \"Add File\" button in the GitHub interface.\n\nName the file `\u003cyour-new-term\u003e.md` for example if you were adding a definition for `Command-Line Interface` you would name the file `command-line-interface.md`.\n\n\nBelow the file, fill out the \"Propose new file\" inputs with information about the term you are adding.\n\nYour title might be \"Add definition for Command-Line Interface\" and your extended description might be: \"I didn't see this term defined so I added it, I linked to the wikipedia page because it is a pretty good overview of the concept.\"\n\nJust share a bit about your reasoning for adding the content. Then click \"Propose new file\" to create a Pull Request.\n\nSomeone will follow up with questions on your PR if there is anything wrong or unclear, and then they'll approve it and merge it and it will go live on the site!\n\n\u003cbr\u003e\n\u003cbr\u003e\n\u003cbr\u003e\n\n## Contributing Code Improvements\n\nWe'd also love code contributions that beautify the site, make it more accessible and usable, and help it follow good web standards.\n\n\u003cbr\u003e\n\n### Local Development and Installation\n\nThe site is statically generated using the [hugo](https://gohugo.io/) framework. To run it locally follow these steps:\n\n1. Fork the repo and clone it down to your local machine\n2. [Install hugo](https://gohugo.io/getting-started/installing#readout) if you don't already have it installed.\n3. Open a terminal in the root directory of the developer-glossary project and run `hugo server -D`\n4. Check that no errors appear in the terminal, it should tell you it is running on localhost:1313. That means you can view the site running locally by going to [http://localhost:1313](http://localhost:1313) in your browser.\n\nYou're off to the races! Reference [hugo docs](https://gohugo.io/about/) to learn more and start making code contributions.\n\n\u003cbr\u003e\n\u003cbr\u003e\n\u003cbr\u003e\n\n## Syncing a Forked Repo\nSync a fork of a repository to keep it up-to-date with the upstream repository.\n```bash\ngit remote add upstream https://github.com/do-community/developer-glossary.git\ngit fetch upstream\ngit checkout main\ngit merge upstream/main\n```\n\n\u003cbr\u003e\n\u003cbr\u003e\n\u003cbr\u003e\n\n## Language Use Guidelines\n\nAll contributions made towards adding a new term and its definition must adhere to these common guidelines:\n\n1. Every contribution made should adhere to the [Code of Conduct](https://github.com/do-community/developer-glossary/blob/main/code_of_conduct.md)\n2. Avoid usage of country specific language when adding a new term, in the term definition and for the examples provided.\n3. [Use simple language](https://plainlanguage.gov/resources/articles/dash-writing-tips/). Avoid idioms and be clear.\n4. Be accurate when providing definitions and examples for a term.\n5. We also adhere to the official [Github Community Guidelines](https://docs.github.com/en/free-pro-team@latest/github/site-policy/github-community-guidelines) which provides additional information on how to collaborate and contribute to projects hosted on Github.\n\n\u003cbr\u003e\n\u003cbr\u003e\n\u003cbr\u003e\n\n## Project Updates \n\nYou can follow updates on the development of our glossary, here.\n\n- 10-30-20:\n    - Added 3+ more terms to the glossary, and an action that performs a test to ensure the site build passes with each PR.\n    - PRs are open for more terms! Let's build a glossary that helps our community to thrive.\n\n- 10-28-20:\n    - [Issue](https://github.com/do-community/developer-glossary/issues/72) being worked on by two contributors- still open to more help! \n    - Merged 3+ new terms and glossary improvements. Remember to name your file using the **lowercase and hyphenated** convention. \n    - Updated README to add more whitespace/styling elements. \n\n- 10-26-20: \n    - New [Issue](https://github.com/do-community/developer-glossary/issues/72) added for UI help- update our glossary's UI!\n    - Merged 15+ new terms into the glossary, and fixed issue in file that prevented Hugo site from running.\n    - Reviewed new and submitted terms for style/content, and submitted edits for various terms. Please follow the guidelines and be sure your terms/examples/links are helpful and appropriate.\n    \n- 10-19-20: \n    - Merged 10+ new terms into the glossary\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdo-community%2Fdeveloper-glossary","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdo-community%2Fdeveloper-glossary","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdo-community%2Fdeveloper-glossary/lists"}