I am doing a very long page with images and want to paginate it with “<!–nextpage–>”.
When using sections, the pagination is ignored and all content is shown.
It would be very convenient on the backend to have the sections according to the pagination.
Is there a possibility to achieve that?
I insert quite often page breaks with <!–nextpage–>. If a topic gets very long or has many images, it makes readability besser and shortens loading time.
Actually it is a very convenient feature of WP to edit on only one page and WP generates for each <!–nextpage–> the subpages automatically.
Right now with GP I can’t use both – sections and WP pagination.And i wonder why?
It would very convenient and cool, if I could do on the backend something like that
Section A
Content A
<!–nextpage–>
Section B
Content B
<!–nextpage–>
Section C
Content C
<!–nextpage–>
etc.
etc.
This way I could structure the backend with Sections according to the <!–nextpage–>.
Right now I started a page with around 15 page-breaks – so probably you can imagine, how much searching and scrolling it means, until it is last revision. I am used to that – no prob.
But it would add a lot of convenience, if Sections would allow the <!–nextpage–> functionality and not break it.
Right now, Sections development is kind of on hold until we can get a grasp on the new Gutenberg editor – if it merges into core, Sections will be completely re-written.