# How to make the "Docs" button work in PkgTemplates autogenerated Readme

**URL:** https://discourse.julialang.org/t/how-to-make-the-docs-button-work-in-pkgtemplates-autogenerated-readme/53306
**Category:** New to Julia
**Tags:** question, pkgtemplates
**Created:** [January 13, 2021, 8:56pm UTC](https://discourse.julialang.org/t/how-to-make-the-docs-button-work-in-pkgtemplates-autogenerated-readme/53306 "2021-01-13T20:56:07Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![mkarikom](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkarikom/32/7096_2.png) [@mkarikom](https://discourse.julialang.org/u/mkarikom)
#### Post date: [January 13, 2021, 8:56pm UTC](https://discourse.julialang.org/t/how-to-make-the-docs-button-work-in-pkgtemplates-autogenerated-readme/53306/1 "2021-01-13T20:56:07Z")

</div>

I basically used the second example from the PkgTemplates Readme:

```julia
t = Template(;
    dir="~/code",
    plugins=[
        Git(; manifest=true, ssh=true),
        Codecov(),
        TravisCI(; x86=true),
        Documenter{TravisCI}(),
    ],
)

```

This makes a Readme for the new package with a button like:  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/c/c/cc6a92d32728d3cc9c34cf8a2ef47273f6b3e17c.png)

However, when I click this I get a 404 error, even though there are a bunch of docstrings in the various src files.

How do I make sure that when I push to the repo, it renders the docstrings in all the files and make this button link to them?

---

<div class="post-metadata">

### Author: ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)
#### Post date: [January 15, 2021, 8:28am UTC](https://discourse.julialang.org/t/how-to-make-the-docs-button-work-in-pkgtemplates-autogenerated-readme/53306/2 "2021-01-15T08:28:05Z")

</div>

The documentation is generated in the `gh-pages` branch in your repo, and you might have to instruct github to use that branch in your repo settings. Have you set the secrets up correctly in travis and github so that the documentation is being built and pushed to your `gh-pages` branch correctly?

---

<div class="post-metadata">

### Author: ![mkarikom](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkarikom/32/7096_2.png) [@mkarikom](https://discourse.julialang.org/u/mkarikom)
#### Post date: [January 15, 2021, 7:12pm UTC](https://discourse.julialang.org/t/how-to-make-the-docs-button-work-in-pkgtemplates-autogenerated-readme/53306/3 "2021-01-15T19:12:08Z")

</div>

Thanks @jishnub!

There are a couple things I’m still confused about:

1. Regarding `Documenter{TravisCI}()`, what does TravisCI have to do with docstrings or Documenter.jl? I’m getting Travis build reports for my unit tests on each commit, so Travis authentication isn’t the issue.
2. Is gh-pages a web-hosting thing I have to sign up for or is it somehow living inside the project repo?

---

<div class="post-metadata">

### Author: ![danielw2904](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/danielw2904/32/10890_2.png) [@danielw2904](https://discourse.julialang.org/u/danielw2904)
#### Post date: [January 15, 2021, 8:01pm UTC](https://discourse.julialang.org/t/how-to-make-the-docs-button-work-in-pkgtemplates-autogenerated-readme/53306/4 "2021-01-15T20:01:48Z")

</div>

The documentation is built and deployed by the CI that’s why it is used with Documenter. If I recall correctly the stable documentation will only be available after you tag a release. Before that you should still have the dev button.