#7180711 Site Settings: refactor and update support links

Sent to vendor

Created on March 14, 2022 , translate by Sunday, March 20, 2022 (810 days ago)

Translate 2 originals (3 words) to Romanian Glossary

Prio	Original string	Translation	—
	{{span}}Portfolio projects{{/span}}	{{span}}Proiecte de portofoliu{{/span}}	Details
{{span}}Portfolio projects{{/span}} {{span}}Portfolio projects{{/span}} {{span}}Proiecte de portofoliu{{/span}} {{span}}Proiecte de portofoliu{{/span}} You have to log in to edit this translation. or Cancel Translation Memory Loading… Meta Status: current Date added: 2022-03-15 08:06:45 GMT Translated by: Dan Caragea (dancarageact62) Priority: normal More links: Permalink to this translation All translations of this original Show all translations across locales Show original across locales Show all deliverables with this original (ro) Show all deliverables with this original (overview) View deliverable: Site Settings: refactor and update support links
	{{span}}Testimonials{{/span}}	{{span}}Testimoniale{{/span}}	Details
{{span}}Testimonials{{/span}} {{span}}Testimonials{{/span}} {{span}}Testimoniale{{/span}} {{span}}Testimoniale{{/span}} You have to log in to edit this translation. or Cancel Translation Memory Loading… Meta Status: current Date added: 2022-03-15 08:06:12 GMT Translated by: Dan Caragea (dancarageact62) Priority: normal More links: Permalink to this translation All translations of this original Show all translations across locales Show original across locales Show all deliverables with this original (ro) Show all deliverables with this original (overview) View deliverable: Site Settings: refactor and update support links

Legend:

Current

Waiting

Fuzzy

Old

With warnings

Export strings as

Description

Changes proposed in this Pull Request

This started out as a simple PR to update the links to the support guide links and during the process, I decided to refactor a few things and make it a little cleaner and more uniform. Here are the major changes I made:

Main Index

Moved section headings within the appropriate components
Removed unused props
Added siteIsAutomatedTransfer prop to the sections that needed to provide the different support links based on that context.

Composing section

Removed unnecessary connect to the store
Removed unused props
Added section header
Changed Latex and Shortcodes components from class components to functions
Updated support links

Content Types

Extrapolated each fieldset into a component BlogPosts, Testimonials, and Portfolios.
I tried to convert the index from a class to a function but was not successful with the autosave/update feature so I left this as a class.
Updated support links

Masterbar (only in self-hosted Jetpack sites)

Added section header

Media (only in self-hosted Jetpack sites)

Added section header

Publishing Tools

Updated support links
Replaced the generic HTML elements with the standardized Form components to make things consistent
Adjusted section header

Theme Enhancements

Changed from class to function component
Removed unused props
Updated support links

Widgets

Removed unused props
Changed from class to function component

Testing instructions

Pull branch and launch calypso with yarn start
Go to Settings ⇢ Writing
Adjust all settings and options and verify they update correctly
Visually inspect for errors (there are slight variations due to the update to match styling)
Click the ( i ) and make sure the link goes to Jetpack links on JPOP only sites and WPCOM for Simple and AT sites
Repeat this process with each version – Simple, AT, and JPOP site
I tested side-by-side with the live version. After a change in my test environment, I would refresh my live version to make sure the changes applied to the site settings.

Fixes #59977

Unfortunately, no screenshots were provided by the developer.

Show less Show more | Github Pull request