Skip to content

Commit

Permalink
fix heading caps
Browse files Browse the repository at this point in the history
  • Loading branch information
danharrin committed May 3, 2024
1 parent 37959ae commit 2f5ac60
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
8 changes: 4 additions & 4 deletions packages/support/docs/08-plugins/02-build-a-panel-plugin.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ You can find the final code for this plugin at [https://github.com/awcodes/clock

First, we'll create the plugin using the steps outlined in the [getting started guide](/docs/3.x/support/plugins/getting-started#creating-a-plugin).

## Step 2: Clean Up
## Step 2: Clean up

Next, we'll clean up the plugin to remove the boilerplate code we don't need. This will seem like a lot, but since this is a simple plugin, we can remove a lot of the boilerplate code.

Expand Down Expand Up @@ -88,7 +88,7 @@ npm install

You may also remove the Testing directories and files, but we'll leave them in for now, although we won't be using them for this example, and we highly recommend that you write tests for your plugins.

## Step 3: Setting up the Provider
## Step 3: Setting up the provider

Now that we have our plugin cleaned up, we can start adding our code. The boilerplate in the `src/ClockWidgetServiceProvider.php` file has a lot going on so, let's delete everything and start from scratch.

Expand Down Expand Up @@ -129,7 +129,7 @@ class ClockWidgetServiceProvider extends PackageServiceProvider
}
```

## Step 4: Create the Widget
## Step 4: Create the widget

Now we can create our widget. We'll first need to extend Filament's `Widget` class in our `ClockWidget.php` file and tell it where to find the view for the widget. Since we are using the PackageServiceProvider to register our views, we can use the `::` syntax to tell Filament where to find the view.

Expand Down Expand Up @@ -191,7 +191,7 @@ return [
];
```

## Step 5: Update your Readme
## Step 5: Update your README

You'll want to update your `README.md` file to include instructions on how to install your plugin and any other information you want to share with users, Like how to use it in their projects. For example:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You can find the final code for this plugin at [https://github.com/awcodes/headi

First, we'll create the plugin using the steps outlined in the [getting started guide](/docs/3.x/support/plugins/getting-started#creating-a-plugin).

## Step 2: Clean Up
## Step 2: Clean up

Next, we'll clean up the plugin to remove the boilerplate code we don't need. This will seem like a lot, but since this is a simple plugin, we can remove a lot of the boilerplate code.

Expand Down Expand Up @@ -86,7 +86,7 @@ module.exports = {

You may also remove the testing directories and files, but we'll leave them in for now, although we won't be using them for this example, and we highly recommend that you write tests for your plugins.

## Step 3: Setting up the Provider
## Step 3: Setting up the provider

Now that we have our plugin cleaned up, we can start adding our code. The boilerplate in the `src/HeadingsServiceProvider.php` file has a lot going on so, let's delete everything and start from scratch.

Expand Down Expand Up @@ -265,7 +265,7 @@ Then we need to build our stylesheet.
npm run build
```

## Step 7: Update your Readme
## Step 7: Update your README

You'll want to update your `README.md` file to include instructions on how to install your plugin and any other information you want to share with users, Like how to use it in their projects. For example:

Expand Down

0 comments on commit 2f5ac60

Please sign in to comment.