So, when we edit or comment on posts we have this lovely editing interface:
But when we are editing pages, we have this interface:
How difficult would it be to use the same editor for both posts and pages?
I ask this for a reason: the post editor allows pasting in images, whereas the pages editor does not. Therefore, with pages the author has to upload the images to their account and then link them (or put them on an external location). I can see this as being problematic if the owner of a community steps down and passes it on to someone else -- it would be possible to accidentally mess up links...
Or worse, what happens if the previous owner deletes their account? Do all the images associated with that account go away?
P.S. I think the name Wiki is a misnomer. The feature allows for simple page editing, and none of the linking features that are the defining feature of a wiki. ;)
You're viewing a single thread.
8 comments
Yes this is completely doable. Please add it to the PieFed codeberg as an issue so we don't forget.
I guess the images would need to be saved into a community account rather than the author's account.
It's a wiki in the sense that authorship is shared but you're right making broken links go to a 'create a page here' form would be much better.
It would be really cool if there were some way to do automatic page / index generation (ie, select all pages with a specific tag, or possibly a sectioned type system). IE, have the wiki generate it's own Table of Contents as an entry page...
But, that's not stuff that needs to be considered now.
Yeah the wiki feature is very much at the MVP stage, with an emphasis on minimum. It'd be good to flesh it out.
I'd agree about the MVP status, but I also don't think you have to go too crazy with it.
Think about 3-5 features that would be most useful and work on them over a few versions. I'd bet some people will think of / suggest things you and I aren't thinking about. :)
On the other hand, there's a ton of wiki software available around the world, whereas on the Threadiverse there is only Lemmy, PieFed, and Mbin. So it makes a lot of sense to me to keep focused on the unique aspects that only @Rimu@piefed.social can offer? Not that I have any call on his time, just sharing this thought in support of the contrasting viewpoint.
Yes, there is a lot of wiki software - but most of that software isn't geared towards the Fediverse, and it would require that someone set it up, host it, administer it, etc. The whole management cycle for using another platform adds a complication to the Threadiverse concept of building Fediverse native communities.
But, with PieFed, Lemmy, Mbin and nodebb we are focused on building those communities. It makes sense to have something like a Wiki more tightly integrated into the community platform. That makes it easier to maintain from administrative standpoint, and from a management cycle perspective.
IMO - I'm not thinking that we should build MediaWiki into PieFed, but I think it could be a better complement to the community portion of the system.
Tbf, MediaWiki is fairly nice to use 😊
Not saying it isn't...but we don't need to have MediaWiki in PieFed. 😀