Update links to explicit paths (polkadot-js#17)

* Update links to explicit paths

* Update README

Author: jacogr

README.md

@@ -1,33 +1,9 @@
-# Website
+# polkadot-js docs
 
-This website is built using [Docusaurus 2](https://v2.docusaurus.io/), a modern static website generator.
+This is a documentation portal for the `@polkadot` family of tools and libraries. The latest version is always available at [https://polkadot.js.org/docs/](https://polkadot.js.org/docs/)
 
-## Installation
 
-```console
-yarn install
-```
+## Help us help others
 
-## Local Development
+If you spot gaps in the information provided, or are uncertain about any specific area, please do [log an issue](https://github.com/polkadot-js/docs/issues) or if you are that way inclined, make a pull-request. We really want to have good documentation in these areas and allow people to be productive right from the start.
 
-```console
-yarn start
-```
-
-This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server.
-
-## Build
-
-```console
-yarn build
-```
-
-This command generates static content into the `build` directory and can be served using any static contents hosting service.
-
-## Deployment
-
-```console
-GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
-```
-
-If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

docs/api/FAQ.md

@@ -1,5 +1,4 @@
 ---
-id: FAQ
 title: FAQ
 ---
 

docs/api/cookbook/intro.md

@@ -1,5 +1,6 @@
 ---
 title: Overview
+slug: /api/cookbook
 ---
 
 The cookbook hosts small code snippets in a question-answer format. It does not walk you through the whole setup, like the [basic examples](../examples/promise), but rather aims to answer some questions around specific uses. It also does not replace the [FAQ](../FAQ.md), rather this is focussed explicitly on code samples, instead of general trouble-shooting for common mishaps.

docs/api/intro.md

@@ -5,8 +5,8 @@ slug: /api
 
 The API provides application developers the ability to query a node and interact with the Polkadot or Substrate chains using Javascript. Here you will find documentation and examples to get you started.
 
-[Jump right in](start/) and get an overview on using the API in your projects, from installation all the way through to making it do magic. Have things working and want tips? The [cookbook](cookbook/) provides some tips and tricks. Getting started and want some full examples? [The ApiPromise examples](examples/promise/) provide some basic examples.
+[Jump right in](start/intro.md) and get an overview on using the API in your projects, from installation all the way through to making it do magic. Have things working and want tips? The [cookbook](cookbook/intro.md) provides some tips and tricks. Getting started and want some full examples? [The ApiPromise examples](examples/promise/intro.md) provide some basic examples.
 
-For oft-repeated questions, the [FAQ](FAQ) may have what you are looking for.
+For oft-repeated questions, the [FAQ](FAQ.md) may have what you are looking for.
 
-Separated from the API you will also find the [Substrate metadata](../substrate) section that has an overview of the RPC, extrinsics, events and errors available on a typical Substrate node.
+Separated from the API you will also find the [Substrate metadata](../substrate/intro.md) section that has an overview of the RPC, extrinsics, events and errors available on a typical Substrate node.

docs/api/start/intro.md

@@ -1,5 +1,6 @@
 ---
 title: Overview
+slug: /api/start
 ---
 
 These sections should provide you with all the information needed to install the `@polkadot/api` package, understand the structure of the interfaces and allow you to start using it. For existing users this really should be titled "Things I wish I knew before I started using the api" - it really aims to close the gap to allow anybody to get to grips with using the packages.

docs/keyring/intro.md

@@ -5,4 +5,4 @@ slug: /keyring
 
 The Keyring allows you to manage a set of keys in a consistent environment, allows you to perform operations on these keys (such as sign/verify) and never exposes the secretKey to the outside world.
 
-For oft-repeated questions, the [FAQ](FAQ) may have what you are looking for.
+For oft-repeated questions, the [FAQ](FAQ.md) may have what you are looking for.

docs/util-crypto/FAQ.md

@@ -1,5 +1,4 @@
 ---
-id: FAQ
 title: FAQ
 ---
 

docs/util-crypto/intro.md

@@ -3,4 +3,4 @@ title: Overview
 slug: /util-crypto
 ---
 
-For oft-repeated questions, the [FAQ](FAQ) may have what you are looking for.
+For oft-repeated questions, the [FAQ](FAQ.md) may have what you are looking for.

src/css/custom.css

@@ -20,13 +20,17 @@
   --ifm-toc-border-color: transparent;
 }
 
+h1 {
+  font-size: var(--ifm-h1-font-size) !important;
+}
+
 .docusaurus-highlight-code-line {
   background-color: rgb(72, 77, 91);
   display: block;
   margin: 0 calc(-1 * var(--ifm-pre-padding));
   padding: 0 var(--ifm-pre-padding);
 }
 
-h1 {
-  font-size: var(--ifm-h1-font-size) !important;
+.menu__link {
+  outline: none !important;
 }