#23743: Add markup support to flatpages
-----------------------------------+--------------------------------------
Reporter: berkerpeksag | Owner: nobody
Type: New feature | Status: new
Component: contrib.flatpages | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
It might be interesting to see if this could be implemented as a third-
party app which could be something like a model mixin so it could be
applied to arbitrary models. The
[https://github.com/django/djangoproject.com/blob/78dfa4836daadddadf68c39006a738e37432ad77/blog/models.py#L27-L56
djangoproject.com blog] implements a selector as you describe for raw
HTML/reST support. I would prefer to see this approach if possible, but if
there is consensus on the DevelopersMailingList to add it to Django, then
okay. The third-party app approach might then require making the
`FlatPage` model swappable which is also something that we'd need to
discuss.
--
Ticket URL: <https://code.djangoproject.com/ticket/23743#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.925d91c574239e66978e97fc3d99f058%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.