pinax-blog icon indicating copy to clipboard operation
pinax-blog copied to clipboard

Support front-end creation and editing of posts

Open jtauber opened this issue 9 years ago • 6 comments

as is done for pinax-pages, would be nice to support in pinax-blog

jtauber avatar Jul 03 '15 09:07 jtauber

I would like to see this as a very rich experience leveraging pinax-images and pinax-images-panel. I'm thinking a ReactJS frontend coupled with a pinax-blog-authoring package (or similar) with the following features:

  • auto-saves as you type content
  • ace.js editor
  • markdown preview
  • auto-populate description from teaser
  • replace the post images in pinax-blog with pinax-images (#73)
  • list view with much of the admin functionality of search / filter / sort

paltman avatar Nov 01 '15 16:11 paltman

Check out the work @davelowe did in #8

paltman avatar Jan 23 '16 08:01 paltman

Instead of ace.js, I wonder about https://quilljs.com/

paltman avatar Sep 06 '16 19:09 paltman

also: https://facebook.github.io/draft-js/

paltman avatar Sep 06 '16 21:09 paltman

I'm now thinking we add the views to support templates/static initially built out in the pinax blog starter project that will run:

https://github.com/yabwe/medium-editor

with

https://github.com/orthes/medium-editor-insert-plugin

To provide a medium-like editing experience, complete with auto-saving: https://github.com/yabwe/medium-editor/issues/856

In order to auto-save, we'll need to create a post as soon as we have content to send. This raises the question of how to handle all the various fields.

Perhaps we only have a Title and Content fields. The subtitle, which medium seems to make out of an h4 if it's the first bit of content in the content area, could be extracted as the teaser.

paltman avatar Sep 07 '17 01:09 paltman

But this also raises the question of do we care about the Revision model anymore? Do we want to require markup or can we post directly to *_html fields?

paltman avatar Sep 07 '17 02:09 paltman