Link PDF/ePub versions on website?

[karlhorky]

I saw that PDF/ePub versions were added in response to issue #107, thanks!

What do you think of linking to the PDF/ePub versions on the website? Eg. possibly on a new page https://gibbok.github.io/typescript-book/downloads ?

[gibbok]

Hi there! 😊

I believe the website already includes a link to the GitHub folder with the PDF and ePub files, you can find it here:
https://gibbok.github.io/typescript-book/book/downloads-and-website/

Those same links are also included inside the PDF and ePub files themselves. Since the website and the ebooks are automatically generated from the same markdown source, I try to keep things as simple and consistent as possible, and avoid using extra syntax like :target="_blank" in the markdown.

Hope this helps, and thanks for checking!

[karlhorky]

Thanks for the note. I did notice that page, but it's a bit hard to find, and visually seemingly also "inside" the content of the book:

I think for an "alternative version" of the content, I would expect to find the link on a higher level, in a more prominent place.

So something like:

1. Top-level Downloads page with direct links to the files, and human-readable descriptions (not only filenames)
2. Link from header on all pages to this Downloads page

If you don't want to maintain a Downloads page with direct links, an alternative could be to link from the header directly to https://github.com/gibbok/typescript-book/tree/main/downloads

[gibbok]

@karlhorky

Thanks for the suggestion. I understand the expectation of having a more prominent, top-level link for an alternative version of the content.

At the moment, I’d prefer not to further highlight the Downloads pages and would rather encourage users to use the website itself. The Downloads section is already visible in the left navigation on every page, which I think is sufficient for now.

That said, linking directly to GitHub from the header could be an option in the future if we find that users have trouble discovering the downloads.

[karlhorky]

Ok, so if I'm understanding correctly, you're suggesting nothing should be done and the issue closed?

in the future if we find that users have trouble discovering the downloads

I think it will be unclear whether users have this problem or not - my guess is that users will just move on and there will be a missed chance at additional distribution.

At the moment, I’d prefer not to further highlight the Downloads pages and would rather encourage users to use the website itself

Why would you prefer users use the website instead of the downloads? To me it seems like just an additional medium to distribute the work in, which is preferable to some users.

[gibbok]

Hi,

Thanks a lot for taking the time to propose this idea. I really appreciate your input.

From my perspective, putting too much emphasis on downloads could risk fragmenting the overall experience. If users jump straight to files, they may miss updates or newer material. Keeping the website as the primary entry point helps ensure a more consistent and up-to-date experience.

I’d also like to keep the navigation as minimal as possible. Additionally, according to GitHub Traffic, the downloads section is currently the 4th most visited page on the website.

Given all this, I’m proposing that we close this ticket. Thanks again for sharing your thoughts and taking the time to suggest the improvement.

[karlhorky]

Ok, thanks for the consideration, closing.