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

Page title based on heading title #45

Open
jamesread opened this issue Apr 3, 2024 · 4 comments
Open

Page title based on heading title #45

jamesread opened this issue Apr 3, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@jamesread
Copy link

jamesread commented Apr 3, 2024

Hey, I've been using asciidoctor-multipage for several years now, for several projects, the biggest of which is http://docs.olivetin.app ( https://github.com/OliveTin/docs.olivetin.app ), and as a developer myself I know that I appreciate when people say thank you, so, thank you! ;-) asciidoctor-multipage has made my life writing longer documentation much easier than having to use something like asciibinder.

I'm not sure if this is a support request (because I've not found the configuration option yet), or a feature-request (if this isn't yet possible), but I'd like the page title to be reflected in the html - currently every page uses the document title, ie;

= OliveTin
:title: OliveTin documentation
:multipage-level: 2

[#installation]
== Installation guide
blah

Which renders: <title>OliveTin documentation</title> on installation.html. I would much rather something like; <title>Installation &bull; OliveTin Documentation</title> but just <title>Installation</title> would be good enough.

The reason being is that it helps people with lots of docs tabs open (often that is me), and helps differentiate search engine results. eg, this isn't great;

image

@owenh000 owenh000 added the enhancement New feature or request label Apr 3, 2024
@owenh000
Copy link
Owner

owenh000 commented Apr 3, 2024

Hi @jamesread, it looks like this is a feature request, so I've labeled it as such.

Issue #46 needs to be done first.

@jamesread
Copy link
Author

@owenh000 Many thanks for the quick reply, and totally understand the need for #46 - I had a look through the code myself, but woah it's difficult to understand (purely due to my very poor understanding of Ruby, and zero understanding of Asciidoctor's internals.

What sort of timeframe do you realistically think it will take for you to implement this?

@owenh000
Copy link
Owner

owenh000 commented Apr 3, 2024

What sort of timeframe do you realistically think it will take for you to implement this?

Without sponsors or some other arrangement, this is just a hobby project and I don't expect to have time to work on it at all aside from the issue discussions and any really simple bug fixes. Unfortunately some of the "that should be easy to fix" bugs are instead, after a closer look, pointing to the need for some overall clean-up!

If you are interested in sponsoring this project then please see my Sponsors page. And as noted there, you are welcome to contact me by email too.

@jamesread
Copy link
Author

You have an email from me in your inbox, to ask about a one-time sponsorship for this issue :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants