New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Validate Markdown content #164

Open

jraddaoui opened this issue Jun 3, 2019 · 0 comments

Collaborator

jraddaoui commented Jun 3, 2019

From @cole in #162:

In lieu of caching for now, what about adding a rendered_content (or similar) field with editable=False? Rendering markdown on each page view isn't crazy expensive, but best avoided if possible, and also if someone introduces invalid markdown, they should find out about it on save ideally.

Related to #96.

This was referenced Jun 3, 2019

Allow content edit and translation #162

Merged

Problem: cannot update the FAQ page #96

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment