Quote:
Originally Posted by DiapDealer
Sure. It's in the important links section of the Sigil github wiki, but I can add a link to the main readme if you think it will help.
But what would you suggest for making it more prominent on the documentation page? The link is already there. In my experience, it's not a problem of the link not standing out. The problem is they simply don't read the documentation page. Or any of the pages, really. For a large portion of the people who can't find the user guide, I've found that it's typically because the darn thing simply refuses to fall out of the sky and into their laps.  |
Ha! I didn't even remember there was a Wiki!
Anyway, when I went searching for a link to the User Guide for jonesyb, it took a lot of clicking for me to find it, whereas links to MobileRead were prominently posted everywhere, which is why I think people come here first and don't even realize there is a User Guide. If a link to the User Guide were posted wherever there is a link to MobileRead, more people might try the User Guide first (if that's even your goal).
For the Documentation page, if you want people to check the User Guide before asking on MobileRead, I suggest making that the first paragraph rather than the last. As it is, the first paragraph says: "Please consider the Sigil User Forums at Mobileread to be the primary resource for getting help with your Sigil questions." If I read that, I'd stop reading right there and click the Mobileread link, never making it to the last paragraph.
Also, you might attach a link to "Sigil User Guide" so that it's highlighted and clickable and make it capitalized and bold. That would make it more noticeable.
Code:
<p>The latest release of the <a href="https://github.com/Sigil-Ebook/sigil-user-guide/releases/latest"><strong>Sigil User Guide</strong></a> can always be found <a href="https://github.com/Sigil-Ebook/sigil-user-guide/releases/latest">in its own repository</a> (in EPUB format), as well as in the <a href="https://github.com/Sigil-Ebook/Sigil/tree/master/docs">docs directory</a> of the source tree.</p>