You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _info-architecture/0003-swift-docs-proposal.md
+29-30Lines changed: 29 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,17 +169,17 @@ Based on the existing content in Swift.org, the general goal is to migrate the m
169
169
All of the listed markdown files would remain in `/documentation`, with their front matter (Jekyll metadata) updated to redirect the URL requests to the new locations as content is migrated and accepted into the new docs repository.
170
170
Markdown files prefixed with `_` are typically only included in other files and not referenced by URL, and can be removed after they are migrated.
171
171
172
-
## Migration Plan for files under `documentation`
172
+
## Migration Plan
173
173
174
-
A few exceptions are detailed after the file names, to accommodate very out-of-date content, or content that's already replicated in other locations.
175
-
176
-
This proposal is primarily meant to provide a guide to the structure for content as we want to see it,
177
-
and isn't meant to provide a full and discrete audit of all existing content.
178
-
Nevertheless, a few examples stand out and have been discussed previously within the community as needing updates, or removal and relevant links redirected to more up-to-date and recent content.
174
+
This proposal is primarily meant to provide a guide to the structure for content as we want to see it.
175
+
In the process of establishing this new repository and structure of DocC catalogs, the following files from swift.org are intended to be migrated.
179
176
A full audit of the documentation for recency and relevancy is worthwhile, but beyond the scope of this proposal.
180
177
181
-
The notes of this migration are intended to be guides, and any migration process isn't expected to be done immediately and in one sweep.
178
+
This list is intended to be a guide, with additional potential updates from the relevant reviewing team, and is not expected to be complete in a single sweep.
182
179
The migration can, and should, occur incrementally, building into the docs repository as supported by the community including content reviewers and their availability.
180
+
The migration process itself will be tracked by pull requests and within an issue or issues housed at https://github.com/swiftlang/swift-org-website/, with the issues and tracking to be started if the proposal is approved.
181
+
182
+
Files under the `documentation` directory on Swift.org:
183
183
184
184
|`source`| status & destination |
185
185
| - | - |
@@ -224,29 +224,28 @@ The migration can, and should, occur incrementally, building into the docs repos
224
224
|[`source-compatibility/index.md`](https://www.swift.org/documentation/source-compatibility/index.html)| migrate to [project-operations](https://github.com/swiftlang/project-operations) repository (referencess to swift source compatibility project) |
225
225
|[`source-code/index.md`](https://www.swift.org/documentation/source-code/index.html)| migrate to [project-operations](https://github.com/swiftlang/project-operations) repository (partial list to existing source code that goes into toolchain, needs updating if kept) |
0 commit comments