Create/Draft blog post improvements

[digitaldirk]

1. Implement a way to preview current draft blog post from create page. Ideally a button that toggles the preview.
   Currently you have to create the post as a draft then go to drafts and view it there.

2. Fix "ghost" placeholder text (maybe an issue on other pages as well?). Currently seeing this on the Post Title, Tags, and Featured Images inputs. Do we just simply remove the placeholder on the input or does this need css style tweaks?
   

3. Dark mode has short description and content in light mode:
   

4. I think the Published toggle should be set to Draft by default. I personally never write a "final draft" in one go and want it as a draft to revisit later. I use the create/update post button mainly to save my progress.

Willing to do a PR but I won't be able to get to this soon.

[linkdotnet]

Hey hey @digitaldirk thanks for the awesome feedack!

Here my two cents to some of them:

1. Currently, it is a bit cumbersome! So you can toggle the editor with the "eye" button to see the preview! But you have to do this for description/content individually.
2. Interesting. Not sure why that happens as these should be normal controls. But yeah, let's get rid of them.
3. I am using (an outdated) Blazorise.Markdown package. Newer versions need a licence, which I don't wanna force anybody onto! Therefore sticking with the current version. I am not sure how much we can hook into that or create a new one (i did have a custom markdown editor at first, but that was lacking features!)
4. I think that can be an appsettings.json toggle. I myself do publish by default.

We can either create subtasks for each of them. I think (3) is a bigger task and needs some investigation before starting!

[digitaldirk]

1. That works good enough for me, was not aware.
2. I will do a PR.
3. Understandable, I'll see if there are any solutions in html/css to force dark mode for the current solution. There are some other blazor markdown editors I have seen (but haven't used in any/much capacity). This one probably needs to be a new issue.
4. This is just a minor inconvenience for me, and I don't think it's worth a setting for it, let's leave it as is.

Thanks!