Add Plugin in Bedrock

1. **Navigate to your Bedrock project directory**:
Open your terminal and change to your Bedrock project directory.

cd path/to/your/bedrock

2. **Require the plugin via Composer**:
Use the `composer require` command to add the plugin. You will need to specify the plugin's package name, which typically follows the format `vendor/plugin-name`.

For example, to add a plugin like "Advanced Custom Fields," you would run:

composer require wpackagist-plugin/advanced-custom-fields

If the plugin is hosted on WordPress.org, you can use the `wpackagist-plugin` repository. For plugins from other sources, you might need to specify the repository details.

3. **Update Composer**:
After running the command, Composer will update your `composer.json` and `composer.lock` files, and install the new plugin.

4. **Check the `composer.json` file**:
Ensure that the plugin appears under the `"require"` section in your `composer.json`. It should look something like this:

"require": {
       "php": ">=7.4",
       "wpackagist-plugin/advanced-custom-fields": "^5.9"
   }

5. **Run Composer Install**:
If you haven’t already, you can run:

composer install

This ensures that all dependencies are correctly installed.

6. **Activate the Plugin**:
After installing the plugin, you may need to activate it through the WordPress admin panel or via WP-CLI.

If using WP-CLI, you can activate the plugin with:

wp plugin activate advanced-custom-fields

That's it! You should now have the new plugin added to your Bedrock project. If you have any specific plugin in mind, let me know, and I can provide tailored instructions!

### Updating WordPress Core

1. **Navigate to your Bedrock project directory**:
Open your terminal and change to your Bedrock project directory.

cd path/to/your/bedrock

2. **Update WordPress via Composer**:
You can update the WordPress core by running:

composer update johnbillion/extended-cpt

or if you want to update WordPress core along with all other dependencies, use:

composer update

This will update all the dependencies listed in your `composer.json`, including the WordPress core.

3. **Check the `composer.json` file**:
Ensure that your WordPress version constraint is set to allow updates. For example:

"require": {
       "php": ">=7.4",
       "wordpress/wordpress": "^6.3"
   }

Adjust the version as necessary if you want to specify a certain version.

### Updating Plugins

1. **Update Specific Plugin**:
To update a specific plugin, use the `composer update` command followed by the plugin's package name. For example, to update "Advanced Custom Fields":

composer update wpackagist-plugin/advanced-custom-fields

2. **Update All Plugins**:
If you want to update all installed plugins, run:

composer update

This command will update all packages defined in your `composer.json`, including plugins and WordPress itself.

### Post-Update Steps

1. **Check for any database updates**:
After updating, log into your WordPress admin panel. Sometimes, after a core or plugin update, you may need to run a database update. WordPress will prompt you to do this if necessary.

2. **Test your site**:
After performing updates, ensure to thoroughly test your site to confirm that everything is working as expected.

3. **Clear Cache (if applicable)**:
If you are using caching plugins or server-level caching, clear the cache to ensure that your visitors see the latest version of your site.

### Note

If you are using version control (like Git), consider committing your changes before running updates, allowing you to revert back if anything goes wrong during the update process.

By following these steps, you can keep your WordPress site and its plugins up-to-date in a Bedrock environment! If you have any specific plugins or situations in mind, feel free to ask!

### 1. Navigate to Your Bedrock Project Directory

Open your terminal and change to your Bedrock project directory:

cd path/to/your/bedrock

### 2. Require the Hello Elementor Theme via Composer

You can add the Hello Elementor theme by running the following command:

composer require wpackagist-theme/hello-elementor

This command tells Composer to download the Hello Elementor theme from the WPackagist repository, which mirrors themes and plugins from WordPress.org.

### 3. Update Composer

After running the command, ensure that the theme is added to your `composer.json` file under the `"require"` section:

"require": {
    "php": ">=7.4",
    "wpackagist-theme/hello-elementor": "^2.5"
}

To install the theme, run:

composer install

or if you've already installed the theme but just want to ensure everything is up to date, you can run:

composer update wpackagist-theme/hello-elementor

### 4. Activate the Theme

After installation, you can activate the Hello Elementor theme. You can do this through the WordPress admin panel:

1. Log in to your WordPress admin dashboard.
2. Navigate to **Appearance > Themes**.
3. Locate the **Hello Elementor** theme and click **Activate**.

Alternatively, you can activate it via WP-CLI:

wp theme activate hello-elementor

### 5. Customize the Theme

Once activated, you can customize the Hello Elementor theme as needed using the Elementor page builder. If you haven't installed Elementor yet, you can add it via Composer as well:

composer require wpackagist-plugin/elementor

### 6. Post-Installation

1. **Check for Updates**: Make sure everything is up-to-date.
2. **Test Your Site**: Ensure the site is working correctly with the new theme.
3. **Clear Cache**: If you are using caching, clear it to see the changes immediately.

