-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wiki #1
Comments
Do you already have a wiki-provider/-solution in mind, and should it be editable by the community or just read-only? |
|
What software do you guys have in mind, and when will be the go-live date? |
Media Wiki and when it is ready. |
Seems kinda dated, but alright. |
Mediawiki is very much alive and gets updates everyday. You may be referring to its look and feel which we will be messing with, most likely after launch, So expect the default theme to start. |
Other priorities keep trumping this one unfortunately(https://github.com/Yellow-Dog-Man/Resonite-Issues/blob/main/HOW_WE_PRIORITIZE.md) My soul burns every day this is not done. I'll keep ya'll up to date. Several things I want in writing though are:
Additionally setting some expectations for when it launches:
|
Is there anything the community can do to help pitch in on this? Eg harvesting and collating info, updating copies of Old Platform docs with new verbiage, digging up / creating useful flexible theme(s)? |
I second clarjon's post. Don't be afraid to let us help. |
There is also not a content gap, well content isn't the main focus. So I'm not entirely sure what can be done to help until this launches. After launch of course, we'll need more content though. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Thought I just had while reading #937: When the wiki (in whatever shape) is actually there, it would be great if every component / protoflux node / tool / window could have a direct link to the relevant page in one way or another. This could be a typical (i) icon, with some recognizable Resonite styling, of course - either directly on the UI for windows and components, or as a context menu option for tools. Protoflux nodes may get too cluttered with an extra element, so for those it could also be a context menu entry that opens the wiki page for the node type that would currently be spawned. Anyways, the reason I'm mentioning it is, that this would become very easy to implement, if the pages just used the (full) name of the component type for their url, so generating the correct link would be trivial to do. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
There now seems to be no thorough FrooxEngine related dcumentation on any sites (be it first or third party). What could we as a community do to make the wiki higher priority? |
I don't think there is super much that can be done from community side right now, because it's already pretty high priority on our end, but it keeps getting pushed back by other higher priority items, that we needed to be tackled in time (for example GDPR related work, resolving server/relay issues and so on). It's mostly just work-bandwidth issue on our end, with a bunch of post-launch problems and issues that need to be sorted out. I know it sucks, but it'll get sorted out in time. |
I have an update, We should be ready by the 15th, likely much before that but hey here's a date. |
Does anyone have any requested mediawiki plugins? I'm going through plugin operations today for some security things. |
The one that allows you to access PDF versions of wiki pages through a direct URL, now that we have native PDF viewing ability. |
Maybe the Math extension, for rendering LaTeX in-line? |
Maybe the Discord extension with a channel to follow wiki edits? |
Mermaid allows you to render graphs/charts/UML diagrams with minimal syntax which could be useful: |
Here's a few that are bundled with MediaWiki that I'd like to see enabled:
For @JackTheFoxOtter's suggestion, ElectronPdfService is the one used and maintained by Wikimedia, and would provide the same functionality as Wikipedia's version. MobileFrontend seems good, to make wiki pages easier to read on mobile devices |
PDF is going to have to wait, it is a complex extension. I don't know why it needs to be though :( |
Ok we got PDF's up and running, they're a bit ugly and images dont work right now but we'll work on that after launch. At some point i'll make images work, but very complicated. The original PDF extension requires a REST server AND an Electron Renderer server to be created and maintained, so Mpdf sounded better. We can revisit the pdf thing later. This has taken hours. |
Ok That's extensions done, Thanks! |
https://wiki.resonite.com now launched. |
Is your feature request related to a problem? Please describe.
A lack of reliable information at a permanent link
Describe the solution you'd like
A publicly available Wiki that documents frequently asked questions and other information.
Additional context
I'm making this to pre-bake it for when this repo goes public.
The text was updated successfully, but these errors were encountered: