Learning Paths are community created how-to articles about software development for the Arm architecture.
All content is covered by the Creative Commons Attribution-ShareAlike 4.0 International License .
A Learning Path is a concise tutorial with detailed steps to learn how to complete a specific task.
A Learning Path is not:
Learning Paths provide a way for software developers to learn about Arm technology.
Arm has a number of content channels where you can access Arm technical content and related information.
Product Documentation and reference manuals are the trusted source of detailed information for developing on the Arm architecture.
Blogs offer news and announcements for recent and upcoming Arm activities.
Videos provide talks and demos of Arm tools and other software topics.
The next section explains how you can setup a computer to create a new Learning Path or modify existing content.
Anyone who wants to share Arm-related software developer material on how to achieve a specific outcome can create a Learning Path. Contributors are Arm employees, Arm Ambassadors from the Arm Developer Program , and community members who enjoy sharing what they have learned.
This Learning Path provides the information you need to create your own Learning Path. If you have questions or need help, please raise an issue on GitHub .
Learning Paths are about software development on Arm. Content is segmented into 5 categories and each Learning Path is related to the category. Each category covers different kinds of computer hardware, and each Learning Path is about software development on Arm hardware. All types of software are welcome.
Learning Paths include only public information. Do not include confidential information, trade secrets, unannounced products, or any other information which should not be on a public website.
You can use GitHub Discussions to ask questions about your Learning Path idea. You may want to do this if you are unsure about the usefulness of your concept or think it might already be covered by other content. You can also use it to determine the best category for your Learning Path. It is possible to have a Learning Path appear in multiple categories, so use GitHub discussions to ask.
Install guides provide a concise summary of how to install tools and software or do a common task. Install guides make it easy to reference repeated actions from multiple Learning Paths. Use GitHub discussions to ask if your content idea should be a Learning Path or an install guide.
Use the GitHub Ideas to share topics you think would make a good Learning Path or install guide. Even if you cannot write the content it’s possible somebody else can do it.
Project maintainers review and merge pull requests on a regular basis. When contributors raise a pull request a number of checks are run for spelling, broken links, malware, and profanity. Once any issues are corrected, the Learning Path is published.
The contribution process comprises 3 stages, all of which are covered in this Learning Path:
You can now walk through the details of each of these three stages in this Learning Path.