That's it! You've successfully added the Hello Elementor theme to your Bedrock project. If you have any other questions or need further assistance, feel free to ask!

### 1. Navigate to Your Bedrock Project Directory

Open your terminal and change to your Bedrock project directory:

cd path/to/your/bedrock

### 2. Require the Yoast SEO Plugin via Composer

You can add the Yoast SEO plugin by running the following command:

composer require wpackagist-plugin/wordpress-seo

This command installs the Yoast SEO plugin from the WPackagist repository, which mirrors plugins from WordPress.org.

### 3. Update Composer

After running the command, ensure that the plugin is listed in your `composer.json` under the `"require"` section:

"require": {
    "php": ">=7.4",
    "wpackagist-plugin/wordpress-seo": "^20.0"
}

Then, run the following command to install the new plugin:

composer install

If the plugin is already installed and you just want to ensure everything is up to date, you can run:

composer update wpackagist-plugin/wordpress-seo

### 4. Activate the Plugin

After installation, you can activate the Yoast SEO plugin. You can do this through the WordPress admin panel:

1. Log in to your WordPress admin dashboard.
2. Navigate to **Plugins**.
3. Locate the **Yoast SEO** plugin and click **Activate**.

Alternatively, you can activate it via WP-CLI:

wp plugin activate wordpress-seo

### 5. Configure Yoast SEO

After activation, you’ll see a new SEO option in the left sidebar of your WordPress admin. You can click on it to configure the settings according to your site's needs.

### 6. Post-Installation Steps

1. **Check for Updates**: Regularly check for updates to ensure you are using the latest version of Yoast SEO.
2. **Review Settings**: After installing, it's a good idea to review the plugin settings and configure it to optimize your site's SEO.
3. **Test Your Site**: Ensure your site is functioning correctly with the new plugin.
4. **Clear Cache**: If you are using caching, clear it to see the changes immediately.

That's it! You've successfully added and activated the Yoast SEO plugin in your Bedrock project. If you have any further questions or need assistance with configurations, feel free to ask!

### 1. Navigate to Your Bedrock Project Directory

Open your terminal and change to your Bedrock project directory:

cd path/to/your/bedrock

### 2. Require the WP Speedster Plugin via Composer

You can add the WP Speedster plugin by running the following command:

composer require wpackagist-plugin/wp-speedster

This command installs the WP Speedster plugin from the WPackagist repository, which mirrors plugins from WordPress.org.

### 3. Update Composer

After running the command, check that the plugin is listed in your `composer.json` under the `"require"` section:

"require": {
    "php": ">=7.4",
    "wpackagist-plugin/wp-speedster": "^1.0"
}

To install the new plugin, run:

composer install

If the plugin is already installed and you just want to update it, use:

composer update wpackagist-plugin/wp-speedster

### 4. Activate the Plugin

After installation, you need to activate the WP Speedster plugin. You can do this through the WordPress admin panel:

1. Log in to your WordPress admin dashboard.
2. Navigate to **Plugins**.
3. Locate the **WP Speedster** plugin and click **Activate**.

Alternatively, you can activate it via WP-CLI:

wp plugin activate wp-speedster

### 5. Configure WP Speedster

After activation, you'll find a new menu item for WP Speedster in your WordPress admin panel. Click on it to access the settings and configure the plugin according to your performance optimization needs.

### 6. Post-Installation Steps

1. **Check for Updates**: Regularly check for updates to ensure you are using the latest version of WP Speedster.
2. **Review Settings**: It's a good idea to review and adjust the plugin settings for optimal performance.
3. **Test Your Site**: Ensure your site is functioning correctly after the plugin installation and activation.
4. **Clear Cache**: If you're using caching plugins or server-level caching, clear the cache to see the changes.

That's it! You've successfully added and activated the WP Speedster plugin in your Bedrock project. If you have any further questions or need help with configuration, feel free to ask!

### Option 1: Install via Git Repository

If the plugin is hosted on a Git repository (like GitHub), you can add it directly to your `composer.json`. Here’s how:

1. **Open your `composer.json` file** in your Bedrock project.

2. **Add a custom repository entry** for the plugin. Here’s an example for a plugin hosted on GitHub:

{
       "repositories": [
           {
               "type": "vcs",
               "url": "https://github.com/vendor/plugin-name"
           }
       ],
       "require": {
           "vendor/plugin-name": "dev-main"
       }
   }

Replace `vendor/plugin-name` with the actual plugin package name and `dev-main` with the appropriate branch or tag.

3. **Run Composer Install**:
After updating your `composer.json`, run:

composer install

or if you have already installed other packages and just want to add this new one:

composer update vendor/plugin-name

