docs(website): added v1 docs to website

Also removes not supported versions (<14.0)

Author: Enda Phelan

docs/plugins/creating-your-own-plugin.md

@@ -254,7 +254,7 @@ query archivedNotesAndComments {
 
 ### With `graphback generate`
 
-Some plugins are designed to be invoked through the Graphback CLI, such as those that output files to the local project. See [Plugin Overview](../overview.md#file-generation-with-cli).
+Some plugins are designed to be invoked through the Graphback CLI, such as those that output files to the local project. See [Plugin Overview](./overview.md#file-generation-with-cli).
 
 `graphback generate` dynamically loads the plugin package by its name defined in the `.graphqlrc`. For plugin packages that begin with `@`, due to a limitation where keys in a YAML object cannot begin with `@`, your plugin documentation should explicitly specify the package name with the `packageName` configuration value.
 

docs/resolvers/custom-resolvers.md

@@ -55,11 +55,11 @@ const apolloServer = new ApolloServer({
 })
 ```
 
-See the [GraphbackCRUDService API Reference](../api/graphback-core/interfaces/_runtime_graphbackcrudservice_.graphbackcrudservice) for information on the methods and parameters available in the `GraphbackCRUDService` interface.
+See the [GraphbackCRUDService API Reference](../api/graphback-core/interfaces/_runtime_graphbackcrudservice_.graphbackcrudservice.md) for information on the methods and parameters available in the `GraphbackCRUDService` interface.
 
 ### context
 
-The [GraphbackContext](../api/graphback-core/interfaces/_runtime_interfaces_.graphbackcontext) interface defines all CRUD services in the `graphback` property. Each service name matches exactly with the name of the model defined in your GraphQL schema.
+The [GraphbackContext](../api/graphback-core/interfaces/_runtime_interfaces_.graphbackcontext.md) interface defines all CRUD services in the `graphback` property. Each service name matches exactly with the name of the model defined in your GraphQL schema.
 
 Accessing the CRUD service for the `Note` model:
 
@@ -118,7 +118,7 @@ In order to avoid such cases, we recommend to pass the `info` object only when t
 
 
 ### Retrieving Nested Fields From `GraphQLResolveInfo`
-If you want to retrieve nested selected fields from the GraphQL query to the database query, you can optionally pass the `nested path` as an argument to the [`findBy`](../api/core/classes/_runtime_crudservice_.crudservice.md#findby) method. 
+If you want to retrieve nested selected fields from the GraphQL query to the database query, you can optionally pass the `nested path` as an argument to the [`findBy`](../api/graphback-core/classes/_runtime_crudservice_.crudservice.md#findby) method. 
 
 For example:
 

website/docusaurus.config.js

@@ -27,29 +27,21 @@ module.exports = {
       },
       items: [
         {
-          to: 'docs/next/introduction',
+          to: 'docs/introduction',
           activeBasePath: 'docs',
           label: 'Docs',
           position: 'left',
           items: [
-            { label: '0.16.x', to: 'docs/introduction' },
+            { label: '1.0', to: 'docs/introduction' },
+            { label: '0.16.x', to: 'docs/0.16.x/introduction' },
             { label: '0.15.x', to: 'docs/0.15.x/introduction' },
             { label: '0.14.x', to: 'docs/0.14.x/introduction' },
-            { label: '0.12.x', to: 'docs/0.12.x/gettingstarted' },
-            { label: '0.11.x', to: 'docs/0.11.x/gettingstarted' },
-            { label: '0.10.x', to: 'docs/0.10.x/gettingstarted' },
-            { label: '0.9.x', to: 'docs/0.9.x/gettingstarted' },
             {
               label: 'Master/Unreleased',
               to: 'docs/next/introduction',
             },
           ],
         },
-        {
-          to: 'versions',
-          label: `v0.16.x`,
-          position: 'right',
-        },
         {
           to: 'blog',
           label: 'Blog',