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

Extensions landing page #3265

Merged
merged 17 commits into from
Sep 17, 2024
Merged

Conversation

mikehoffms
Copy link
Contributor

@mikehoffms mikehoffms commented Sep 11, 2024

Rendered landing page for review:

To force-load the revised TOC:
F12 > right-click "Refresh" > "Empty cache and hard refresh" > F12
Open different branches in different windows.

This PR makes the following changes:

  • Added a landing page for Extensions, as a destination that's not a particular article; represents whole set of articles as a URL to give to users.
  • Modified the TOC, so that bucket names use concrete keywords that match article title keywords:
    • Broke out the "Publish an extension" toc bucket into "Register as an extension developer" and "Publish an extension".
      • Helps group Publish articles, and supports structuring the relation (future toc design) of those articles.
    • Broke out the "Manage and maintain an extension" toc bucket into "Update an extension" and "Analytics and user reviews"
      • To surface the key words of the contained articles' titles, instead of abstract synonyms.
      • Matches scope of landing page cards of uniform length / article-count.
  • Changed title from:
    Automatically update an extension in Microsoft Edge
    to:
    Set an extension to automatically update
    • Partly improves lead-in summary flow in that article.

AB#53967047

@mikehoffms mikehoffms added cat: extensions Extensions-related content. in-progress labels Sep 11, 2024
microsoft-edge/toc.yml Outdated Show resolved Hide resolved
microsoft-edge/toc.yml Outdated Show resolved Hide resolved
@mikehoffms mikehoffms marked this pull request as ready for review September 13, 2024 17:00
Copy link

Learn Build status updates of commit 21d9b11:

✅ Validation status: passed

File Status Preview URL Details
microsoft-edge/extensions-chromium/index.md ✅Succeeded View
microsoft-edge/extensions-chromium/landing/index.yml ✅Succeeded View
microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md ✅Succeeded View
microsoft-edge/extensions-chromium/publish/api/using-addons-api.md ✅Succeeded View
microsoft-edge/extensions-chromium/publish/auto-update.md ✅Succeeded View
microsoft-edge/toc.yml ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

Copy link
Contributor

@captainbrosset captainbrosset left a comment

Choose a reason for hiding this comment

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

I don't have comments about the landing page itself, which I think is great.
It's very useful to have a landing page that we can link users to, as an entry point to the extensions docs.
I did leave a couple of comments about other changes.

Copy link

Learn Build status updates of commit 5b4ed24:

✅ Validation status: passed

File Status Preview URL Details
microsoft-edge/extensions-chromium/index.md ✅Succeeded View
microsoft-edge/extensions-chromium/landing/index.yml ✅Succeeded View
microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md ✅Succeeded View
microsoft-edge/extensions-chromium/publish/api/using-addons-api.md ✅Succeeded View
microsoft-edge/extensions-chromium/publish/auto-update.md ✅Succeeded View
microsoft-edge/toc.yml ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@captainbrosset captainbrosset merged commit d095db0 into main Sep 17, 2024
2 checks passed
@captainbrosset captainbrosset deleted the user/mikehoffms/extensions-landing branch September 17, 2024 22:33
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.

2 participants