Updating IDP Homepage Docs by amlakhanpal · Pull Request #39393 · DataDog/documentation

amlakhanpal · 2026-08-21T16:35:24Z

Added section for configuring homepage and updated with GitLab and Linear integrations

What does this PR do? What is the motivation?

Merge readiness

Ready for merge

For Datadog employees:

⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

Added section for configuring homepage and updated with GitLab and Linear integrations

github-actions · 2026-08-21T16:44:31Z

Preview links (active after the `build_preview` check completes)

Modified Files

https://docs-staging.datadoghq.com/amlakhanpal/idp-homepage-docs/internal_developer_portal/homepage

domalessi

Thanks, Amrita! Some feedback inline, plus some overarching things:

Prerequisites

Setup requirements show up in Prerequisites and again under GitHub, GitLab, Jira, and Linear, and they've already drifted a bit. I also think the Prerequisites format can be cleaned up a bit.

Something like:

The Homepage aggregates data from your Datadog integrations. Configure the following before using the Homepage.

**GitHub**
Required for the **GitHub** tab in **Your PRs**. An administrator configures the GitHub integration and webhook, and each user signs in with their GitHub account.
[Set up the GitHub integration][1].

**GitLab Source Code**
Required for the **GitLab** tab in **Your PRs**. An administrator configures the GitLab Source Code integration and webhook, and each user signs in with their GitLab account.
[Set up the GitLab Source Code integration][2].

**Jira**
Required for the **Jira** tab in **Your Tickets**. An administrator configures the Jira integration and webhook.
[Set up the Jira webhook][3].

**Linear**
Required for the **Linear** tab in **Your Tickets**. An administrator configures the Linear integration and webhook.
[Set up the Linear webhook][4].

How much UI to document

Several lists describe every status group and column. Useful for agents that can't see the product, but it drifts fast and is hard to maintain. I suggest trimming -- short statement of what the tab is for, plus anything you can't get from the UI.

domalessi · 2026-08-21T19:28:32Z

+- **Comment counts**, including resolved and unresolved discussion counts
+- **Age**, shown as the time since the last update
+
+Like GitHub, this tab requires two setup steps, in order: an administrator connects the GitLab integration for the organization, and each user signs in with their own GitLab account. After you authorize access, the tab loads your merge requests, grouped by status. 


Prerequisites already cover the GitLab Source Code integration and webhook. Repeating them here is what drifted out of sync with the GitHub tab.

Suggested change

Like GitHub, this tab requires two setup steps, in order: an administrator connects the GitLab integration for the organization, and each user signs in with their own GitLab account. After you authorize access, the tab loads your merge requests, grouped by status.

After you sign in with your GitLab account, the tab loads your merge requests, grouped by status. For setup steps, see [GitLab Source Code][2].

domalessi · 2026-08-21T19:28:32Z

+- **Priority**
+- **Due**
+
+An administrator authorizes the Linear integration for the organization. After setup, Datadog detects your assigned issues, and they appear automatically. For setup steps, see [Linear][4]. 


Same as GitLab: keep setup in Prerequisites so these sections don't drift.

Suggested change

An administrator authorizes the Linear integration for the organization. After setup, Datadog detects your assigned issues, and they appear automatically. For setup steps, see [Linear][4].

After setup, your assigned issues appear automatically. For setup steps, see [Configure a Linear webhook][4].

domalessi · 2026-08-21T19:28:32Z

 - **Due**
 - **Assignee**

+An administrator configures the Jira integration and sets up a Jira webhook so that issue events reach Datadog. After setup, your assigned tickets appear automatically. For setup steps, see [Configure a Jira webhook][3].


Same trim as Linear so the two ticket tabs stay parallel.

Suggested change

An administrator configures the Jira integration and sets up a Jira webhook so that issue events reach Datadog. After setup, your assigned tickets appear automatically. For setup steps, see [Configure a Jira webhook][3].

After setup, your assigned tickets appear automatically. For setup steps, see [Configure a Jira webhook][3].

domalessi · 2026-08-21T19:28:32Z

 - **Assignee / Reviewer**  

-This section requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the section loads your pull requests, grouped by status. 
+This tab requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the tab loads your pull requests, grouped by status. 


Trimming this keeps the GitHub and GitLab tabs parallel. The permissions list and empty-state prompt below are still worth keeping; they aren't in Prerequisites.

Suggested change

This tab requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the tab loads your pull requests, grouped by status.

After you sign in with your GitHub account, the tab loads your pull requests, grouped by status.

domalessi · 2026-08-21T19:28:32Z

 - Checks: Read

-The section also requires a configured GitHub webhook so that pull request events reach Datadog in real time. For setup steps, see [GitHub][1]. 
+The tab also requires a configured GitHub webhook so that pull request events reach Datadog in real time. For setup steps, see [GitHub][1]. 


Delete this line. Webhook setup and the GitHub docs link are already in Prerequisites, and the empty-state sentence above already links the GitHub tile.

domalessi · 2026-08-21T19:28:33Z

 - **Assignee / Reviewer**  

-This section requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the section loads your pull requests, grouped by status. 
+This tab requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the tab loads your pull requests, grouped by status. 


If you keep these setup steps rather than trimming them as suggested on this paragraph, use a numbered list. Sequential steps shouldn't live in one sentence.

Suggested change

This tab requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the tab loads your pull requests, grouped by status.

The **GitHub** tab requires two setup steps:

1. An administrator connects the GitHub integration for the organization.

2. Each user signs in with their own GitHub account.

After you authorize access, the tab loads your pull requests, grouped by status.

