Skip to content

Site Overview: Add manage dns to domain card #105105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

arthur791004
Copy link
Contributor

Part of DOTDASH-250

Proposed Changes

  • Implement Manage DNS action to the domain dataviews on domain card

Why are these changes being made?

Testing Instructions

  • Go to /v2/sites/:site on your site with custom domain
  • Click the ... on the custom domain on the domain card
  • Click Manage DNS
  • Ensure it opens the Manage DNS page

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
    • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

@arthur791004 arthur791004 marked this pull request as ready for review August 7, 2025 12:03
@arthur791004 arthur791004 requested a review from a team as a code owner August 7, 2025 12:03
@matticbot matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Aug 7, 2025
@arthur791004 arthur791004 self-assigned this Aug 7, 2025
Copy link

github-actions bot commented Aug 7, 2025

@matticbot
Copy link
Contributor

matticbot commented Aug 7, 2025

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

  • help-center
  • notifications
  • wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug DOTDASH-250/domains-card-manage-dns on your sandbox.

@matticbot
Copy link
Contributor

matticbot commented Aug 7, 2025

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~168 bytes added 📈 [gzipped])

name                    parsed_size           gzip_size
entry-dashboard-dotcom       +149 B  (+0.0%)      +83 B  (+0.0%)
entry-dashboard-a4a          +149 B  (+0.0%)      +81 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Sections (~185 bytes added 📈 [gzipped])

name                parsed_size           gzip_size
sites-dashboard          +149 B  (+0.0%)      +91 B  (+0.0%)
site-settings            +149 B  (+0.0%)      +94 B  (+0.0%)
site-performance         +149 B  (+0.0%)      +91 B  (+0.0%)
site-monitoring          +149 B  (+0.0%)      +91 B  (+0.0%)
site-logs                +149 B  (+0.0%)      +91 B  (+0.0%)
overview                 +149 B  (+0.0%)      +91 B  (+0.0%)
hosting                  +149 B  (+0.0%)      +91 B  (+0.0%)
github-deployments       +149 B  (+0.0%)      +91 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~91 bytes added 📈 [gzipped])

name                       parsed_size           gzip_size
async-load-v-2-sites-list       +149 B  (+0.1%)      +91 B  (+0.1%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

@arthur791004 arthur791004 force-pushed the DOTDASH-250/domains-card-manage-dns branch from 119c101 to a4e2add Compare August 7, 2025 12:33
Copy link
Contributor

@fushar fushar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested both primary and non-primary domains 👍

@@ -63,8 +69,18 @@ export const useActions = ( { user, site }: { user: User; site?: Site } ) => {
id: 'manage-dns-settings',
label: __( 'Manage DNS' ),
supportsBulk: false,
callback: () => {},
isEligible: () => false,
callback: ( items: Domain[] ) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: we don't need the types :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants