# Discourse Basic Editor

**URL:** https://meta.discourse.org/t/discourse-basic-editor/159431
**Category:** Plugin
**Tags:** broken
**Created:** [July 31, 2020, 4:00pm UTC](https://meta.discourse.org/t/discourse-basic-editor/159431 "2020-07-31T16:00:55Z")
**Posts on this page:** 1
**Showing post:** 81

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [October 17, 2022, 4:17am UTC](https://meta.discourse.org/t/discourse-basic-editor/159431/81 "2022-10-17T04:17:04Z")

</div>

> [@spirobel](#):
>
> As said before, modifying the discourse frontend when it comes to something major like this is not a good idea.

My goal is to have all the building blocks in place to allow for editor experimentation in Discourse.

I have discussed this with @david, @tgxworld and @martin in the past, we have a lot of stuff in progress at the moment and can not get started quite yet. That said … our rough plans are:

1. enough extensibility to allow easy replacement of the editor with a contenteditable composer
2. experiments around trivial components that add minimal extra interesting functionality
  - A component that “inlines” images and leaves everything else alone in markdown (super useful for mobile composer)
  - A component that syntax highlights markdown

3. perform experiments around full feature editors such as CKEditor 5 (on my list to contact Wiktor once we are ready)

The approach of starting from scratch with a brand new frontend is not advisable and will be something that will be a nightmare to support long term. It may be a short term hack that buys you a few months, but long term it is wasted effort.

---

_[View the full topic](https://meta.discourse.org/t/discourse-basic-editor/159431)._