Large request intake and timelines

Explains which path a large request to about.gitlab.com takes, how long each step takes, and how to work out the earliest go-live date.

What a large request is

A large request is a new page or a big change to a page on about.gitlab.com. You file it as an issue with the large request template.

This page explains which path your request takes. It also explains why each timeline is the length it is and how to work out the earliest go-live date. Each team confirmed its own timeline in the intake issue.

Content freeze

Content freeze is the day you hand the final content and the images to Marketing Engineering. Both must be final.

All timelines on this page count from content freeze, except the MOps forms timeline, which counts from when MOps confirms the form requirements. No timeline counts from the day you open the issue.

Choose a path

There are two paths for the page itself: the fast path and the custom design path.

Pick the fast path if your content follows an existing page layout. In other words, a page like yours already exists. The template says: “Not sure? Pick Fast path if a page like yours already exists.”

Pick the custom design path if your page needs a new layout or new components.

The triager suggests a reference layout for the fast path. These are some examples:

Fast path timeline

The target is about 4 business days from content freeze. This includes SEO review.

Marketing Engineering quoted “about 4 business days from content” on recent requests. The quote had two conditions. The page used an existing layout, and the requester supplied product screenshots.

Custom design path timeline

The designer (@Tinaliseng) scopes each request case by case. The design numbers below are estimates for the first round of design only.

  • Net-new design from a Claude artifact takes 1 to 2 business days. The time depends on the level of rework.
  • Net-new design from a content doc takes 3 business days.
  • Add 1 business day if the page needs product images and you provide the screenshots.
  • Add 3 or more business days if Marketing Engineering must source the product images.
  • Add more days for feedback cycles. The time depends on how fast reviewers respond and how much they revise.

After the design is final, engineering takes 1 business day to build the page. Design review and QA take about 1 more business day.

The triager uses 2 business days for a Claude artifact. This is the upper end, so the date isn’t optimistic.

MOps forms timeline

If your page has a form, MOps (@jennyt) builds it. A brand new form takes 5 business days. The count starts when MOps confirms the form requirements are complete.

The reason, in the words of MOps: “our SLA for forms is 5 business days for a brand new form due to the automation required. However, we can typically do this quicker if it’s a lighter weight form and the requirements aren’t anything crazy.”

MOps decides whether a lighter form is faster.

A change to the form rarely moves the date. MOps would likely move the date if the form needs a complete automation overhaul or if you change all the fields.

Send the form requirements early. The MOps clock runs on its own and doesn’t depend on content. If you confirm the form before content freeze, it adds no time.

Technical SEO timeline

Technical SEO (@hsmith-watson) takes 1 business day for a new or changed URL, H1, or meta tags. This needs a working review app or a full description of the change.

The SEO team fills in the URL, redirects, meta title, meta description, and keywords. The PMM provides the H1.

How the earliest go-live date is worked out

The earliest go-live date is the later of two dates.

  1. Content freeze plus the turnaround for your path.
  2. MOps confirmation plus 5 business days. Use this only if the page has a form.

The later date is the binding constraint. It decides the earliest go-live date.

Business days are Monday to Friday. Day 1 is the first business day after the start date. The triager doesn’t count holidays or time off, so Marketing Engineering adjusts the date at refinement.

Example 1: fast path with a form

Content freeze is Monday 2026-11-16. The fast path adds 4 business days, so the content is ready on Friday 2026-11-20.

MOps confirms the form on Wednesday 2026-11-18. Adding 5 business days gives Wednesday 2026-11-25.

The earliest go-live date is 2026-11-25. MOps is the binding constraint.

If MOps had confirmed the form by Friday 2026-11-13, MOps would be ready on 2026-11-20. The earliest go-live date would then be 2026-11-20.

Example 2: custom design path, no form

Content freeze is Monday 2026-11-16. You link a Claude artifact and provide screenshots.

Design takes 2 business days. Screenshots add 1. Build takes 1. Review and QA take 1. That is 5 business days in total.

The earliest go-live date is Monday 2026-11-23. Extra feedback rounds add time.

What the triager does

An AI triage bot runs when you open the issue. It checks the required fields and works out the earliest go-live date. If your requested date is earlier, it flags this and proposes a new date.

The date is an estimate. A person in Marketing Engineering triages every issue before design or engineering starts. That person confirms the date at refinement.

Localization

Translation starts after the English page is live on production. There is no default turnaround for translation, so it isn’t in the earliest go-live date.

Send questions about localization to @mjsibanez.