Proper use of "how to" articles
I'm about to prepare some "how to" material. However I see that these articles are not linked to on the main handbook gateway page, nor do I see a clear way that users learn about them. I'm probably missing something obvious. Can someone kindly answer these questions?
-
Are how-tos still viewed as an important resource? How do users find them?
-
Assuming they are still relevant, would it be appropriate to add a link from the handbook page to the how-tos?
-
Is it appropriate to link from a particular handbook page to a relevant how-to, explaining details about the use of a feature?
I'd rather not do something stupid that needs to be undone. Thanks.
Comments
3*yes
In reply to People find them when they… by Louis Cloete
Oh jeez, they're right there in the support menu. I don't know how I missed that. OK never mind, this is a clear enough path even though idiots like me might miss it.
There are a few handbook pages with links to the how to's. There are even a few handbook pages that link to the forums because someone thought it should be done.
Thanks everyone for your input. I wanted to be sure I was current with How-To use. I was surprised to see only two articles under 3.x and feared these were no longer relevant.
In reply to Thanks everyone for your… by spinality
Much of the 3.x effort to date has been to make it usable rather than things like How to's. Hopefully this will start to change in the next couple of months when we know version 3.1 is stable and we can take advantage of How to's to explain new features.
In reply to Thanks everyone for your… by spinality
There are more under 'Any', which means they apply to more than one version.
We need an additive mechanism here, like we have for plugins
In reply to Thwere are more under 'Any',… by Jojo-Schmitz
Agreed!
In reply to Thwere are more under 'Any',… by Jojo-Schmitz
Hmm. I do see the potential for some new user confusion here. With many platforms (e.g. Windows), support articles are identified by their relevance to a particular release. When I see an article for an earlier OS release, I presume it has not been updated, and is likely out-of-date. So I generally only look for current-release material.
From what you say, when a MuseScore user selects "any how-to" this means "show me how-tos that apply to any=all releases" -- as opposed to "show me how-tos that are specific to any release."
My instinct would be for us to try to update the earlier how-tos, and then flag them as part of the 3.x universe. But perhaps my own confusion on this is not typical.
In reply to Hmm. I do see the potential… by spinality
I'd want 3.x Howtos to show then 3.x is selected, which it is by default, but I also want to be able to flag a howto to be valid for 3.x and 2.x, so it shows in both categories
Or 3.x to mean 3.x + any (unspecified, those flagged as none)