domalessi · 2026-08-21T19:28:33Z

+- **Comment counts**, including resolved and unresolved discussion counts
+- **Age**, shown as the time since the last update
+
+Like GitHub, this tab requires two setup steps, in order: an administrator connects the GitLab integration for the organization, and each user signs in with their own GitLab account. After you authorize access, the tab loads your merge requests, grouped by status. 


Same as GitHub: if you keep these steps rather than trimming them, use a numbered list.

Suggested change

Like GitHub, this tab requires two setup steps, in order: an administrator connects the GitLab integration for the organization, and each user signs in with their own GitLab account. After you authorize access, the tab loads your merge requests, grouped by status.

The **GitLab** tab requires two setup steps:

1. An administrator connects the GitLab Source Code integration for the organization.

2. Each user signs in with their own GitLab account.

After you authorize access, the tab loads your merge requests, grouped by status.

domalessi · 2026-08-21T19:28:33Z

 ---

-{{< img src="tracing/software_catalog/idp_homepage.png" alt="IDP Homepage showing a personalized view of GitHub pull requests awaiting review and Jira tickets" style="width:100%;" >}} 
+{{< img src="tracing/software_catalog/idp_homepage.png" alt="IDP Homepage showing a personalized view of pull requests awaiting review and tickets" style="width:100%;" >}} 


Don't overwrite idp_homepage.png in place (same for services_entities_table.png). Add the new screenshots under new filenames and update the Markdown. See Update Image Repository.

domalessi · 2026-08-21T20:38:21Z

The new screenshots need to be added under new filenames, and you'll need to update the Markdown. More details here: https://datadoghq.atlassian.net/wiki/spaces/docs4docs/pages/1985314888/Screenshots+and+Videos#Update-Image-Repository.

domalessi · 2026-08-21T20:38:55Z

 ---
 title: Homepage
 site_support_id: idp
 description: The Internal Developer Portal Homepage gives you a centralized view of your team's entities, GitHub pull requests, Jira tickets, and Datadog Work Items in one place.


Should update to include GitLab and Linear

Updating IDP Homepage Docs

505c201

Added section for configuring homepage and updated with GitLab and Linear integrations

amlakhanpal requested a review from a team as a code owner August 21, 2026 16:35

Removing outdates homepage image

6ddc7cc

github-actions Bot added the Images Images are added/removed with this PR label Aug 21, 2026

amlakhanpal added 3 commits August 21, 2026 12:37

Adding image of "Your Tickets" section

3cf0521

Removing outdated services & entities image

2f884f3

Replacing services and entities table image

c1e1f66

amlakhanpal added 3 commits August 21, 2026 13:19

Replacing Homepage overview screenshot

d108513

Add PRs table image

3df8cd3

Updating mistake in GitLab section

765a107

domalessi self-assigned this Aug 21, 2026

domalessi reviewed Aug 21, 2026

View reviewed changes

Navigation Menu

Uh oh!

Updating IDP Homepage Docs - #39393

Updating IDP Homepage Docs#39393
amlakhanpal wants to merge 8 commits into
masterfrom
amlakhanpal/idp-homepage-docs

amlakhanpal commented Aug 21, 2026

Uh oh!

github-actions Bot commented Aug 21, 2026

Uh oh!

domalessi left a comment

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

domalessi Aug 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	Like GitHub, this tab requires two setup steps, in order: an administrator connects the GitLab integration for the organization, and each user signs in with their own GitLab account. After you authorize access, the tab loads your merge requests, grouped by status.
	After you sign in with your GitLab account, the tab loads your merge requests, grouped by status. For setup steps, see [GitLab Source Code][2].

	An administrator authorizes the Linear integration for the organization. After setup, Datadog detects your assigned issues, and they appear automatically. For setup steps, see [Linear][4].
	After setup, your assigned issues appear automatically. For setup steps, see [Configure a Linear webhook][4].

	An administrator configures the Jira integration and sets up a Jira webhook so that issue events reach Datadog. After setup, your assigned tickets appear automatically. For setup steps, see [Configure a Jira webhook][3].
	After setup, your assigned tickets appear automatically. For setup steps, see [Configure a Jira webhook][3].

	This tab requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the tab loads your pull requests, grouped by status.
	After you sign in with your GitHub account, the tab loads your pull requests, grouped by status.

-This tab requires two setup steps, in order: an administrator connects the GitHub integration for the organization, and each user signs in with their own GitHub account. After you authorize access, the tab loads your pull requests, grouped by status.
+The **GitHub** tab requires two setup steps:
+. An administrator connects the GitHub integration for the organization.
+. Each user signs in with their own GitHub account.
+After you authorize access, the tab loads your pull requests, grouped by status.

-Like GitHub, this tab requires two setup steps, in order: an administrator connects the GitLab integration for the organization, and each user signs in with their own GitLab account. After you authorize access, the tab loads your merge requests, grouped by status.
+The **GitLab** tab requires two setup steps:
+. An administrator connects the GitLab Source Code integration for the organization.
+. Each user signs in with their own GitLab account.
+After you authorize access, the tab loads your merge requests, grouped by status.

Uh oh!

Conversation

amlakhanpal commented Aug 21, 2026

What does this PR do? What is the motivation?

Merge readiness

For Datadog employees:

AI assistance

Additional notes

Uh oh!

github-actions Bot commented Aug 21, 2026

Preview links (active after the build_preview check completes)

Modified Files

Uh oh!

domalessi left a comment

Choose a reason for hiding this comment

Prerequisites

How much UI to document

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Preview links (active after the `build_preview` check completes)