-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add some type of marker before the child list on each landing page #20
Comments
Hi @cirosantilli, thanks for the feedback. Unfortunately I don't understand the problem. As I write this, the example you linked does not include any Table of Contents. Please note that the asciidoctor-multipage extension does not have or maintain a stylesheet (only a few rules which can be disabled)—the stylesheet is maintained in the Asciidoctor project. And regardless, you're free to use a custom stylesheet instead of the default. |
Hi, precisely, there is no Table contents. What I propose is that something like a |
@cirosantilli, the Table of Contents already has a title. Here is the HTML portion: <div id="toctitle">Table of Contents</div> And here is a screenshot of the sample document in the repository: If there is still a problem or I am misunderstanding, please provide an example, test case, or screenshot clearly demonstrating it and re-open this issue. |
Just in case: input.adoc
Desired multipage output: h1.html
Current multipage output: there is no
This can be seen e.g. at: https://cirosantilli.com/china-dictatorship/anti-ccp-info-sources.html "Backlinks to this page" is the last list item, and "Reddit" is the first child. |
@cirosantilli, so this isn't related to the Table of Contents, as mentioned in the title and description? The "Table of Contents" is the listing of all parts/chapters/etc. in the document, including (when asciidoctor-multipage is in use) those that are not included on the current page. In the screenshot from earlier, the Table of Contents is on the left side with a grey background. From a writing style perspective, I recommend avoiding using multiple lists in succession. Instead use a regular paragraph to tell the reader what the new list contains. However, if you want more spacing between successive lists, just add this CSS rule, adjusting the margin value to suit you: ul,ol,dl{margin-bottom:2em} (As mentioned before, the asciidoctor-multipage extension does not have or maintain a stylesheet.) |
Sorry if terminology was confusing. What I meant is that multipage essentially adds a one level ToC to every page automatically.
Note that the input does not contain consecutive lists. Only the multipage does. |
Oh, okay. I understand now. You are suggesting that we add an h2 on each landing page before its list of child pages. Thanks for the examples and clarification. In my opinion, the best solution here is to understand that your document output (with asciidoctor-multipage) will be generated using landing and leaf pages. Landing pages are not intended to contain document content; the purpose of those pages is to list child pages. As described in more detail over there, this extension is not designed for use as a website generator. Still, I will leave this issue open in case there is need for further discussion. |
+1 |
found another possibility using css:
the list of child headers is always displayed at last on a page (except in the first page as "first-child") |
Can't do a sed hack, there absolutely no difference in the child list from a regular list: https://github.com/cirosantilli/china-dictatorship/blob/e7e9032f11734012f837c9003c39d085fa8afd31/push#L25
At
gem 'asciidoctor-multipage', '0.0.12'
It feels to me a bit too hard to separate the header body from he list of children that goes at the bottom.This is especially true if the header ends in a large Asciidoctor list for example:
it would be hard for readers to see that the list in
h1
ends atlist
and thath2
andh3
that follow are the children as it renders something like:I would recommend adding a marker for that, e.g. saying Table of Contents or Children in bold. e.g. like:
Sample live rendered example: https://cirosantilli.com/china-dictatorship/anti-ccp-info-sources.html that illustrates the difficulty.
Here's an example of the output style I went for on my own markup language: http://cirosantilli.com/evil#toc
The text was updated successfully, but these errors were encountered: