Rich text editor and it's use case

SHANKS

While I appreciate the technical leap in Flarum 2.0, we must remember a fundamental truth: this software is built for everyday users, not just developers.
As a final user, I don't care about how clean the backend code is if the Composer (the heart of the forum) remains a barrier. The average user shouldn't have to learn Markdown or use complex syntax just to perform basic tasks like:

Text Coloring: It’s a basic necessity for highlighting ideas, and it should be a native, clickable tool.
Rich Content Embedding: Users expect to embed media seamlessly without technical hurdles.
Typography & Lists: Bullet lists must be visually clear with a comfortable font size by default.

The focus needs to shift from 'developer-centric' to 'user-centric.' We need a true WYSIWYG experience where what a person sees is what they get. If we want Flarum to thrive, we must make it accessible to the simple user who just wants to write and share beautifully without needing a manual. A forum is only as good as its writing experience.

KBExit

SHANKS I'm sorry you feel the way. I personally feel like Flarum is really simple to use. In the text editor, you get a lot of buttons to toggle to assist with markdown, and markdown is really simple to use honestly.
Additionally, there is a WYSIWYG Extension you can download (if I recall correctly).
Composer isn't bad to use either, many PHP applications actually use it one way or another. You also have the option to use the Extension Manager if you prefer that.

SHANKS

KBExit The 'simplicity' you're referring to is actually a lack of native functionality. For a large-scale community, relying on Markdown is a step backward in UX. Not everyone wants to write code to format a post; they want a seamless, visual experience.

Regarding your suggestion of WYSIWYG or other extensions: I’ve tested them, and they are far from perfect. Many of these extensions struggle with core features like text coloring (BBCode/Color) or maintaining consistent styling for bulleted lists across different devices. They often break the output or conflict with other plugins, which proves that Flarum’s core editor still lacks the robustness found in other professional forum engines.

My goal isn't just to 'get by' with extensions that barely work; it’s to provide a stable, intuitive, and accessible interface for my users without them needing a manual to change a font color or size

KBExit

SHANKS I don't want to sound harsh. But you also have native hotkeys that work in the text editor to make things bold, etc. To call markdown "code" is also a bit of a stretch. Markdown has been widely adopted for many note taking apps and document building software in the modern office environment. It's been standard for a while now. To struggle with it is merely a skill issue that can be resolved with a little reading. Phpbb and smf use bbcodes, which is also still an option with Flarum. If even that cannot satisfy you, I don't know what will.

IanM

KBExit fixed. Missed permission from when re we-organised the other day 🙈

SHANKS

KBExit Dismissing UX flaws as a 'skill issue' is the hallmark of a developer who builds for himself, not for the end user. I manage professional communities on Invision Community (IPS), so I’m well-versed in what a 'standard' should look like. A true standard is intuitive, not something that requires a manual for a basic task like font coloring or bullet alignment.

You mention Markdown is standard for 'modern office environments,' yet you forget that even the most advanced tools (like Slack, Notion, or Jira) provide a Rich Text GUI because they value the user's time. If Flarum’s core philosophy is that my users should act like they’re writing README files on GitHub just to share a post, then it’s failing its primary purpose as a social platform.

I’m here to build a community, not a coding bootcamp. If I have to fix broken extensions and override CSS just to get a usable editor, the issue isn't my 'skill'—it's the platform’s lack of maturity in handling professional-grade UI/UX requirements

Capybara

SHANKS Flarum is an extensible platform. Alongside a simple and lightweight core, you have dozens of extensions at your disposal. For the editor, I can recommend my MagicBB, which adds a convenient color picker

SHANKS

![
I’ve actually tested the MagicBB extension, and it only confirmed my concerns: these extensions often lack stability and fail at the most basic tasks. Specifically, the color codes in the extension simply do not work, which is a perfect example of the frustration I'm talking about. In a professional platform like Invision Community, I don’t need 'magic' for basic tasks; I expect a reliable, built-in system that works seamlessly from day one.
It is puzzling why Flarum still lacks a native, high-quality, and intuitive WYSIWYG editor. The screenshots from my community showcase a robust editor where features like text coloring, font resizing, and bulleted lists are not optional extras, but fundamental parts of the core. Having a 'Source' mode for advanced customization should be a standard, not a luxury.

KBExit

SHANKS sounds to me you're wanting Invision Power Board. You're honestly just campaigning for them at this point. Stick to what works for you. Your complaints aren't an issue with functionality but rather an unfamiliarity with modern message boards like Flarum / Discourse.
You like IPB? Stick to it.

Also, this topic is about the updates on this board. I am flagging your discussion for a split.

ernestdefoe

SHANKS you are talking about Invision and the difference is it’s a commercial platform that costs a bunch of money so yeah you’re going to get more features and such. Flarum is built different in the fact it’s not bloated like Invision is. Plus to have WYSIWYG editors like Invision and xenForo have integrated into it cost money to have the correct license which is why those two platforms cost money. To have something that robust you’d either have to develop it yourself or would have to charge for a premium extension to account for the license you’d need to use the editor.

IanM

I should add here that it is intended to port the old WYSIWGY rich text editor over to @FriendsOfFlarum and build on top of that for Flarum 2.x

Like everything else, it's simply a matter of time and resources to do this sustainably in the Flarum open source ecosystem.

It will happen, and hopefully before the stable release of Flarum 2.0, but it is currently not guaranteed.

Capybara

SHANKS the color codes in the extension simply do not work

That is not true. The plugin supports any color value and has preset options. The plugin is fully stable, features a responsive design for mobile, and is suitable for both intuitive use and for users who need creative freedom. Your argument that you work on a major product is irrelevant here. I work at a large corporation, and many services using Markdown, like Jira, also don't place every button on the formatting toolbar. This is standard practice

SHANKS

KBExit Labeling a technical critique as 'campaigning' is just a poor excuse to avoid admitting Flarum's core is incomplete. If a broken editor and constant reliance on unstable extensions are what you call 'modern,' then your standards are simply lower than mine. I don't need to 'learn' a tool that fails at basic tasks; I choose tools that actually work.

KBExit

SHANKS none of what you claim is true. You either installed Flarum incorrectly or you're coming in here with extreme bias.
Either or, none of your claims are true for a properly installed Flarum instance with best practice extension installation.

SHANKS

ernestdefoe Claiming that a professional WYSIWYG editor requires a 'premium license' is a pure technical fallacy. Look at MyBB, SMF, and PBBoard; these are all free, open-source platforms that have provided robust, native editors for years without charging users a dime.
If these community-driven projects managed to integrate functional editors as a core component without 'licensing' excuses, why can't Flarum? It’s not about the money; it's about a flawed philosophy that prioritizes 'minimalism' over actual usability.
Stop labeling basic, essential features as 'bloat.' A car without steering isn't 'lightweight'—it’s just broken. If other open-source scripts can offer a complete experience for free, then Flarum’s lack of a native editor is a choice, not a financial limitationClaiming that a professional WYSIWYG editor requires a 'premium license' is a pure technical fallacy. Look at MyBB, SMF, and PBBoard; these are all free, open-source platforms that have provided robust, native editors for years without charging users a dime.
If these community-driven projects managed to integrate functional editors as a core component without 'licensing' excuses, why can't Flarum? It’s not about the money; it's about a flawed philosophy that prioritizes 'minimalism' over actual usability.
Stop labeling basic, essential features as 'bloat.' A car without steering isn't 'lightweight'—it’s just broken. If other open-source scripts can offer a complete experience for free, then Flarum’s lack of a native editor is a choice, not a financial limitation

ernestdefoe

SHANKS the thing is there is a feature rich editor in Flarum it just requires you to learn how to use Markdown. Yes it can be a bit of a pain but technical people already know it. As @KBExit had stated if something isn’t working for you then you didn’t do something right. I’ve been using the extension from @Capybara almost since it was released and it works amazingly well especially since there are issues with the WYSIWYG editor as it hadn’t been updated in some time. Also most forum platforms I’ve mentioned and you have mentioned have also been around a heck of a lot longer than Flarum has. They tend to have a bigger ecosystem as well due to that fact. Flarum will get there in time.

SHANKS

KBExit Claiming I 'installed it wrong' is the classic developer's excuse for a broken product. If I need a PhD in 'Installation Best Practices' just to see a functional color picker or a basic editor, then the problem isn't my installation—it's your software's identity crisis.

A professional script should work out of the box, not require a 'magic' ritual of extensions just to perform tasks that MyBB and SMF perfected fifteen years ago. Stop blaming the user for your platform’s inability to provide the basics .

You’re missing the point entirely. Third-party extensions are meant to be aesthetic or optional enhancements, not a substitute for missing core organs.

A community platform without a functional, native editor is like a car company selling a vehicle without a steering wheel or a gear stick, then telling the customer to go buy them from a third-party 'magic' shop.

If I need to 'correctly install' a dozen plugins just to reach the basic functionality that MyBB, SMF, and PBBoard have had in their core for decades, then Flarum isn't 'modern'—it's just an empty shell. A professional engine is judged by what it can do out of the box, not by how many 'crutches' it needs to stand up .

The discussion ended with him being attributed to me.

ernestdefoe

SHANKS Claiming that a professional WYSIWYG editor requires a 'premium license' is a pure technical fallacy. Look at MyBB, SMF, and PBBoard; these are all free.

The free software aren’t using a professional editor. They are probably using an older version of TinyMCE while the paid software are using a true professional editor which they have to pay a license to use in their software. So as such it’s not technical fallacy. You want pro features you pay a pro price. While TinyMCE has been used for a long time it’s far from considered pro.

ernestdefoe

SHANKS A professional script

Flarum isn’t professional hence why it’s free. No free forum software is professional. You want/need professional then you need to stick with the paid software.

ernestdefoe

SHANKS You’re missing the point entirely. Third-party extensions are meant to be aesthetic or optional enhancements, not a substitute for missing core organs.

Both xenForo and Invision have both removed features in the core of the software, jacked the price up and opened the door for third party developers to add the functionality back in for a substantial cost.