GetPublii / Publii

The most intuitive Static Site CMS designed for SEO-optimized and privacy-focused websites.
https://getpublii.com
GNU General Public License v3.0
6.06k stars 407 forks source link

[Feature Request]: Change post type after it's created #1327

Open sxiii opened 5 months ago

sxiii commented 5 months ago

Feature Description

Greetings.

It's been gazillion of times when I need to change editor from Markdown to Block or WYSIWYG or wise-versa. Every time I have to create a new post and hence ruin the ID scheme of the posts. Would be awesome to be able to:

  1. Change the post editor type after post had been written. Even if this would lead to loss of formatting, I'm okay with that (I can quickly re-make the formatting), but I don't want to make a new post every time and destroy the old post. This looks inefficient. Ideally, each post should allow for quick and easy switch of the editor while you're in the post already.

  2. Allow editing IDs of the posts in Publii GUI itself. So we don't have to fiddle with the database. At least this way we could make a new post and change the ID to older so we can preserve the IDs being low numbers instead of them shooting far ahead.

atomGit commented 4 months ago

the funny thing is, tinymce supports some markdown by default AFAIK, however that functionality is AWOL in publii for whatever reason

having 3 post editors seems unnecessary to me and, as you point out, problematic

the block editor, which i suspect is also tiny powered, is just plain silly IMO - WordPress started this nonsense and forced it on all their users which resulted in a massive amount of criticism and a fork (ClassicPress)

markdown is great as long as it's rendered in real-time, as publii sort of does, however this should be incorporated into the wysiwyg editor IMO, as WordPress does, thus providing one editor that handles both html and md and eliminates the problem you describe

just my 0.02

candidexmedia commented 1 month ago

having 3 post editors seems unnecessary to me and, as you point out, problematic

the block editor, which i suspect is also tiny powered, is just plain silly IMO - WordPress started this nonsense and forced it on all their users which resulted in a massive amount of criticism and a fork

I don't necessarily disagree, but the WYSIWYG Editor has issues with erasing custom HTML that the Block editor handles with no issue (see: https://github.com/GetPublii/Publii/issues/1527). It's also great at formatting code snippets.

Block editors are used in Medium, Ghost, Notion, etc., so I believe that it may have been added to accommodate users who are used to that.

I will say: one integrated editor (or, at least, a more efficient way of switching between editors) would be ideal...