-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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.
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
Empty post placeholder #1082
Comments
@youknowriad yes, let's get an empty text block there. The placeholder should be the default for the block (i.e. if the default was an image, it'd be the image placeholder, etc.) We'll see if #798 pans out. |
Here's how I've been imagining it: Not sure about the "(optional)" part — perhaps that's premature. The idea is that we are also looking to retire post formats, and you might have a post format that doesn't include a title. But this is probably better solved by making the post title an actual block that you can remove, down the road. Below that, like Matías says, is a text block. Or the default block you decided in #798. By the way I appreciate your mockups, @paaljoachim, it's good to have a diversity of ideas here! |
@paulwilde For constructiveness' sake, can you elaborate on your reaction to @paaljoachim's comment? |
@aduth I'm just not a huge fan of the placement of the title in the toolbar. It has the disadvantage of not being able to support multi-line so you need to horizontality scroll should the title be longer than the input field width. Also there would need to be a lot of considerations on its placement on mobile also, which currently isn't a concern (I believe?). Separating it outside of the content canvas might also be a little confusing to some users, as it could suggest that its more of an internal title rather than content which (for the most part, depending on the theme) is output on the page. |
@paulwilde That is a very valid point! One that I did not think about. |
I'm starting to think about the technical details of the first version of this. We have several options: Append an empty block in the block list when initializing the editor Pros:
During the render, fallback to a empty text block if the block list is empty Pros:
Cons:
Thoughts on this @aduth |
This is ok and speaks to the ability of saving "ready made templates" as page content (think the About page that already comes with WordPress, or the hello-world post). This should also be a configurable setting in PHP for plugins, etc. |
I've been having some thoughts here also, which tie into the default block also. The idea is, essentially, to show a "fake" block at the bottom, with a writing prompt inside (like "Write your story"). It's just a big button, but if you click it, it becomes your default text block. Then on the right side there's a small dropdown that lets you select what this default text block is. Defaults to single p text, but you could potentially pick freeform, or even let a markdown block register itself here. The inserter plus would sit below this. I'm still thinking about this and want to provide a mock-up, but this is the general idea. |
Now that we have a direct "New post" link, should we add a global placeholder "Start writing"(or similar)?
I wonder if we should automatically add an empty text block (with this placeholder) to all new posts.
The text was updated successfully, but these errors were encountered: