Should we have <kotl.in/maven> and <kotl.in/gradle...

# announcements

[stevecstian]

Should we have kotl.in/maven and kotl.in/gradle?

[Shawn]

for what?

[stevecstian]

https://kotlinlang.org/docs/reference/using-gradle.html and https://kotlinlang.org/docs/reference/using-maven.html

[Shawn]

I don’t really think either are directly accessed so frequently as to warrant kotl.in links

[Shawn]

kotl.in/issue is useful because folks constantly have things to file issues over

[Shawn]

usage with build systems is something you look up maybe once or twice when you get started or start a new project

[Shawn]

that’s a quick google since it’s in the docs

[Shawn]

google doesn’t index youtrack application links (e.g. new issue, login, etc) very well.

[stevecstian]

At least to me, those links might help people to get started.

[Shawn]

I feel like if someone were at that stage with kotlin, it would be much more useful to link https://kotlinlang.org/docs/reference/

[Shawn]

(which they can easily get to by googleing kotlin docs)

[stevecstian]

We also have kotl.in/coroutines and kotl.in/1.3

[Shawn]

both useful for folks who already know kotlin and are aware of kotl.in links

[Shawn]

also two of the most hotly discussed subjects on this slack at least

[hho]

I'd love the shortlinks. I use the Maven page of the docs all the time (to C&P the huge XML block)...

[stevecstian]

Having same experience with Maven...