Skip to content
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

Excerpts as they are seen in a post preview. #1288

Closed
paaljoachim opened this issue Jun 20, 2017 · 11 comments
Closed

Excerpts as they are seen in a post preview. #1288

paaljoachim opened this issue Jun 20, 2017 · 11 comments

Comments

@paaljoachim
Copy link
Contributor

paaljoachim commented Jun 20, 2017

A thought...

On a few of my sites I use a styled excerpt as part of the post preview on the front page.
I have added some code to add TinyMCE to the excerpts meta box so that I can make it a little nicer. Here is an example in Norwegian. The word Utdrag is the same as Excerpt.

screen shot 2017-06-20 at 00 46 42

When I go to the front page and look at the styling of the excerpt this is what I see:

screen shot 2017-06-20 at 00 48 35

Having a simple way to style the contents of the excerpt box directly would be of help or else it would just show up as a block of text.

@mtias
Copy link
Member

mtias commented Jun 22, 2017

I think we'll want an excerpt block to exist.

@paaljoachim
Copy link
Contributor Author

That is a very good idea!

@westonruter
Copy link
Member

Would excerpt block be locked to the first position in the editor once it is inserted?

@mtias
Copy link
Member

mtias commented Jun 23, 2017

@westonruter most likely, yes, and it wouldn't get the "mover" controls.

@paulwilde
Copy link
Contributor

paulwilde commented Jun 23, 2017

Should it be something you add via the popup - It would make sense to limit to only be added once, and then disable/fade it in the popup.

On that note, such a feature would be nice in general for the API so third-party plugins could introduce blocks that have a specific limit to the amount of times it can be added to the editor.

@westonruter
Copy link
Member

@mtias also I presume that the Excerpt's block contents should get stored in the excerpt field of the post (the post_excerpt DB field) as opposed to being inline in the post_content, right?

@mtias
Copy link
Member

mtias commented Jun 26, 2017

@westonruter yes, correct. I had an issue for similar handling of featured images too.

@Drivingralle
Copy link

I don't think that's a good idea to lock the excerpt or other "meta box" like fields in place on top of the editor.

As some of my projects are made so 50+ users can publish, it's already hard enough to teach the frontend and backend method to create and view content.
Thinking about telling them that they should ignore the first few "locked" blocks, because they will not appear in the frontend in that place anyway just cause them and me headaches.
Having the excerpt metabox and other below the current wp-editor allows to teach something like:
"And in this boxes all the other notes and related information need to be entered.".

Not mixing the main blocks and other blocks (excerpt-block) in one column/interface-part is very important for people which can not abstract as well as we (techy) web people/devs.

IMHO:
If Gutenbergs goal is to provide a better interface to edit visible content, maybe it should become an frontend editor. So the wp_content or sidebar can be replaced with there own Gutenberg instances. Plus an area (customizer like) that allows to edit "invisible" meta data.

@paaljoachim
Copy link
Contributor Author

I think it is totally fine where it is located right now as part of the Document settings. But then we need a way to add various styling to it. It could actually behave like a block but inside the Document setting.

@paaljoachim
Copy link
Contributor Author

paaljoachim commented Aug 18, 2017

Here is some semi styling of the excerpts box:

gutenberg-semi-styling-excerpts

One should also have the chance to use a heading in it as well.

@mtias
Copy link
Member

mtias commented Nov 20, 2017

This is a good one for looking at after the editing phase is done.

@mtias mtias closed this as completed Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants