docs migration - Deploying on Ubuntu
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- markdown, swift
- Domain
- documentation
Research direction
Start with documentation/server/guides/deploying/ubuntu.md and compare it with current supported Ubuntu LTS releases. Migrate it to server-guides/Sources/ServerGuides.docc/deploying/ubuntu.md, add it to ServerGuides.docc/Documentation.md, and run the listed documentation generation and preview commands in server-guides/. Done includes workgroup review and the post-publication redirect updates described in the checklist.
Written by the indexing model from the issue text.
Description
Source: documentation/server/guides/deploying/ubuntu.md
Proposed disposition: Migrate
Proposed destination: server-guides/Sources/ServerGuides.docc/deploying/ubuntu.md
Reviewer: @swiftlang/server-workgroup
Checklist
- Create a GitHub issue to track this migration
- Determine disposition (suggested: Migrate) and confirm destination
- Review source for accuracy against current Ubuntu LTS releases supported by Swift
- Translate Jekyll markdown to DocC markdown format
- Remove YAML front matter
- Convert any Jekyll callouts to DocC-style callouts
- Update cross-references to the DigitalOcean guide to use DocC links
- Verify all shell commands against current Ubuntu setup
- Add article to
ServerGuides.docc/Documentation.mdunder a "Deployment" topic group - Run
swift package generate-documentation --analyze --warnings-as-errorsinserver-guides/ - Preview locally with
swift package --disable-sandbox preview-documentationinserver-guides/ - Submit PR to this repository for server workgroup review
- After merge and publication: add
redirect_to:in the swift.org source file's front matter - Submit redirect PR to swift-org-website
- Dominant language
- Python
- Stars
- 28
- Forks
- 5
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 18
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from swiftlang/docs
-
content migration
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
task
-
content error enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
task
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100