Merge pull request #26 from pulsar-edit/fix-broken-links

Change all registry URLs (and fix a broken link)

Author: savetheclocktower

docs/core-packages-and-features/autocomplete.md

@@ -20,4 +20,4 @@ The autocompletion interface is implemented in the {autocomplete-plus} package.
 * The core {autocomplete-css} package suggests tag names, CSS property names, and contextually relevant values for properties.
 * The core {autocomplete-snippets} package suggests snippets whose prefixes match what has already been typed in the current word.
 
-Community packages — in particular [packages that wrap language servers](/ide-features/) — can also act as “brains” for autocompletion. Pulsar’s package registry can show you [a list of packages](https://web.pulsar-edit.dev/packages?serviceType=provided&service=autocomplete.provider) that can supply data to `autocomplete-plus`.
+Community packages — in particular [packages that wrap language servers](/ide-features/) — can also act as “brains” for autocompletion. Pulsar’s package registry can show you [a list of packages](https://packages.pulsar-edit.dev/packages?serviceType=provided&service=autocomplete.provider) that can supply data to `autocomplete-plus`.

docs/developing-for-pulsar/developing-a-package.md

@@ -14,7 +14,7 @@ You can run the generator by invoking the command palette and searching for "Gen
 ::: note Note
 
 You may encounter a situation where your package is not loaded.
-Make sure the package name you choose isn’t an existing bundled package name or one hosted on [pulsar-edit.dev](https://web.pulsar-edit.dev/packages).
+Make sure the package name you choose isn’t an existing bundled package name or one hosted on [pulsar-edit.dev](https://packages.pulsar-edit.dev/packages).
 
 :::
 

docs/developing-for-pulsar/developing-a-theme.md

@@ -23,7 +23,7 @@ Themes are pretty straightforward, but it’s still helpful to be familiar with
 - Your theme’s `package.json` must contain a `theme` key with a value of `ui`
   or `syntax` for Pulsar to recognize and load it as a theme.
 - You can find existing themes to install or fork in
-  [Pulsar Package Repository](https://web.pulsar-edit.dev/packages). <!--TODO: Update to a themes URL if we get one on the front end site-->
+  [Pulsar Package Registry](https://packages.pulsar-edit.dev/packages). <!--TODO: Update to a themes URL if we get one on the front end site-->
 
 ## Creating a syntax theme
 

docs/developing-for-pulsar/maintaining-your-package.md

@@ -18,7 +18,7 @@ Some people prefer to control every aspect of the package publishing process. No
 
 ::: note Note
 
-The `ppm` tool will only publish and [Pulsar Package Registry](https://web.pulsar-edit.dev) will only list packages that are hosted on [GitHub](https://github.com), regardless of what process is used to publish them.
+The `ppm` tool will only publish and [Pulsar Package Registry](https://packages.pulsar-edit.dev) will only list packages that are hosted on [GitHub](https://github.com), regardless of what process is used to publish them.
 
 :::
 
@@ -56,7 +56,7 @@ The name of your package will be reserved even after being unpublished!
 
 :::
 
-If you no longer want to support your package and cannot find anyone to take it over, you can unpublish your package from [Pulsar Package Registry](https://web.pulsar-edit.dev). For example, if your package is named `package-name`, you’d run:
+If you no longer want to support your package and cannot find anyone to take it over, you can unpublish your package from [Pulsar Package Registry](https://packages.pulsar-edit.dev). For example, if your package is named `package-name`, you’d run:
 
 ```sh
 $ pulsar -p unpublish package-name

docs/developing-for-pulsar/publishing.md

@@ -25,15 +25,15 @@ There are a few things you should double check before publishing:
 
 ## Publish your package
 
-Before you publish a package it is a good idea to check ahead of time if a package with the same name has already been published to [the Pulsar Package Repository](https://web.pulsar-edit.dev/packages). You can do that by visiting `https://web.pulsar-edit.dev/packages/your-package-name` to see if the package already exists. If it does, update your package’s name to something that is available before proceeding.
+Before you publish a package, it’s a good idea to check ahead of time if a package with the same name has already been published to [the Pulsar Package Registry](https://packages.pulsar-edit.dev/packages). You can do that by visiting `https://packages.pulsar-edit.dev/packages/your-package-name` to see if the package already exists. If it does, update your package’s name to something that is available before proceeding.
 
 Now let’s review what the `pulsar -p publish` command does:
 
-1. Registers the package name on Pulsar Package Repository if it is being published for the first time.
+1. Registers the package name on Pulsar Package Registry if it is being published for the first time.
 2. Updates the `version` field in the `package.json` file and commits it.
 3. Creates a new [Git tag](https://git-scm.com/book/en/Git-Basics-Tagging) for the version being published.
 4. Pushes the tag and current branch up to GitHub.
-5. Updates Pulsar Package Repository with the new version being published.
+5. Updates Pulsar Package Registry with the new version being published.
 
 Now run the following commands to publish your package:
 
@@ -46,7 +46,7 @@ $ pulsar -p publish minor
 
 If this is the first package you are publishing, the `pulsar -p publish` command may prompt you for your GitHub username and password. If you have two-factor authentication enabled, use a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) in lieu of a password. This is required to publish and you only need to enter this information the first time you publish. The credentials are stored securely in your [keychain](<https://en.wikipedia.org/wiki/Keychain_(software)>) once you login.
 
-Your package is now published and available on Pulsar Package Repository. Head on over to `https://web.pulsar-edit.dev/packages/your-package-name` to see your package’s page.
+Your package is now published and available on Pulsar Package Registry. Head on over to `https://packages.pulsar-edit.dev/packages/your-package-name` to see your package’s page.
 
 With `pulsar -p publish`, you can bump the version and publish by using
 

docs/docs.11tydata.json

@@ -54,7 +54,7 @@
     {
       "text": "APIs",
       "link": "/api",
-      "summary": "Read reference documentation for our APIs: Pulsar’s own API and that of the package repository."
+      "summary": "Read reference documentation for our APIs: Pulsar’s own API and that of the package registry."
     }
   ]
 

docs/getting-started/dependencies-for-some-community-packages.md

@@ -9,8 +9,8 @@ This is an advanced topic and it might not be necessary! Most community packages
 
 However, some popular packages will involve the use of native modules. Please read this page if you’re planning to install one of the packages below:
 
-* [x-terminal-reloaded](https://web.pulsar-edit.dev/packages/x-terminal-reloaded)
-* [Hydrogen](https://web.pulsar-edit.dev/packages/hydrogen) (which should be [installed directly from GitHub](https://github.com/pulsar-edit/package-backend/blob/main/docs/reference/Admin_Actions.md#hydrogen))
+* [x-terminal-reloaded](https://packages.pulsar-edit.dev/packages/x-terminal-reloaded)
+* [Hydrogen](https://packages.pulsar-edit.dev/packages/hydrogen) (which should be [installed directly from GitHub](https://github.com/pulsar-edit/package-backend/blob/main/docs/reference/Admin_Actions.md#hydrogen))
 
 :::
 

docs/getting-started/terminal-commands.md

@@ -80,7 +80,7 @@ The `-p`/`--package` switch is most useful for AppImage installations, but you m
 
 ## About `ppm`
 
-`ppm` stands for _Pulsar Package Manager_. It’s a Pulsar-branded version of [`npm`](https://web.pulsar-edit.dev/) that installs packages from Pulsar’s own [package registry](https://web.pulsar-edit.dev/).
+`ppm` stands for _Pulsar Package Manager_. It’s a Pulsar-branded version of [`npm`](https://packages.pulsar-edit.dev/) that installs packages from Pulsar’s own [package registry](https://packages.pulsar-edit.dev/).
 
 It’ll be covered in greater depth later; just know that it’s a way to install Pulsar packages from the command line, and it works whether or not Pulsar is running.
 

docs/ide-features/community-packages.md

@@ -53,7 +53,7 @@ In this case, the services’ differing designs are the reason. The `linter` ser
 
 Nonetheless, this is an implementation detail that users usually won’t have to care about. All you need to know is that **providers** need to match up with **consumers** and _vice versa_.
 
-In the Pulsar package repository, each package will list the services it consumes and provides. Clicking on a particular service in that list will show you search results for packages that fulfill the _opposite_ side of that service (and can therefore be paired with the original package).
+In the Pulsar Package Registry, each package will list the services it consumes and provides. Clicking on a particular service in that list will show you search results for packages that fulfill the _opposite_ side of that service (and can therefore be paired with the original package).
 
 :::
 

docs/ide-features/getting-started.md

@@ -47,9 +47,9 @@ Using language servers in Pulsar is a two-step process:
 
 The Language Server Project site maintains [a list of known language servers](https://microsoft.github.io/language-server-protocol/implementors/servers/) for various languages and frameworks. Often you’ll see more than one language server on that page for the same language! But it’s typically enough simply to verify that at least one server exists for your language.
 
-### Search the package repository for an IDE package for your language
+### Search the package registry for an IDE package for your language
 
-Packages that integrate with language servers are named according to convention. If you’re looking for an IDE package for a given language, search for `ide-[language]` in the package repository.
+Packages that integrate with language servers are named according to convention. If you’re looking for an IDE package for a given language, search for `ide-[language]` in the package registry.
 
 Suppose you use a language `foo`. You may find an `ide-foo` package in the repository; this would’ve been written for Atom and may be several years old by now, but may still work to some extent.