#21611 closed New feature (needsinfo)
RichTextField
Reported by: | Julien Bouquillon | Owned by: | nobody |
---|---|---|---|
Component: | Forms | Version: | 1.6 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
hi
Having support for a rich text field in the admin looks like a more and more common use case to me : editing pages, fragments, model descriptions...
There are many existing HTMLField implementations but generally painful to integrate, especially for django newcomers. (and too much choices)
Would be awesome to have a builtin RichTextField with at least a minimal wysiwyg editor, which could handle HTML, or markdown. We could make the editor swipable with another implementation (tinymce, redactor.js...) if needed. (Next to this there is image upload from the editor, but we'll talk about it a bit later).
Do you think this makes sense to integrate this in Django core ?
I think this would be a really nice addition to the already awesome admin interface, and makes things easier for beginners.
If so let's discuss about implementation, which editor to use... and i'd be pleased to help.
Thanks !
Change History (3)
comment:1 by , 11 years ago
Resolution: | → needsinfo |
---|---|
Status: | new → closed |
comment:3 by , 6 years ago
Just for the people that might stumble across this issue: there's a 3rd party editor agnostic `RichtTextField` for Django available that does pretty much what's described in this ticket. (full disclosure, I'm the author of said package)
Assessing and selecting an external app takes some work, but competition results in better apps overall that what could be maintained in Django itself. It's pretty much the same story as urllib2 vs. requests :)
As far as I know, third-party apps such as django-markitup do the job well with the hooks currently provided by Django. If Django could provide better hooks to make such integrations smoother, we'd certainly consider suggestions favorably.
That said, the proper place to discuss a large addition is the django-developers mailing list, in order to reach a wide audience. You'll have to present a concrete proposal and compelling arguments, because the current trend is to trim down Django by deprecating contrib apps that aren't "best of breed" any more. The team's resources are already spread thin for maintaining core and contrib. "It would be nice" won't fly!
In terms of process, I'm going to close the ticket as "needsinfo", where the info needed is a concrete implementation plan and a consensus on the mailing list that it's a good idea, or at least a few +1 from core devs. If you reach that point, then you can reopen this ticket and use it to track the implementation work. Thanks for your understanding!