![]() This is used to explain different areas of the program. The MuseScore handbook broadly contains two main types of information: descriptive material, and goal-oriented instructions. "Adding time signatures", rather than "Time signatures" Content Lastly, try to always start your headings with a verb. Use sparingly if additional sub-sections are required. Use for the start of every sub-section, and to introduce single-step instructions (I.e. Heading levelĭefault for all page headings (Not editable by contributors) Please also don’t skip heading levels (By, for example, adding a heading 4 after a heading 2). The first section heading you will enter will therefore always be a Heading 2. All headings need to be formatted as tags with semantic meaning.Īll pages start by default with a Heading 1. For pages that lack headings, feel free to create your own in a style similar to that used elsewhere.įor accessibility reasons, headings should never be formatted in regular bold text. Please organize your content within this structure. In an effort to ensure consistency of style for community-written pages, we have already provided headings on many pages. Please be sure to enable the "Generate a table of contents" option for all Handbook pages. Focus on user tasks, not just UI componentsįor instance, a section about "Creating custom key signatures" is better than a section called "Using the master palette". This may sometimes require less-commonly-used features to be discussed alongside more-commonly used ones, but that's okay. Related concepts should be discussed together. Put solutions for the most common tasks towards the top of the page less commonly needed information can go towards the bottom. Think about what most users will be trying to achieve, and why they might be coming to the handbook to look for information. Overviews don't usually need a section heading. Starting your page with an overview can help introduce a topic before launching into details. Not every page is identical, but keeping the following in mind can help you structure your page content in a way that's easy to understand for the reader: Start with an overview If a page feels like it is getting too long, try splitting it into separate pages. Structure - General principlesĮach page should explain a single topic more or less completely. This information is intended to help, but if you're in doubt about anything or have any questions, please join the discussion on the Documentation forum. Please read this page carefully before editing anything in our handbook. This page contains brief guidelines to get you started with writing articles. So you'd like to contribute to the MuseScore 4 handbook – great! We're so happy you're here. If you can't find the information you need in the Handbook, please ask for help in the Support Forum. ![]() Use the search function as shown on the screenshot below.Use this Google search syntax site: your topic, e.g.Open "Full Table of Contents", use "Find in page (Ctrl/Cmd⌘ + F)" function of your web browser, or.Try browsing the illustrated Glossary for notations you are incapable of naming.Alternatively, you can view the entire handbook as a single continuous page, and use your browser's Print facility to turn that page into a PDF for offline viewing. Use the links below to explore content in each chapter of the handbook. MuseScore 3 features not implemented in MuseScore 4. ![]() Upgrade from MuseScore 3.x (includes a list of keyboard shortcuts that have changed).If you are upgrading from MuseScore 3, you may find the following pages useful: Contributions and Help with translations are welcome! In case of doubt, please consult the English version of this handbook, or ask for help in the Support Forum. ![]() This handbook is maintained and translated by the MuseScore community. If you are using a different version of the program, please consult the appropriate handbook for your version: This handbook is valid for MuseScore version 4.0 and above.
0 Comments
Leave a Reply. |