Restructures and expands 'Publish to SPFx marketplace' docs (SharePoint#5946)

* Restructures and expands 'Publish to SPFx marketplace' docs

* Updates to address review feedback

Author: waldekmastykarz

docs/spfx/publish-to-marketplace-after-publishing.md

@@ -0,0 +1,36 @@
+---
+title: Maintain and support your published app
+description: Tips to maintain and support your SharePoint Framework app after publishing it to the marketplace
+ms.date: 06/25/2020
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# Maintain and support your published app
+
+Publishing the application to the marketplace is just the first step in helping users solve their business problem. Following sections contain some tips that you should consider after publishing your application to the marketplace.
+
+## Install applications from the marketplace in the tenant app catalog
+
+SharePoint Online allows you to create a tenant app catalog where you centrally manage applications available in your organization. Additionally, you can create site collection app catalogs, where you can deploy applications to specific sites.
+
+Applications that you acquire from the marketplace, you can install only in tenant app catalogs. After installing the application, you can decide whether you want to deploy it globally and make it available to all sites in your tenant or if you want to deploy it only to specific sites.
+
+For more information about managing SharePoint Framework solution in the app catalog visit: [https://docs.microsoft.com/sharepoint/use-app-catalog](https://docs.microsoft.com/sharepoint/use-app-catalog) and [https://docs.microsoft.com/sharepoint/dev/general-development/site-collection-app-catalog](https://docs.microsoft.com/sharepoint/dev/general-development/site-collection-app-catalog).
+
+## Permissions required to install applications from the marketplace
+
+By default, only tenant administrators can install applications from the marketplace. They can however choose to delegate the responsibility to others in your organization by granting them access to the tenant app catalog.
+
+SharePoint Framework applications execute on behalf of the current user and can do whatever the current user can do. Because of this, only tenant app catalog administrators can install applications from the marketplace. Users who are not app catalog administrators can request a specific application to be installed by the app catalog administrator, but they cannot install the application themselves.
+
+## Notify users of new versions
+
+As you update your application, you should notify your users when an updated version is available. The marketplace does not offer any version checking mechanism and you should implement it your application so that notifications are meaningful and as unobtrusive as possible. In your code you can for example call a custom API that you own to compare the current version of the application with the latest version available.
+
+Tenant app catalog administrators can update applications acquired from the marketplace directly from the app catalog, by selecting the application in the app catalog and from the ribbon choosing the **Upgrade Store App** option. When the upgrade succeeds, the latest version will be automatically visible to users in all sites where the application has been installed.
+
+## Applications listed in the SharePoint category
+
+All SharePoint Framework applications published in the marketplace are listed in the **SharePoint** category. At this moment, it is not possible to specify a custom category. Also, even if you configured web parts in your application to be exposed in Microsoft Teams, the application will still be listed in the **SharePoint** category.
+

docs/spfx/publish-to-marketplace-checklist.md

@@ -0,0 +1,181 @@
+---
+title: Prepare your SharePoint Framework application for publishing to the marketplace
+description: Tips & tricks to help you get your SharePoint Framework application published in the marketplace
+ms.date: 06/25/2020
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# Prepare your SharePoint Framework application for publishing to the marketplace
+
+Before a SharePoint Framework application is published in the marketplace, it must go through an approval process. This process is executed free of charge by Microsoft and is meant to ensure that your app functions properly and that its page clearly describes its purpose and features. To help you get your application published in the marketplace, following is the list of tests executed as a part of the approval process.
+
+## Prerequisites
+
+### Use SharePoint Framework v1.11 or newer
+
+To build solutions that you want to publish to the marketplace, you need to use SharePoint Framework v1.11 or higher. Starting from version 1.11, SharePoint Framework solution manifest has additional information about your organization and solution, which is required for publishing your application in the marketplace.
+
+> [!TIP]
+> If your application is built using an older version of the SharePoint Framework, you can easily upgrade it to SharePoint Framework v1.11 or newer using Office 365 CLI. For more information, visit [https://pnp.github.io/office365-cli/cmd/spfx/project/project-upgrade/](https://pnp.github.io/office365-cli/cmd/spfx/project/project-upgrade/).
+
+### Test application in both root and non-root sites
+
+When testing your application, verify that it's working as intended when installed both in the root site collection of a tenant as well as non-root sites. This will help you verify that it doesn't have any dependencies on specific site URLs.
+
+### Test application in the required browsers
+
+When testing your application against checks described in the following section, verify that it works as expected at least on Windows 10 in the latest versions of Microsoft Edge, Google Chrome, Firefox and Microsoft Teams Desktop client (if your application exposes web parts in Teams).
+
+## Required checks
+
+Following checks must be passed. If one or more checks from this category failed, your application will be rejected and you will be instructed to fix the reported issues.
+
+### Under normal circumstances solution should work as intended
+
+Under normal circumstances, all components (web parts and extensions) in your solution should work as intended. Preferably, before submitting your application for approval, you should verify that it's working as expected on multiple tenants and using different user accounts to ensure that it doesn't depend on any specific configuration. If your solution requires specific settings, mention it explicitly in your solution's description.
+
+### Web part should work in all hosts in which its exposed
+
+When building web parts using SharePoint Framework, you can choose [where they should be exposed](integrate-with-teams-introduction.md). Before submitting you application for review, ensure that your web part works as intended in all these hosts.
+
+### Solution package must contain valid developer metadata
+
+In the solution's manifest (managed in the `package-solution.json` file) there is a new section named `developer` with the following properties:
+
+Attribute|Description|Mandatory
+---|---|---
+`name`|Name of the organization that built the application|Yes
+`websiteUrl`|URL of a website with additional information about the application|Yes
+`mpnId`|Microsoft Partner Network ID (more details on [MS Partner Network](https://docs.microsoft.com/partner-center/mpn-overview))|No (but highly recommended to provide it)
+`privacyUrl`|Privacy statement URL|Yes
+`termOfUseUrl`|Terms of use URL|Yes
+
+Including this additional information allows you to clearly communicate information about your application towards your users and in the future should allow you to access additional usage data.
+
+The developer information is displayed when installing web parts in Microsoft Teams. Information about the application and the developer that is displayed in the marketplace is managed separately in the marketplace.
+
+### Web part metadata description text must briefly describe its functionality and value proposition
+
+Ensure that your web part's description in the metadata is meaningful so that users understand what is your web part's purpose and what they can expect of it.
+
+### Solution's description must clearly describe the different components included in the package
+
+When submitting your package to the marketplace, be sure to clearly describe what different component (web parts, application customizers, etc.) are included in the package to manage user expectations and help them understand the impact of using your application.
+
+### Don't use names of features in Teams and SharePoint in your solution's name
+
+In your solution name don't use words matching features in Microsoft Teams or SharePoint, such as **Chat**, **Contacts**, **Calendar**, **Calls**, **Files**, **Meeting**, **Activity**, **Teams**, **Apps**, **Help**, **SharePoint**, **List**, **Page**, etc. as these names could be confused with the standard functionality in Teams and SharePoint.
+
+### Don't use names of other Microsoft's products in your solution's name
+
+Your solution will be rejected if its name contains a name of another Microsoft product, such as **Outlook**, **Word**, **Calendar**, **Tasks**, **Teams**, **Excel**, **PowerPoint**, **Visio**, etc.
+
+### Don't use keywords that are related to Microsoft's products
+
+Your solution must not use Microsoft Teams or SharePoint feature-specific keywords like - **Start meeting**, **Make call**, **Upload file**, **Start chat**, etc. These keywords are used in Microsoft's products and using them in your application could confuse users. If your application offers similar functionality, include the name of your name in the action, eg: **Start a Zoom Meeting**, **Upload file to Dropbox**, **Start Freshdesk chat**, etc.
+
+### Naming your solution
+
+If your solution is named after a common word, such as **Orders**, you will need to include your company name as well to clearly differentiate it from other solutions in the marketplace, eg. **Contoso Orders**.
+
+### Don't include additional advertising in your app's description and screenshots
+
+Make sure that your app's description, screenshots, text, and promotional images, describe only the app and don't contain any additional advertising.
+
+### All properties exposed in the property pane should be functional
+
+Properties exposed in the property pane of your web part should be meaningful. Changing their settings, should clearly change the behavior of your web part.
+
+### Verify that the package file can be uploaded to App catalog without errors
+
+Verify that the solution package can be uploaded to the App catalog in your tenant without any errors.
+
+### Verify that the app can be deployed without errors
+
+Verify that your application can be installed in a specific site but also that it can be deployed globally to all sites without any errors.
+
+### Provide justification for any API requests
+
+If your application requires additional API access (for example to communicate with Microsoft Graph), it should request them in the solution manifest. Additionally, prepare justification for the requested API access as we might ask for it when reviewing your app.
+
+### All URLs displayed in the web part must be working
+
+If your web part shows URLs, they must be pointing to existing resources and must not lead to non-existent or error pages.
+
+### Application doesn't stop responding
+
+When using your application, it shouldn't stop responding to users. If it needs to perform an operation that could take a moment to complete, it communicates this to the user.
+
+### Is the solution complete
+
+Does your solution contain all functionality as advertised in its description and screenshots?
+
+### Is the application's UI finished
+
+The first impression users will have of your application will be by looking at its UI. If it doesn't look polished, if some elements are misaligned, it uses many different fonts or some placeholder text has not been replaced by its final value, it could give them an impression that your application isn't finished and that they shouldn't use it.
+
+> [!TIP]
+> To ensure seamless integration with SharePoint and Teams, we recommend that you use Office UI Fabric which is the design language for Microsoft 365. For more information, see the [design](../design/design-guidance-overview.md) section of this documentation.
+
+### Application shouldn't prompt users without explicit interaction
+
+Your application shouldn't prompt users without explicit interaction on their part.
+
+### Verify that browsers don't block your pop-ups
+
+If your application uses pop-ups, verify, that browsers with default settings don't block them interrupting the user flow.
+
+### Correct first-launch experience
+
+If possible, your application should work when launched for the first time. If it must be configured first, clearly communicate next steps to the user. If the configuration is complex or requires additional information, provide clear instructions to help users setup your application.
+
+### Test syncing to Teams
+
+If your application contains web parts that are exposed as Teams tabs or personal apps, verify that they can be deployed to teams using the **Sync to Teams** option in the App catalog without any errors. After syncing the configuration to Teams, verify that all web parts are exposed in the Teams' app catalog as intended, can be installed and work as expected.
+
+### Verify that links with additional information are correct
+
+Verify, that links such as **Terms of Service**, **Privacy Policy**, **About**, etc. are valid and point to correct pages.
+
+### Acquire account or license
+
+If your solution requires users to acquire an account or a license, is it clear how they can do it and how they can use the obtained information with your application?
+
+### No demo content if free trial is included in the offering
+
+If your offering includes a free trial of your application, then your application shouldn't include any demo content.
+
+### Don't include malicious code
+
+Solutions that contain malicious code, links to malicious websites or otherwise illegal resources will be rejected from publishing in the marketplace.
+
+### Don't include vulnerable resource
+
+Verify, that your code doesn't contain any vulnerabilities. If you're using third-party dependencies
+
+### Ensure that your application doesn't use resources excessively
+
+When testing your application, verify that it doesn't lead to noticeable or sustained increase in CPU usage, that it doesn't consume a lot of memory an that it doesn't lead to the browser becoming unresponsive. In general, your application should run well on an average desktop computer with internet access. Also, it shouldn't take longer than 10 seconds for your application to load.
+
+## Recommended checks
+
+Following checks are recommended to pass. While a failed check in this category won't prevent you from publishing your application in the marketplace, it might have a negative impact on end-user experience.
+
+### Web part icon should be 64x64px with transparent background
+
+We recommend that you use a 64x64px image with transparent background for your web part's icon. This will allow it to be correctly displayed in the different UI modes in SharePoint.
+
+### Web part should have a title that's configurable in the property pane
+
+We recommend that all web parts have a title that clearly describes the information the web part presents. Page authors should be able to adjust this title through property pane, so that if the web part is configurable, the title can correctly describe its contents.
+
+> [!TIP]
+> You can easily add a configurable title to your web part by using the [WebPartTitle](https://pnp.github.io/sp-dev-fx-controls-react/controls/WebPartTitle/) PnP Reusable React control.
+
+### Properly handle different themes
+
+Your application should properly handle light- and dark-color themes. Switching between the different themes shouldn't have a negative effect on the usability of your application. While not supporting themes will not prevent you from publishing your app in the marketplace, it's strongly recommended that you support them to offer optimal user experience.
+
+> [!TIP]
+> For more information about using themes in your application, see the [Use theme colors in your SharePoint Framework customizations](use-theme-colors-in-your-customizations.md) article.

docs/spfx/publish-to-marketplace-faq.md

@@ -0,0 +1,35 @@
+---
+title: Publish SharePoint Framework applications to the marketplace - FAQ
+description: Frequently asked questions about publishing SharePoint Framework applications to the marketplace
+ms.date: 06/25/2020
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# Publish SharePoint Framework applications to the marketplace - FAQ
+
+Following are some of the most frequently asked questions regarding publishing SharePoint Framework applications to the marketplace.
+
+## Is it required to configure web parts to be isolated for publishing in the marketplace
+
+No, it is not required to configure web parts to be isolated. It is fully up to you to decide if your web parts should be isolated or not and you can use either mode in the application you publish to the marketplace.
+
+## Can I request additional API permissions for my solution
+
+Yes, if your solution needs additional API permissions to work as intended, then you should request these permissions to be granted in your solution’s manifest. Please note, that the marketplace verification team could ask you to justify access to the permissions that you have requested when verifying your submission.
+
+## Can I expose my web parts in Office add-ins
+
+At this moment exposing SharePoint Framework web parts in Office add-ins is in preview and is not yet supported in solutions published in the marketplace.
+
+## Can I include library components in my solution
+
+Yes, library components are fully supported in solutions published to the marketplace.
+
+## Can I use a custom Microsoft Teams manifest
+
+When building SharePoint Framework web parts, you can choose to [expose them in SharePoint and Microsoft Teams as personal apps or tabs](https://docs.microsoft.com/sharepoint/dev/spfx/integrate-with-teams-introduction). To use your web parts in Teams you can either generate the manifest and the Teams solution package yourself or have the SharePoint Framework generate it for you. Creating the manifest manually gives you more flexibility and allows you to create multi-tab personal apps.
+
+At this moment, the marketplace does not support embedding custom Teams manifests in SharePoint Framework packages. You can expose your web parts in Teams using the manifest auto-generated by SharePoint Framework.
+
+If your web part requires configuration and you expose it as a personal Teams app, you need to implement a custom UI yourself to allow users to configure it.

docs/spfx/publish-to-marketplace-overview.md

@@ -0,0 +1,15 @@
+---
+title: Publish SharePoint Framework applications to the marketplace
+description: Considerations for publishing SharePoint Framework applications to the marketplace
+ms.date: 06/25/2020
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# Publish SharePoint Framework applications to the marketplace
+
+Publishing your SharePoint Framework solutions to [marketplace (also known as AppSource)](https://appsource.microsoft.com/) allows you to reach other organizations and let them easily install your application in their Microsoft 365 tenant. Following sections describe considerations that you should take into account before publishing your solutions to the marketplace.
+
+* [App validation checklist](publish-to-marketplace-checklist.md)
+* [After publishing your app](publish-to-marketplace-after-publishing.md)
+* [Frequently asked questions](publish-to-marketplace-faq.md)