:question: Open question to the community... Do pe...
# general
w
❓ Open question to the community... Do people read the release notes/blog section of the website? ❓ https://www.pantsbuild.org/blog If so, are there any particular topics you'd like to see short posts (< 5 minute) about? These could also be candidates for documentation - but preferably more high level topics
👍 3
b
I do read the blog and come back to some of the blog posts regularly! for example I refer to https://www.pantsbuild.org/blog/2022/08/02/optimizing-python-docker-deploys-using-pants all the time and the release announcements like https://www.pantsbuild.org/blog/2025/10/03/pants-2-29 have been a good way for me to share when the releases happen with my teammates (although lately I've been linking the Github release notes too)
👍 1
💯 1
h
I read the blog / release posts very often. I would love to see some content on best practices and useful features in integration with CI (GitLab CI preferably).
➕ 2
👍 2
g
I also read the blog and I'd love to see more content there, which is not covered in the docs (best practices, integration, more example use-cases etc)
👍 1
w
I'm hoping to also pull more of the integration and best practices into the docs themselves - so they're readily available
b
I'll add that a strength of pants is its great docs site (such a huge contrast to Bazel). I find the blog easier to reference and search than Github discussions
👍 1
w
That's great, thanks! I'm hoping to streamline usages a bit and focus some more on use cases
n
Echoing that the article on docker is great. I think some posts that mention stringing together a few different plugins might be valuable - e.g. building a docker image and deploying with terraform to (e.g.) cloud run. Maybe also some guidance on CLI commands - like how pants can be used to find dependencies of X - I can't think of a good example off the top of my head. But also think better if the docs can be opinionated and suggest the best path/pattern.
👍 1
w
I think a lot of the origin of the docs was "you can use pants to do whatever you want" because of Pants' flexibility - I'm personally more opinionated and like that sort of direction... e.g. "I recommend this, but you can also do whatever you want, I guess, if you insist"
Maybe also some guidance on CLI commands - like how pants can be used to find dependencies of X
Some of these are littered throughout the docs already. I sporadically re-find gems, but not always where I expected. I'm hoping to collapse some of the docs into fewer, longer pages - so that we can maintain context better without jumping around too much
Wouldn't hurt to have some more examples too. I'd been looking for this macro I wrote for months, then I realized it was in a random repo I rarely look at: https://github.com/RobotPajamas/dockerfiles/blob/main/pants-plugins/macros.py
n
Oh... those macros are nice - hadn't considered doing that - didn't realise it would be that simple / didn't want to think about it
w
Yeah! Me neither, until I had to make some - and it was like “whelp, this is ridiculously useful”
So, I want to add a collection of simple macros into the docs as well to de-mystify them
Just a reminder that our docs site repo is here: https://github.com/pantsbuild/pantsbuild.org/issues/ While mechanically some tickets will be created either here or in pants, this feels like a nice place to capture tickets related specifically to the live site
h
I think a lot of the origin of the docs was “you can use pants to do whatever you want” because of Pants’ flexibility - I’m personally more opinionated and like that sort of direction... e.g. “I recommend this, but you can also do whatever you want, I guess, if you insist”
I think the flexibility and high potential is a bit of a hurdle in systems like these, at least for newcomers. Having some concrete useful examples of extended the OOTB features would go along way.