### Option 2: Install from a Zip File

If you have a zip file for the plugin, you can manually install it:

1. **Download the Plugin**:
Download the zip file for the plugin.

2. **Unzip the Plugin**:
Extract the contents of the zip file.

3. **Move the Plugin to the Right Directory**:
Copy the extracted folder to the `web/app/plugins/` directory of your Bedrock project.

4. **Activate the Plugin**:
Log in to your WordPress admin dashboard, navigate to **Plugins**, find your new plugin, and click **Activate**.

### Option 3: Install via Custom Composer Package

You can create your own Composer package if you have the plugin files.

1. **Create a New Directory for the Plugin**:
Create a directory for your custom plugin in your Bedrock project, for example:

mkdir -p web/app/plugins/your-plugin

2. **Place Your Plugin Files**:
Copy your plugin files into this directory.

3. **Add a `composer.json` for the Plugin**:
In your plugin directory, create a `composer.json` file that describes your plugin:

{
       "name": "vendor/your-plugin",
       "description": "A brief description of your plugin.",
       "type": "wordpress-plugin",
       "require": {},
       "autoload": {
           "psr-4": {
               "Vendor\YourPlugin\": "src/"
           }
       }
   }

4. **Update Your Bedrock `composer.json`**:
In your Bedrock project’s `composer.json`, add a path repository for your plugin:

{
       "repositories": [
           {
               "type": "path",
               "url": "web/app/plugins/your-plugin"
           }
       ],
       "require": {
           "vendor/your-plugin": "*"
       }
   }

5. **Run Composer Install**:
Run the following command to install the plugin:

composer install

### Activating the Plugin

After installation, activate the plugin either through the WordPress admin dashboard or using WP-CLI:

wp plugin activate vendor/your-plugin

### Summary

– For plugins not on WPackagist, you can install them from a Git repository, manually upload them, or create a custom Composer package.
– Remember to always check the plugin's licensing and compatibility with your WordPress version.

If you have a specific plugin in mind or need further assistance, feel free to ask!

### 1. Set Up Blade Files

Make sure your Blade files are located in the appropriate directory, typically `resources/views`. You can create a new Blade file or edit an existing one. Here’s an example of creating a new Blade file:

– Create a new Blade file named `example.blade.php` in the `resources/views` directory:

<!-- resources/views/example.blade.php -->
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link href="{{ mix('css/app.css') }}" rel="stylesheet">
    <title>Example Page</title>
</head>
<body class="font-sans">
    <h1 class="text-2xl">Hello, World!</h1>
    <p class="mt-4">This is an example of using Blade with Tailwind CSS.</p>
</body>
</html>

### 2. Configure Your Mix File

Ensure you have set up Laravel Mix to compile your assets. Typically, this is done in your `webpack.mix.js` file. Here’s an example of how your `webpack.mix.js` might look:

const mix = require('laravel-mix');

mix.js('resources/js/app.js', 'public/js')
   .sass('resources/sass/app.scss', 'public/css') // Or use .postCss if you're not using Sass
   .postCss('resources/css/app.css', 'public/css', [
       require('tailwindcss'),
   ])
   .version(); // Optional: versioning for cache busting

### 3. Compile Your Assets

Run the following command to compile your assets, which includes processing your Tailwind CSS styles:

npm install && npm run dev

or for production:

npm run production

### 4. Serve Your Application

You can serve your application using the Laravel development server:

php artisan serve

### 5. Access Your Blade File

You can create a route to access your Blade file. For example, in your `routes/web.php`, you can add:

use IlluminateSupportFacadesRoute;

Route::get('/example', function () {
    return view('example');
});

### 6. Use the Font in Your Blade Files

Now that you have added the `Public Sans` font to your Tailwind configuration, you can use it in your Blade files. The class `font-sans` applied to your “ tag in the example will ensure that the `Public Sans` font is used throughout your page.

### Final Example

Here’s a recap of what the example Blade file would look like, with the Tailwind CSS configuration applied:

<!-- resources/views/example.blade.php -->
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link href="{{ mix('css/app.css') }}" rel="stylesheet">
    <title>Example Page</title>
</head>
<body class="font-sans">
    <h1 class="text-2xl">Hello, World!</h1>
    <p class="mt-4">This is an example of using Blade with Tailwind CSS.</p>
</body>
</html>

### Summary

1. Create Blade files in the `resources/views` directory.
2. Ensure Tailwind CSS is configured in your `tailwind.config.js`.
3. Compile assets using Laravel Mix.
4. Set up a route to access the Blade file.
5. Use Tailwind CSS classes in your Blade files.

Now, you should be able to utilize your Blade files with Tailwind CSS styling in your Laravel application! If you need further assistance or have specific requirements, let me know!