Skip to content
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

Update Description column in "Publish a Microsoft Edge extension" #3330

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

bhuvanapriyap
Copy link
Contributor

@bhuvanapriyap bhuvanapriyap commented Dec 17, 2024

Rendered article section for review:

AB#55532841

@mikehoffms mikehoffms added the cat: extensions Extensions-related content. label Dec 17, 2024
@mikehoffms mikehoffms changed the title Update publish-extension.md Update Description column in "Publish a Microsoft Edge extension" Dec 17, 2024
Copy link

| Property name | Required? | Description |
|---|---|---|
| **Display name** | Required for at least one language | The `name` of your extension specified in the manifest file of your extension. To change the store display name after submission, you can update the name in the manifest file, create a new extension package, and then re-upload it. |
| **Description** | Required for each language | The `description` field explains what your extension does, why users should install it, and any other relevant information users need to know. <br/>* **Length:** Minimum 250 characters, maximum 5000 characters. <br/>* **Clarity:** Must clearly describe the full functionality of your extension. <br/>* **Completeness:** Should be thorough and should leave no important details out. <br/>* **Appropriateness:** Must not contain any misleading or inappropriate content. |
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
| **Description** | Required for each language | The `description` field explains what your extension does, why users should install it, and any other relevant information users need to know. <br/>* **Length:** Minimum 250 characters, maximum 5000 characters. <br/>* **Clarity:** Must clearly describe the full functionality of your extension. <br/>* **Completeness:** Should be thorough and should leave no important details out. <br/>* **Appropriateness:** Must not contain any misleading or inappropriate content. |
| **Description** | Required for each language | The `description` field explains what your extension does, why users should install it, and any other relevant information users need to know. <br/>* **Length:** Minimum 250 characters, maximum 5000 characters. <br/>* **Clarity:** Must clearly describe the full functionality of your extension. <br/>* **Completeness:** Should be thorough and include all important details. <br/>* **Appropriateness:** Must not contain any misleading or inappropriate content. |

Copy link
Collaborator

Choose a reason for hiding this comment

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

changed locally

Copy link
Collaborator

Choose a reason for hiding this comment

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

(the change was entered w/ my other account, not this main account)



<!-- ========================================================================== -->
## Step 3: Provide Availability details
## Step 3: Provide Availability details
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
## Step 3: Provide Availability details
## Step 3: Provide availability details

Copy link
Collaborator

Choose a reason for hiding this comment

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

lowercased 2x

1. Complete your submission.
* [Step 1: Start a new submission](#step-1-start-a-new-submission).
* [Step 2: Upload the extension package](#step-2-upload-the-extension-package).
* [Step 3: Provide Availability details](#step-3-provide-availability-details).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* [Step 3: Provide Availability details](#step-3-provide-availability-details).
* [Step 3: Provide availability details](#step-3-provide-availability-details).

Copy link
Collaborator

@mikehoffms mikehoffms Jan 8, 2025

Choose a reason for hiding this comment

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

lowercased locally 2x

Copy link
Collaborator

Choose a reason for hiding this comment

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

@bhuvanapriyap could simply use this page of the PR, click "Add single comment" - or batch (click Add To Batch on each PR Comment) and remember to submit the batch and don't leave this page until done. b/c all comments are simply Suggestion comments. so don't need to use local VS Code.

@captainbrosset - i fixed locally all Comments, but I can't push commit to fix all these Comments yet until I'm added as Collaborator on Bhuvana's fork of edge-dev repo.

* [Step 1: Start a new submission](#step-1-start-a-new-submission).
* [Step 2: Upload the extension package](#step-2-upload-the-extension-package).
* [Step 3: Provide Availability details](#step-3-provide-availability-details).
* [Step 4: Enter Properties describing your extension](#step-4-enter-properties-describing-your-extension).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* [Step 4: Enter Properties describing your extension](#step-4-enter-properties-describing-your-extension).
* [Step 4: Enter properties describing your extension](#step-4-enter-properties-describing-your-extension).

Copy link
Collaborator

@mikehoffms mikehoffms Jan 8, 2025

Choose a reason for hiding this comment

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

lowercased locally 2x

* [Step 2: Upload the extension package](#step-2-upload-the-extension-package).
* [Step 3: Provide Availability details](#step-3-provide-availability-details).
* [Step 4: Enter Properties describing your extension](#step-4-enter-properties-describing-your-extension).
* [Step 5: Add Store listing details for your extension](#step-5-add-store-listing-details-for-your-extension).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* [Step 5: Add Store listing details for your extension](#step-5-add-store-listing-details-for-your-extension).
* [Step 5: Add store listing details for your extension](#step-5-add-store-listing-details-for-your-extension).

Copy link
Collaborator

Choose a reason for hiding this comment

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

lowercased locally 2x



<!-- ========================================================================== -->
## Step 4: Select Properties for your extension
## Step 4: Enter Properties describing your extension
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
## Step 4: Enter Properties describing your extension
## Step 4: Enter properties describing your extension

Copy link
Collaborator

Choose a reason for hiding this comment

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

lowercased 2x

![Store listing section for an extension](./publish-extension-images/store-listing-section-for-extension.png)


The information provided in the **Store listings** page is displayed to users who view your listing on the Microsoft Edge Add-ons website. Even though some fields are optional, you should provide as much information as possible.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The information provided in the **Store listings** page is displayed to users who view your listing on the Microsoft Edge Add-ons website. Even though some fields are optional, you should provide as much information as possible.
The information provided in the **Store Listings** page is displayed to users who view your listing on the Microsoft Edge Add-ons website. Even though some fields are optional, you should provide as much information as possible.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

inconsistent ui at P. C.:
left nav: listings
top of page: Listings.
@captainbrosset - a UI bug. trends in several companies would go w/ lowercase for the page title.
Changed all 2 instances to uppercase L. That's ok b/c they are not specifically saying "click the words x in the left nav."

Copy link
Collaborator

@mikehoffms mikehoffms left a comment

Choose a reason for hiding this comment

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

LGTM - Content Developer

@Lakshmisha-KS
Copy link

#Sign-off

Reviewed and this should be fine

Incorp rvw comments in PR 3330 (Update Description column in "Publish a Microsoft Edge extension")
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cat: extensions Extensions-related content.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants