Publish the Extension
Before we can publish, we need to zip up the folder containing the files to be published. We also need to create screenshots that will be displayed on the Chrome Web Store page.
Last updated
Before we can publish, we need to zip up the folder containing the files to be published. We also need to create screenshots that will be displayed on the Chrome Web Store page.
Last updated
We must set up an account and access the Chrome Web Store Developer Dashboard to publish an extension.
We need to prepare some Graphic Assets:
The store icon should be 128x128 pixels and located in the Zip file. The icon should be 96x96 with 16 transparent pixels per side. It must be in PNG format. It should look OK in light an dark backgrounds. It will appear next to the Chrome address bar with other Chrome Extension icons.
You can optionally include a video by supplying a link that will be posted on the Store website.
Provide at least one and up to five screenshots that will be displayed with the store listing. These must be 1280x800 or 640x400. The format must be JPEG or 24-bit PNG.
A small promo title image that is 480x280 with a JPEG or 24-bit PNG format.
A marquee promo file that is 1400x560 with a JPEG or 24-bit PNG format.
The folder that is zipped for Link Reveal looks like this:
There are a couple of files that have not been discussed yet. The index.html renders a web page containing a lot of different variations on links to test with. The nolinks.html contains no links. When there are no links on the user's web page, a message will appear indicating that no links were found and that a page refresh might help. This is because some pages get put to sleep, and if the user returns to a page, the refresh will help make it available for injections. There are two markdown files: README and a PrivacyPolicy. The README contains notes on the application. The PrivacyPolicy will be served from github.io, and the link will be supplied to Google via the publishing process.
Questions arise about the security and permissions required by the extension. Because it requests access to all URLs, there is a security policy. The extension is stored in the GitHub repository that holds the code and is rendered with GitHub pages. The link is shared in the Privacy section of the publishing process. When the extension is submitted, it will be reviewed, and more requirements may be asked for.
The contents of the security policy are shown below:
When we click the New Item button, we're prompted to upload the zip file containing the extension code.
Once the code is uploaded, we provide information for the store listing and share privacy considerations.
Note that if we change the extension code or configuration, we need to update the version in the manifest file and then click Package on the left menu to upload a new zip file.
