# A Call for Documentation Help **URL:** \ **Category:** AllStarLink\ **Created:** [November 3, 2024, 6:14pm UTC](https://community.allstarlink.org/t/a-call-for-documentation-help/22183 "2024-11-03T18:14:55Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [November 3, 2024, 6:14pm UTC](https://community.allstarlink.org/t/a-call-for-documentation-help/22183/1 "2024-11-03T18:14:55Z")
ASL Community, # We need your help! As the leadership [announced](https://community.allstarlink.org/t/become-part-of-the-team-allstarlink-is-looking-for-beta-testers-for-asl-3/22049) a few weeks ago, we are looking for beta testers and maybe even some development help. That's one key way to contribute, although response has been disappointingly light. However if beta testing isn't your thing, there's another great way you can contribute - by writing documentation! The long-term goal is to consolidate all AllStarLink documentation into the [ASL Manual](https://allstarlink.github.io). This includes updating and replacing the content on [wiki.allstarlink.org](https://wiki.allstarlink.org) as well was going through some of the excellent help that's been provided here. The ability to edit and contribute to the documentation does not require any significant technological skill and can be done on any common OS - Windows, MacOS, or Linux. All that's needed is to: 1. Install VSCode (or another editor of your choice), Git, Python3, and MKDocs 2. Create a GitHub account (if you don't have one) 3. Learn some VERY basic use of Git and GitHub 4. Contribute! If you can write a post in the Community, you can contribute documentation to AllStarLink. In fact, the ASL Community forum and the ASL Manual both use a very simple text styling format named [Markdown](https://www.markdownguide.org/getting-started/). This format is far simpler than HTML or even the Mediawiki page language. Spending 30 minutes doing the tutorial will prepare just about anyone to contribute. There is a [long todo list](https://github.com/AllStarLink/ASL3-Manual/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) of good first issues for people wanting to contribute. The ASL Developers will help out with any questions on getting started, using git, etc. We're working to improve the documentation on how to improve the documentation too!! See the [ASL3 Manual README.md](https://github.com/AllStarLink/ASL3-Manual/blob/main/README.md) for more info ## Contributing some documentation is not a lot of invested time, but it's an invaluable contribution to the AllStarLink community. If you are interested, please contact myself or [WA3WCO](https://community.allstarlink.org/u/wa3wco/summary). Thanks, Jason N8EI ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [November 4, 2024, 1:00am UTC](https://community.allstarlink.org/t/a-call-for-documentation-help/22183/2 "2024-11-04T01:00:40Z")
Pinned on November 4, 2024, 1:00am UTC ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [November 4, 2024, 1:00am UTC](https://community.allstarlink.org/t/a-call-for-documentation-help/22183/3 "2024-11-04T01:00:53Z")
Made this a banner on November 4, 2024, 1:00am UTC. It will appear at the top of every page until it is dismissed by the user. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [January 17, 2025, 7:24pm UTC](https://community.allstarlink.org/t/a-call-for-documentation-help/22183/4 "2025-01-17T19:24:37Z")
Removed this banner on January 17, 2025, 7:24pm UTC. It will no longer appear at the top of every page.