Technical Writing milestone plan for 18.10
This issue provides a consolidated view of what the Technical Writing team expects to work on with their assigned groups for the upcoming milestone. In addition to the work with their assigned groups, the [Technical Writing team](https://handbook.gitlab.com/handbook/product/ux/technical-writing/) also works on other tasks that are not reflected in this issue.
**On the `1st` of each month:**
The [TW Bot](https://gitlab.com/project_10614162_bot_25c9076e9d506547fa969897d2d0a5f3) creates the issue for the upcoming milestone using a [scheduled pipeline](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/pipeline_schedules) and a [template](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/blob/main/.gitlab/issue_templates/tw-milestone-plan.md).
We open this issue on the 1st to align with planning activities carried out by other teams and stakeholders. The 1st is on or around 12 days before the milestone begins. For example, for 16.8 (2024-01-17), the milestone starts on 2023-12-16 and we open this issue on 2023-12-01. For more information, see the [product development timeline](https://handbook.gitlab.com/handbook/engineering/workflow/#product-development-timeline).
**By the start of the milestone:**
The TW carries out [planning activities](https://docs.gitlab.com/development/documentation/workflow/#planning) for their assigned groups, and populates [Checklist and links](#checklist-and-links) to confirm these activities have taken place:
1. Have a conversation - synchronously or asynchronously - with either the group **PM** or **EM** to review:
- Planned ~"documentation" and ~"UI text" work for the upcoming milestone (`Milestone: Upcoming`) or (`Milestone: Started`).
- Improvement or development opportunities they're aware of in their areas of the product documentation.
- If any deprecations can be announced according to the [process for deprecations, removals, and breaking changes](https://handbook.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes). Deprecations should be announced as soon as possible, but the group should have a firm idea of deprecated features from about half-way through a major release cycle.
This can be a regular group meeting or any other means of communication that you have established with your group.
If the TW, PM, or EM is unavailable around the beginning of the milestone, we encourage using async methods (like commenting in issues or Slack messages) or having conversations at an earlier time. If the conversation happens before the creation of the issue, just add the planning information to the issue when it's available.
2. Identify a linked artifact that describes the upcoming planned work, such as:
- An issue board for the group's documentation/UI text items for the milestone.
- A filter that describes/lists the planned work. ([Example](https://gitlab.com/gitlab-org/gitlab/-/boards/7694915?label_name%5B%5D=devops%3A%3Aplan&label_name%5B%5D=documentation&milestone_title=Upcoming) for ~"devops::plan")
- The group's planning issue, if it identifies issues/MRs that require Technical Writing team involvement. ([Example](https://gitlab.com/gitlab-org/ci-cd/pipeline-authoring/-/issues/30))
3. Select the appropriate checkboxes and share the links to planned features to confirm that the "conversation" has taken place.
## Checklist and links
After you've reviewed the plan with your PM or EM, select the checkbox for your group. If you can't meet with the PM or EM for some reason (perhaps they're on PTO), append that information to the end of the line and leave the checkbox cleared.
### Stage ~"devops::package"
- [x] ~"group::container registry" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/589090)
- [x] ~"group::package registry" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/589090)
### Stage ~"devops::verify"
- [x] ~"group::pipeline authoring" - [Planning issue](https://gitlab.com/gitlab-org/ci-cd/pipeline-authoring/-/work_items/211)
- [x] ~"group::pipeline execution" - [Doc issues epic](https://gitlab.com/groups/gitlab-org/-/work_items/19526), [issue board](https://gitlab.com/groups/gitlab-org/-/boards/1372896?label_name%5B%5D=group%3A%3Apipeline%20execution&label_name%5B%5D=documentation)
- [x] ~"group::runner core" - [Board](https://gitlab.com/groups/gitlab-org/-/boards/9726167?milestone_title=Started&label_name%5B%5D=group%3A%3Arunner%20core)
- [x] ~"group::ci functions platform" - [Planning issue](https://gitlab.com/gitlab-org/step-runner/-/issues/387)
- [x] ~"group::ci platform" - [Planning issue](https://gitlab.com/gitlab-org/ci-cd/ci-platform-group/-/work_items/10)
### Stage ~"devops::growth"
- [x] [Growth First Orders Epic board](https://gitlab.com/groups/gitlab-org/-/epic_boards/2079888?label_name%5B%5D=Growth%3A%20Driving%20First%20Orders&label_name%5B%5D=Next%20Up&label_name%5B%5D=section%3A%3Agrowth) (18.10 will focus on items with ~"workflow::in dev")
### Stage ~"devops::ai-powered"
- [ ] https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1593+
* https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1594+
- [ ] ~"group::agent foundations" - `Link to board or filter`
- [x] ~"group::ai coding" - [Planning issue](https://gitlab.com/gitlab-com/ai-engineering/ai-coding/team-ops/-/work_items/4), [board](https://gitlab.com/groups/gitlab-org/-/boards/10081212?milestone_title=18.10&label_name%5B%5D=group%3A%3Aai%20coding)
- [x] ~"group::ai framework" - [board](https://gitlab.com/groups/gitlab-org/-/boards/7346017?label_name%5B%5D=group%3A%3Aai%20framework&milestone_title=18.10)
- [x] ~"group::custom models" - [Planning issue](https://gitlab.com/gitlab-org/ai-powered/custom-models/custom-models/-/work_items/123)
- [x] ~"group::duo chat" - [Duo Chat Development Board](https://gitlab.com/groups/gitlab-org/-/boards/9922052?label_name%5B%5D=group%3A%3Aduo%20chat&milestone_title=18.8&milestone_title=Started)
- [x] ~"group::editor extensions" - [Planning issue](https://gitlab.com/gitlab-org/editor-extensions/meta/-/work_items/299)
- [x] ~"group::global search" - [issue](https://gitlab.com/gitlab-org/search-team/team-tasks/-/work_items/266)
- [x] ~"group::workflow catalog" - [planning issues](https://gitlab.com/gitlab-org/ai-powered/workflow-catalog/team-tasks/-/work_items?sort=created_date&state=opened&label_name%5B%5D=Planning%20Issue&first_page_size=100)
### Stage ~"devops::create"
- [x] ~"group::code review" - [board](https://gitlab.com/groups/gitlab-org/-/boards/2159734?label_name%5B%5D=group%3A%3Acode%20review&label_name%5B%5D=Technical%20Writing&milestone_title=18.10), [planning issue](https://gitlab.com/gitlab-org/create-stage/-/issues/13296)
- [x] ~"group::import" - [issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/588656)
- [x] ~"group::source code" - [board](https://gitlab.com/groups/gitlab-org/-/boards/1626594?label_name%5B%5D=group%3A%3Asource%20code&label_name%5B%5D=Technical%20Writing&milestone_title=18.10), [planning issue](https://gitlab.com/gitlab-org/create-stage/-/issues/13297)
### Stage ~"devops::plan"
- [x] ~"group::knowledge" - [board](https://gitlab.com/groups/gitlab-org/-/boards/9797565?label_name%5B%5D=Technical%20Writing&label_name%5B%5D=group%3A%3Aknowledge&milestone_title=18.10) | [planning issue](https://gitlab.com/gitlab-org/plan-stage/product/-/issues/215)
### Stage ~"devops::analytics"
- [x] ~"group::optimize" - [board](https://gitlab.com/groups/gitlab-org/-/boards/4893971?label_name[]=documentation&milestone_title=18.10)
### Stage ~"devops::fulfillment"
All Fulfillment groups: [board](https://gitlab.com/groups/gitlab-org/-/boards/4978071?milestone_title=Upcoming&label_name%5B%5D=documentation)
- [x] ~"group::provision" - [issue](https://gitlab.com/gitlab-org/fulfillment/meta/-/issues/2568)
- [x] ~"group::utilization" - [issue](https://gitlab.com/gitlab-org/fulfillment/meta/-/issues/2577)
- [x] ~"group::seat management" - [issue](https://gitlab.com/gitlab-org/fulfillment/meta/-/issues/2585)
- [x] ~"group::subscription management" - [issue](https://gitlab.com/gitlab-org/fulfillment/meta/-/issues/2583)
### Stage ~"devops::gitlab dedicated"
GitLab Dedicated issues: [board](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/boards/2843761?label_name%5B%5D=documentation)
- [x] ~"group::switchboard" - [board](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/boards/2843761?label_name%5B%5D=group%3A%3Aswitchboard&label_name%5B%5D=documentation), [Switchboard FY27Q1 deliverables](https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/work_items/849),
- [x] ~"group::environment automation" - [board](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/boards/2843761?label_name%5B%5D=group%3A%3Aenvironment%20automation&label_name%5B%5D=documentation)
- [x] ~"group::US PubSec" - [board](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/boards/4964764?label_name%5B%5D=group%3A%3AUS%20PubSec&label_name%5B%5D=documentation)
### Stage ~"devops::gitlab delivery"
- [x] ~"group::build" - `Link to board or filter`
- [x] ~"group::operate" - [board](https://gitlab.com/groups/gitlab-org/-/boards/9192617?label_name%5B%5D=group%3A%3Aoperate)
### Stage ~"devops::tenant scale"
- [x] ~"group::geo" - [issue](https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/?sort=updated_desc&state=opened&search=outlook)
- [x] ~"group::gitaly" - [board](https://gitlab.com/groups/gitlab-org/-/boards/1140874?label_name%5B%5D=group%3A%3Agitaly&milestone_title=Started)
- [x] ~"group::organizations" - [Issue board](https://gitlab.com/groups/gitlab-org/-/boards/7487616?label_name%5B%5D=group%3A%3Aorganizations&milestone_title=18.10)
- [ ] ~"group::tenant services" - `Link to board or filter`
### Stage ~"devops::application security testing"
- [ ] ~"group::composition analysis" - `Link to board or filter`
- [x] ~"group::dynamic analysis" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/issues/588351)
- [x] ~"group::secret detection" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/590055)
- [x] ~"group::static analysis" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/589567)
### Stage ~"devops::security risk management"
- [x] ~"group::security insights" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/588414)
- [x] ~"group::security policies" - [Planning issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/591332)
- [ ] ~"group::security platform management" - No issue.
### Stage ~"devops::software supply chain security"
- [x] ~"group::authentication" - [Issue board](https://gitlab.com/gitlab-org/gitlab/-/boards/4374016?not%5Bmilestone_title%5D=Backlog&label_name%5B%5D=group%3A%3Aauthentication)
- [x] ~"group::authorization" - [Issue board](https://gitlab.com/gitlab-org/gitlab/-/boards/7129613?not%5Bmilestone_title%5D=Backlog&label_name%5B%5D=group%3A%3Aauthorization)
- [x] ~"group::pipeline security" - [Planning issue](https://gitlab.com/gitlab-org/software-supply-chain-security/pipeline-security-group/-/work_items/26)
### Stage ~"devops::developer experience"
- [ ] ~"group::api platform" - [Issue board](https://gitlab.com/groups/gitlab-org/-/boards/9736881?not%5Bmilestone_title%5D=Backlog&label_name%5B%5D=group%3A%3Aapi%20platform)
## Other events and team efforts this milestone
### Group changes
```glql
display: table
title: Group changes
description: Group changes we are tracking this milestone
fields: title, milestone, state
limit: 20
query: project = "gitlab-org/technical-writing/team-tasks" AND label = "TW group change" AND milestone = "18.10"
```
### Events
- [`Scale 23x`](https://www.socallinuxexpo.org/scale/23x)` North America's largest community-run open source conference. March 5-8, 2026`
- [`Embedded World EMEA`](https://www.embedded-world.de/en)` Leading annual trade fair and conference to embedded systems industry. March 10-12,2026`
### :scissors: UX Paper Cuts
The Paper Cuts team has been merged into the Design Systems team. Anyone is welcome to create MRs to make changes in the product if they feel comfortable doing so. Some changes may come from your assigned teams or groups.
### TW recurring tasks
- [Release Post structural check](https://handbook.gitlab.com/handbook/marketing/blog/release-posts/managers/): `@chandran`
- [Monthly doc version](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/main/doc/releases.md): `@rdickenson`
- [Docs project maintenance tasks](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/blob/main/.gitlab/issue_templates/tw-monthly-tasks.md): `@brendan777`
- [Review docs-only backlog issues](https://docs.gitlab.com/development/documentation/workflow/#review-and-triage-documentation-only-backlog-issues): All technical writers
- [Monthly content audit update](https://internal.gitlab.com/handbook/product/ux/technical-writing/content-audit/#monthly-update-page-views): `@rjlandry`
- [<span dir="">Quarterly content audit update</span>](https://internal.gitlab.com/handbook/product/ux/technical-writing/content-audit/#quarterly-update-all-other-sheets)<span dir="">, if applicable: n</span>/a
### TW team KRs
- [Deepen content design skillset](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1581)
- [Reduce docs feedback widget backlog](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1583)
- [Daily DAP usage consistently at 90% or higher](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1586)
### Other team KRs
List of KRs from other teams with ~"Technical Writing" impact or involvement this quarter:
| Stage and group | TW | KR |
|-----------------|----|----|
| `stage and group label` | `TW name` | `link to KR` |
| `stage and group label` | `TW name` | `link to KR` |
| `stage and group label` | `TW name` | `link to KR` |
### Stage lead issues
| Stage | TWs | Issue |
|-------|-----|-------|
| ~"devops::application security testing" | `@rdickenson` `@rsarangadharan` | https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1578 |
| ~"devops::create" | `@aqualls` `@brendan777` `@eread` | https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1576 |
| ~"devops::plan" | `@brendan777` | https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1577 |
| ~"devops::verify" | `@lyspin` `@marcel.amirault` `@rsarangadharan` | https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1575 |
### Docs site work
- [Issue board](https://gitlab.com/groups/gitlab-org/-/boards/4340643?label_name%5B%5D=Category%3ADocs%20Site) (ongoing work)
## TW Manager tasks
- [x] Replace `<milestone>` in the group changes query with the milestone number. For example, `"18.2"`.
- [x] Check the [Developer Advocacy Team Calendar](https://handbook.gitlab.com/handbook/marketing/developer-relations/developer-advocacy/calendar/) for Hackathons and other events that may impact team velocity this milestone. List the events and dates in the section above. Let the team know in the `tw-team` Slack channel, and as a read-only in the TW Team meeting.
- [x] Assign another month of [regularly scheduled tasks](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#regularly-scheduled-tasks).
- [x] Update the [schedule table](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#schedule) with the assignments for each role. (Robert: [MR to update schedule table](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18408))
- [x] Update [`release_post_managers.yml`](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/release_post_managers.yml) with the `structural_check` assignment. This data populates the [release post scheduling](https://handbook.gitlab.com/handbook/marketing/blog/release-posts/managers/) handbook page. (Robert: [MR to update release post managers file](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/142574))
issue