Currently problems and solutions are scattered among three or more locations: manual upgrade README, halospv3/spv3-known-issues/issues, halospv3/spv3-known-issues/wiki, and the #self-help channel in the Discord.
Write up all the issue and solutions as individual pages, tag them with keywords/phrases for SEO, and share them. Where applicable, their preview embeds will show the issue's key phrase as the Page's name along with a short summary of the issue.
However, they should not be written as blog posts. That would make the blog feed messy.
Instead, a Troubleshooting button should be added to the site's navbar which then presents a wiki-like interface for browsing and searching issues.
[ ] Add Troubleshooting page; Add one page per issue (solution(s) are added to the respective pages as sections/headers). Troubleshooting page should be accessible from the navbar. It should have a page index.
[ ] may require an additional Jekyll plugin for search functionality. Allow searching by page title, key phrase, keyword(s). Needs search syntax!
Currently problems and solutions are scattered among three or more locations: manual upgrade README, halospv3/spv3-known-issues/issues, halospv3/spv3-known-issues/wiki, and the #self-help channel in the Discord.