docs: group the Dockerfile page by scope - #2964
Open
vladfrangu wants to merge 2 commits into
Open
Conversation
Contributor
|
✅ Preview for this PR (commit |
vladfrangu
force-pushed
the
docs/dockerfile-page-regroup
branch
2 times, most recently
from
September 10, 2026 09:23
c6325ea to
9015588
Compare
vladfrangu
force-pushed
the
docs/dockerfile-page-regroup
branch
from
September 11, 2026 09:56
4203640 to
05f9bd2
Compare
apify-service-account
added
the
t-tooling
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #2954. Follows up on the review note there that the page alternates between general, Node.js and Python advice.
Sections are now grouped: general first (base images, available tags, custom Dockerfile), then one Node.js images block (base images, tag format, version pinning, package managers, TypeScript builds), then Python images (base images, tag format), then the migration guide. Pure move apart from three lines: the tag-naming intro sentence is gone, the pinning intro no longer says "Node.js/Python" since it sits under Node.js, and the Python tag format gained a one-line pinning recommendation. Removed anchors:
#image-tag-naming-convention;#nodejs-imagesand#python-imagesnow point at the new blocks. Nothing else insources/links to them.[🤖] Claude Code using Fable 5