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

Introduce a Next Page Block to allow post pagination #4930

Closed
felixarntz opened this issue Feb 7, 2018 · 7 comments
Closed

Introduce a Next Page Block to allow post pagination #4930

felixarntz opened this issue Feb 7, 2018 · 7 comments
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability [Feature] Blocks Overall functionality of blocks New Block Suggestion for a new block

Comments

@felixarntz
Copy link
Member

Issue Overview

In the classic editor, you can insert a <!--nextpage--> comment to break a post into multiple pages. This should be supported in Gutenberg as well and be possible in an intuitive way.

Expected Behavior

It should be intuitive to add pagination functionality to a post.

Current Behavior

You can currently insert the comment manually in the HTML view, and it technically works because of existing core logic. However it's not possible to create that in a user-friendly way, and is not visually reflected in the editor when the comment exists.

Possible Solution

There should be a "Next Page" block that takes over that functionality. Existing <!--nextpage--> comments could be autoconverted to that.

Related Issues and/or PRs

#983 (similar approach for the more tag)

@felixarntz felixarntz added [Feature] Blocks Overall functionality of blocks Backwards Compatibility Issues or PRs that impact backwards compatability labels Feb 7, 2018
@gziolo
Copy link
Member

gziolo commented Feb 7, 2018

See #1467 - @swissspidy made some progress on this one. It would be nice to continue this work.

@mtias
Copy link
Member

mtias commented Feb 7, 2018

This seems to have been closed before #1328 (should not be).

@mtias
Copy link
Member

mtias commented Feb 7, 2018

Also, we'd want to do it like this in advance: #2973

@mtias mtias added the New Block Suggestion for a new block label Feb 7, 2018
@swissspidy
Copy link
Member

Ah right, @gziolo asked me about that. I knew there was an email I forgot about! :-)

I'm happy to continue working and to collaborate on #1467 if there's interest. Closing issues and then reopening them months later is confusing…

@gziolo
Copy link
Member

gziolo commented Feb 7, 2018

I'm removing Stale label in that case from #1467 :)

@mtias
Copy link
Member

mtias commented Feb 7, 2018

@swissspidy I think this one was just closed by mistake as "new block" tickets were moved into a project, but the blocks that match existing functionality should be kept open. Sorry about it :)

@danielbachhuber danielbachhuber added this to the Merge Proposal milestone Apr 11, 2018
@karmatosed karmatosed modified the milestones: Merge Proposal, Merge Proposal: Back Compat Apr 12, 2018
@mcsf
Copy link
Contributor

mcsf commented Apr 27, 2018

Closed via #1467

@mcsf mcsf closed this as completed Apr 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability [Feature] Blocks Overall functionality of blocks New Block Suggestion for a new block
Projects
None yet
Development

No branches or pull requests

7 participants