tailwind 3.4.0 and update readme

Author: jeffreyvr

README.MD

@@ -2,7 +2,6 @@
 
 [![GitHub release](https://img.shields.io/github/release/jeffreyvr/tailpress?include_prereleases=&sort=semver)](https://github.com/jeffreyvr/tailpress/releases/)
 [![License](https://img.shields.io/badge/License-MIT-blue)](#license)
-[![issues - tailpress](https://img.shields.io/github/issues/jeffreyvr/tailpress)](https://github.com/jeffreyvr/tailpress/issues)
 
 # Introduction
 
@@ -20,25 +19,16 @@ composer global require jeffreyvanrossum/tailpress-installer
 tailpress new example-theme
 ```
 
-*If you haven't already, make sure to place the `~/.composer/vendor/bin` directory in your `PATH` so the tailpress executable is found when you run the tailpress command in your terminal.*
+*If the tailpress command is not found, make sure to place Composer's global vendor bin in your `$PATH` ([see](#command-tailpress-not-found)).*
 
-You can optionally set the theme name.
+Flags you can pass when using the installer:
+- Set a theme name `--name="Example Theme"`
+- Choose your compiler, mix or esbuild: `--compiler="esbuild"`
+- Initialize a git repository `--git`
+- Set the git branch name `--branch="main"`
 
-```bash
-tailpress new example-theme --name="Example Theme"
-```
-
-By default, TailPress uses Laravel Mix for compiling. Rather use Esbuild?
-
-```bash
-tailpress new example-theme --compiler="esbuild"
-```
-
-You can also initialize a new Git repository (branch defaults to `main`):
-
-```bash
-tailpress new example-theme --name="Example Theme" --git --branch="main"
-```
+If you choose to install WordPress through the installer, these flags might be of interest as well:
+`--dbname`, `--dbuser`, `--dbpass` and `--dbhost`.
 
 Once your theme is ready, don't forget to cd into the directory.
 
@@ -67,20 +57,30 @@ There are several NPM scripts available. You'll find the full list in the `packa
 | dev        | Creates a development build of app.js, app.css and editor-style.css.           |
 | watch      | Runs several watch scripts concurrently.                                       |
 
-## Block editor support
+## Tips
 
-TailPress comes with support for the [block editor](https://wordpress.org/support/article/wordpress-editor/).
+### Styling within the block editor
 
-A basic setup for `theme.json` is included. This also means that you need to at least use WordPress 5.8. If you wan't to support earlier WordPress versions, you can use an [older version](https://github.com/jeffreyvr/tailpress/tree/0.1.1) of TailPress instead.
+To make the editing experience within the block editor more in line with the front end styling, a `editor-style.css` is generated.
 
-CSS-classes for alignment (full, wide etc.) are generated automatically. You can opt-out on this by removing the plugin from the `tailwind.config.js` file.
+### CSS classes generated by TailPress
 
-To make the editing experience within the block editor more in line with the front end styling, a `editor-style.css` is generated.
+CSS classes for alignment (full, wide etc.) are generated automatically. You can opt-out on this by removing the plugin from the `tailwind.config.js` file.
 
-### Define theme colors and font sizes
+### Customize colors
 
 Several colors and font sizes are defined from the beginning. You can modify them in `theme.json`.
 
+### Command `tailpress` not found
+
+Make sure to place Composer's global vendor bin directory in your `$PATH` so the `tailpress` executable can be found by your system. This directory exists in different locations based on your operating system; however, some common locations include:
+
+- macOS: `$HOME/.composer/vendor/bin`
+- Windows: `%USERPROFILE%\AppData\Roaming\Composer\vendor\bin`
+- GNU / Linux Distributions: `$HOME/.config/composer/vendor/bin or $HOME/.composer/vendor/bin`
+
+You could also find the composer's global installation path by running `composer global about` and looking up from the first line.
+
 ## Links
 
 * [TailPress website](https://tailpress.io)