# New pkg.julialang.org

**URL:** <https://discourse.julialang.org/t/new-pkg-julialang-org/22622>\
**Category:** Community\
**Tags:** announcement\
**Created:** [April 2, 2019, 1:24am UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622 "2019-04-02T01:24:18Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![felipenoris](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/felipenoris/32/553_2.png) [@felipenoris](https://discourse.julialang.org/u/felipenoris)\
**Post date:** [April 2, 2019, 2:37pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/21 "2019-04-02T14:37:18Z")

</div>

Thanks for this!

Just picked a corner case: a package like [Pkg.jl](https://github.com/JuliaLang/Pkg.jl) doesn’t show up in the search results.

---

<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:** [April 2, 2019, 2:45pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/22 "2019-04-02T14:45:45Z")

</div>

Pkg is not registered in General. When more standard libraries get their own repos like Pkg it would be nice with a dedicated section for those on [pkg.julialang.org](http://pkg.julialang.org). For the time beeing it could be worthwile to special case Pkg to include it.

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 2, 2019, 3:26pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/23 "2019-04-02T15:26:21Z")

</div>

It would be great if there was some way of coordinating the redundant tags, for example there is a `math` and a `mathematics` tag… maybe the result lists could be combined for words like that.

All it would take is a list of synomyms, so that equivalent words and tags get grouped. ([#16](https://github.com/JuliaDocs/DocumentationGenerator.jl/issues/16))

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [April 2, 2019, 3:42pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/24 "2019-04-02T15:42:45Z")

</div>

Once search works, we’ll probably also want to inlcude Julia’s own docs since that badly needs search that works. We can probably have options to search any of:

- base
- stdlibs
- packages

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [April 2, 2019, 3:44pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/25 "2019-04-02T15:44:06Z")

</div>

We can machine learn it! 😁

---

<div class="post-metadata">

**Author:** ![DoktorMike](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/doktormike/32/2736_2.png) [@DoktorMike](https://discourse.julialang.org/u/DoktorMike)\
**Post date:** [April 2, 2019, 5:20pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/26 "2019-04-02T17:20:22Z")

</div>

Well done guys 🍾🍰🎂

---

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [April 2, 2019, 5:37pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/27 "2019-04-02T17:37:04Z")

</div>

> [@pfitzseb](#):
>
> By default, we build whatever you have in `docs/make.jl` or fall back to your `README`

It looks like it does not support `docs/Project.toml`? Is there any plan to support docs-only dependencies?

> <https://github.com/JuliaDocs/DocumentationGenerator.jl/blob/00151f539f9248e791f4c1a62baf2f921f33f57f/src/worker_work.jl#L21-L32>

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [April 2, 2019, 5:42pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/28 "2019-04-02T17:42:06Z")

</div>

I think we mostly handle docs-only dependencies correctly, but the implementation is a major hack IIRC. So yes, better handling for docs in their own environment is definitely planned.

---

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [April 2, 2019, 6:34pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/29 "2019-04-02T18:34:45Z")

</div>

I have a [customized `docs/make.jl` script](https://github.com/tkf/Transducers.jl/blob/v0.2.1/docs/make.jl) that is [not handled](https://pkg.julialang.org/docs/Transducers/cATK6/0.2.1/) by `rewrite_makefile`

> <https://github.com/JuliaDocs/DocumentationGenerator.jl/blob/00151f539f9248e791f4c1a62baf2f921f33f57f/src/DocumentationGenerator.jl#L84-L89>

There seems to be a major issue in how `docs/make.jl` works — it builds _and_ deploys the docs. I know Documenter works hard to detect Travis environment but I think it’d be much more straightforward if there are `docs/build.jl` and `docs/deploy.jl`.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [April 2, 2019, 7:43pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/30 "2019-04-02T19:43:05Z")

</div>

A more declarative way for specifying docs would make a lot of sense, IMHO. Say there was a config file in the `docs` folder that had all the kind of settings that one currently passes to the two function calls in `make.jl`, and then `Documenter` just exported two functions, say `build(packagename)` and `deploy(packagenmae`). I think that would make things quite a bit easier.

---

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [April 2, 2019, 9:09pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/31 "2019-04-02T21:09:26Z")

</div>

> [@davidanthoff](#):
>
> `Documenter` just exported two functions, say `build(packagename)` and `deploy(packagenmae` )

Anything that works like `Pkg.test(packagename)` entrypoint for docs (i.e., something that sets up the environment as well) would be great. This way, package writers can check if the docs build for `DocumentationGenerator` works by locally invoking the same function.

---

<div class="post-metadata">

**Author:** ![mcabbott](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mcabbott/32/6603_2.png) [@mcabbott](https://discourse.julialang.org/u/mcabbott)\
**Post date:** [April 4, 2019, 2:09pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/32 "2019-04-04T14:09:20Z")

</div>

This is very nice to have! I have two questions:

- Is there a standard link to the page for a given package, not to a particular version? For example to link to latest docs page from the readme.

- Is there any way to control what functions are included? Some docstrings on functions used internally are just notes to remind myself; perhaps if these functions are named `_fun` they could be excluded.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [April 4, 2019, 2:20pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/33 "2019-04-04T14:20:24Z")

</div>

> [@mcabbott](#):
>
> Is there a standard link to the page for a given package, not to a particular version? For example to link to latest docs page from the readme.

No, not yet. We should just link e.g. `https://pkg.julialang.org/docs/IJulia/nfu7T/stable` to `https://pkg.julialang.org/docs/IJulia/nfu7T/1.9.3` though, just like Documenter does.

> [@mcabbott](#):
>
> Is there any way to control what functions are included? Some docstrings on functions used internally are just notes to remind myself; perhaps if these functions are named `_fun` they could be excluded.

There is not, see [here](https://github.com/JuliaDocs/DocumentationGenerator.jl/issues/14) for more discussion.

---

<div class="post-metadata">

**Author:** ![Roger-luo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/roger-luo/32/3399_2.png) [@Roger-luo](https://discourse.julialang.org/u/Roger-luo)\
**Post date:** [April 4, 2019, 2:36pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/34 "2019-04-04T14:36:10Z")

</div>

It doesn’t sounds hard, some word2vec algorithm will be enough.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [April 4, 2019, 3:07pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/35 "2019-04-04T15:07:59Z")

</div>

> [@pfitzseb](#):
>
> No, not yet. We should just link e.g. `https://pkg.julialang.org/docs/IJulia/nfu7T/stable` to `https://pkg.julialang.org/docs/IJulia/nfu7T/1.9.3` though, just like Documenter does.

Ideally, `https://pkg.julialang.org/docs/IJulia` would be a redirect to `https://pkg.julialang.org/docs/IJulia/nfu7T/` when there’s only one package named `IJulia` or a disambiguation page when there’s more than one package named `IJulia` and `https://pkg.julialang.org/docs/IJulia/nfu7T/` is a redirect to the docs for the current version of `IJulia`.

Which brings up another question: are we going to have generated docs for all historical versions? If not, what is the point of having the version number in the URL? Doesn’t that just mean that we’re ruining our own SEO by having transient, ever-changing URLs instead of fixed URLs with content that changes over time?

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [April 4, 2019, 3:12pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/36 "2019-04-04T15:12:16Z")

</div>

> [@StefanKarpinski](#):
>
> Which brings up another question: are we going to have generated docs for all historical versions?

If I understood @Venkatesh_D correctly, yes – at least for all versions registered from now on. We could also generate docs for older versions, but do we want that?

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [April 4, 2019, 3:21pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/37 "2019-04-04T15:21:17Z")

</div>

Hmm. This is different from what we decided to do for Julia itself. For Julia itself, we decided to have a single page for a given major version (only v1 so far) and then just note in the docs when a feature was added in a given version, e.g. Julia 1.2, that you need at least that version to use the feature. This has the nice property that everyone can always look at the most recent docs, which are usually better and more complete than historical snapshots of the docs.

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [April 4, 2019, 3:25pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/38 "2019-04-04T15:25:14Z")

</div>

> [@StefanKarpinski](#):
>
> Doesn’t that just mean that we’re ruining our own SEO by having transient, ever-changing URLs instead of fixed URLs with content that changes over time?

This used to happen to me all the time with the julialang docs. Google was constantly taking me to v0.4.

One monkey patch I thought of for this would be a banner at the top (like the one some sites use to tell you they use cookies) that just says “do you know you’re not on the latest version of this page? Click here for the current stable version.”

I have no concept of how hard that would be to implement…

---

<div class="post-metadata">

**Author:** ![chakravala](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chakravala/32/6832_2.png) [@chakravala](https://discourse.julialang.org/u/chakravala)\
**Post date:** [April 15, 2019, 6:57pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/39 "2019-04-15T18:57:32Z")

</div>

Could [pkg.julialang.org](http://pkg.julialang.org) data be updated one more time, now that METADATA is finished?

How often will it be updated?

---

<div class="post-metadata">

**Author:** ![Venkatesh\_D](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/venkatesh_d/32/7760_2.png) [@Venkatesh\_D](https://discourse.julialang.org/u/Venkatesh_D)\
**Post date:** [April 15, 2019, 7:54pm UTC](https://discourse.julialang.org/t/new-pkg-julialang-org/22622/40 "2019-04-15T19:54:40Z")

</div>

We will be updating tomorrow again hopefully, with some bug fixes

[Previous page](https://discourse.julialang.org/t/new-pkg-julialang-org/22622.md?page=1)

[Next page](https://discourse.julialang.org/t/new-pkg-julialang-org/22622.md?page=3)