-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
How to split post like WordPress <!--nextpage--> #3035
Comments
Hi @kohki-shikata. That is an interesting question. What about this? <a id="page-marker-01" style="page-break-after: always;"></a> This attribute The attribute Will that work for your purposes? |
@tcrowe |
Lets try another approach. Asset folders! https://hexo.io/docs/asset-folders.html
That will create a directory More pages can be added in it:
Link to the pages: [Pg 1](./index.html) [Pg 2](./part02.html) [Pg3](./part03.html) That may accomplish similar to what you want. I will check for a multi-page plugin now. |
I searched for "hexo plugin multiple page post" but I did not find anything yet. Are you good at JS? Can you make a plugin for this? It would be a good plugin to use with asset folders. |
I will close this Issue because implementing this feature in Hexo is complex. If the input is a single Markdown file while generating multiple HTML outputs, it would require significant modifications to existing mechanisms (such as permalink and post asset), resulting in substantial maintenance costs. I suggest implementing this through a frontend JS script within the theme. By using JS to analyze GET parameters and manipulate HTML, it can selectively display specific content on the page. |
In WordPress, we can split post with the tag "<!--nextpage-->" in the post text, then output one post to consisted multiple pages like below...
http://example.com/permalink/?page=2
http://example.com/permalink/?page=3
http://example.com/permalink/?page=4
…
So, does anyone know how to same function in Hexo?
originalpost: https://groups.google.com/forum/#!topic/hexo/SH-QaSEEg4g
The text was updated successfully, but these errors were encountered: