docs update

Author: damianlegawiec

README.md

@@ -1,7 +1,5 @@
 # Developer's Documentation
 
-![Vendo comes with a built-in storefront, features and integrations. Try it for free.](.gitbook/assets/spree\_vendo\_user\_doc.png)
-
 [![GitHub stars](https://img.shields.io/github/stars/spree/spree.svg?style=social\&label=Star\&maxAge=2592000)](https://github.com/spree/spree/)
 
 This is the developer-focused part of Spree Commerce documentation. Here you will find all kinds of information on topics such as Customization, Deployment, Configuration, and inside knowledge on how Spree works under the hood.

SUMMARY.md

@@ -4,14 +4,15 @@
 
 ```ruby
 gem 'spree' # core and API
-gem 'spree_backend' # Rails admin panel (optional)
+gem 'spree_backend' # Admin panel (optional)
+gem 'spree_frontend' # Storefront (optional)
 gem 'spree_emails' # transactional emails (optional)
 gem 'spree_sample' # dummy data like products, taxons, etc
-gem 'spree_auth_devise', '~> 4.3' # Devise integration (optional)
-gem 'spree_gateway', '~> 3.9' # payment gateways eg. Stripe, Braintree (optional)
-gem 'spree_i18n', '~> 5.0' # translation files (optional) 
+gem 'spree_auth_devise' # Devise integration (optional)
+gem 'spree_gateway' # payment gateways eg. Stripe, Braintree (optional)
+gem 'spree_i18n' # translation files (optional) 
 
-# only needed for MacOS and Ruby 3.0
+# only needed for MacOS and Ruby 3+
 gem 'sassc', github: 'sass/sassc-ruby', branch: 'master'
 ```
 
@@ -25,23 +26,23 @@ gem 'sassc', github: 'sass/sassc-ruby', branch: 'master'
 
 ```
 bin/rails g spree:install --user_class=Spree::User
+bin/rails g spree:backend:install
+bin/rails g spree:frontend:install
 bin/rails g spree:auth:install
 bin/rails g spree_gateway:install
-bin/rails javascript:install:esbuild
-bin/rails g spree:backend:install
 ```
 
 ### Installation options
 
 By default, the installation generator (`rails g spree:install`) will run migrations as well as adding seed. This can be disabled using
 
-```
+```bash
 bin/rails g spree:install --migrate=false --sample=false --seed=false
 ```
 
 You can always perform any of these steps later by using these commands.
 
-```
+```bash
 bin/rake railties:install:migrations
 bin/rails db:migrate
 bin/rails db:seed
@@ -78,7 +79,7 @@ To stop the webserver, hit Ctrl-C in the terminal window where it's running. In
 
 #### Logging Into the Admin Panel
 
-The next thing you'll probably want to do is to log into the admin interface. Use your browser window to navigate to [http://localhost:4000/admin](http://localhost:4000/admin). You can log in with the username `[email protected]` and password `spree123`.
+The next thing you'll probably want to do is to log into the admin interface. Use your browser window to navigate to [http://localhost:3000/admin](http://localhost:3000/admin). You can log in with the username `[email protected]` and password `spree123`.
 
 Upon successful authentication, you should see the admin screen:
 

advanced/existing_app_tutorial.md

@@ -1,16 +1,12 @@
 # Getting Started with Spree API
 
-Spree comes with a fully-featured API that allows it to operate in a fully headless mode.
-
-To use the APIs, install the `spree_api` gem with a version corresponding to your version of Spree. If you're using [spree\_starter](https://github.com/spree/spree\_starter) as a base for your project, the API will be included out of the box.
-
+Spree comes with a fully-featured API that allows it to operate in a fully headless mode (if you wish). This means that you can use Spree as a backend for your custom storefront, mobile app, or any other application that needs to interact with an e-commerce platform.
 
+To use the APIs, install the `spree_api` gem with a version corresponding to your version of Spree. If you're using [spree\_starter](https://github.com/spree/spree\_starter) as a base for your project or you have the `spree` gem in your `Gemfile` the API will be included out of the box.
 
 Currently there are two types of APIs:
 
 * [Storefront API](storefront-api/) - that's designed to allow customers to interact with the store via external applications (e.g. Vue Storefront or a dedicated mobile app).
 * [Platform API](platform-api/) - that provides management capabilities, allowing third party apps to perform actions otherwise available via the admin panel.
 
-
-
-Spree also offers a legacy v1 API, that's been extracted to `spree_api_v1`gem in Spree 4.5. It uses an outdated architecture and is now deprecated.
+Spree also offers a legacy v1 API, that's been extracted to `spree_api_v1` gem in Spree 4.5. It is not recommended to use it in new projects, but it's still available for existing ones.

api/getting-started-with-spree-api.md

@@ -28,7 +28,7 @@ Once the application is configured inside Spree, you can use its credentials to
 
 To obtain the token, send the following `POST` request to `/spree_oauth/token`
 
-```
+```json
 {
   "grant_type": "client_credentials",
   "client_id": "xxx",

api/platform-api/authenticating-requests.md

@@ -6,7 +6,7 @@ Storefront API requires authorization only for certain actions associated with u
 
 To obtain a token, send the following `POST` request to `/spree_oauth/token`
 
-```
+```json
 {
   "grant_type": "password",
   "username": "[email protected]",
@@ -22,7 +22,7 @@ OAuth tokens obtained via the previous step are valid only for a specific time.
 
 To refresh a token, send the following `POST` request to `/spree_oauth/token`
 
-```
+```json
 {
   "grant_type": "refresh_token",
   "refresh_token": "xxx"
@@ -35,6 +35,12 @@ In the response, you'll receive a new bearer token to use when accessing the API
 
 Endpoints under `/api/v2/storefront/cart` and `/api/v2/storefront/checkout` paths also allow interactions without bearer token, which allows building guest checkouts.
 
-When you first create a cart via `POST /api/v2/storefront/cart`, you'll receive a response containing an empty cart. This response also contains a `token` field. 
+When you first create a cart via:
+
+```http
+POST /api/v2/storefront/cart
+```
+
+You'll receive a response containing an empty cart. This response also contains a `token` field. 
 
 You can store this token in the frontend session and pass it in a `X-Spree-Order-Token: {token}` header.