Jamulus
Should we put the KB on Wordpress? #1132
Replies: 2 comments 18 replies
|
Out of curiosity, I asked SF to add a vhost called knowledge.jamulus.io which now resolves to https://sourceforge.net/projects/llcon/ but I can't work out how to make that resolve to the web space. If I can, I'll see if I can install WP as a test. |
|
Interesting suggestion. I think (and you probably also think so) that we should try to get as much as possible on GitHub. Yes, adding content is a bit more difficult since we have all the fit stuff around it. WordPress would be easier but is there maybe a better way to add community content? E.g. via Issues which get converted to .md files and uploaded to jamulus.io? That would make adding/editing content a lot easier. |
|
Oh OK, sure. The maintenance is minimal BTW. I've got about 30 WP installations on that server and they're all backed up nightly (10 day incrementals) to S3 and upgraded (base, plugins and themes) on a weekly cron job. And like I said, the KB isn't mission critical so if for whatever reason it went down for a bit or needed migrating it wouldn't be a big deal. |
|
Yes. But it's another place where people need to create accounts, would need another (jamulus like) template,... |
|
Sure (although GH doesn't do social login). But let's see what using Issues is like and we can compare it with WP. At least we know what the WP route would involve now. |
|
The GitHub issues thing would require some coding/internet research but should be possible with GH Actions. |
|
Basically this action the other way round: https://github.com/peter-evans/create-issue-from-file Step 1: Should not be too difficult to code. |
Uh oh!
There was an error while loading. Please reload this page.
The stuff about the Knowledge Base in https://github.com/jamulussoftware/jamuluswebsite/discussions/316 made me think about the fact that I was looking at SourceForge PHP/MySQL the other day for hosting discussions - but might it be better used for the KB?
The knowledge base is not a critical part of the project, so if it went down or needed to move to another platform one day it wouldn't be much of a big deal. That was my main concern with using SF to host our discussions. Also, Wordpress is widely-used, understood, exportable and flexible, and crucially - we could set the permissions to "contributor" by default AND allow social logins for GitHub, Facebook etc. thereby achieving a community wiki by other means.
All reactions