# PSA: Use a project for building your docs

**URL:** https://discourse.julialang.org/t/psa-use-a-project-for-building-your-docs/14974
**Category:** Tooling
**Tags:** documentation
**Created:** [September 14, 2018, 7:09pm UTC](https://discourse.julialang.org/t/psa-use-a-project-for-building-your-docs/14974 "2018-09-14T19:09:42Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [September 15, 2018, 4:18pm UTC](https://discourse.julialang.org/t/psa-use-a-project-for-building-your-docs/14974/8 "2018-09-15T16:18:40Z")

</div>

Right, maybe that is actually a better option but then you have to explicitly upgrade your doc build dependencies to get shiny new stuff. I actually do this in [Literate.jl](https://github.com/fredrikekre/Literate.jl/blob/22c6d530d3d331cd0b260c745bd1d48274c56dfd/.travis.yml#L25-L26), where I have `developed` the package with a relative path, [stored in the manifest](https://github.com/fredrikekre/Literate.jl/blob/22c6d530d3d331cd0b260c745bd1d48274c56dfd/docs/Manifest.toml#L94). That means that `Pkg.instantiate()` is enough, and I don’t have to `Pkg.add` my own package as a separate step.

---

_[View the full topic](https://discourse.julialang.org/t/psa-use-a-project-for-building-your-docs/14974)._