PHPackages                             den1n/nova-blog - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. den1n/nova-blog

AbandonedArchivedLibrary

den1n/nova-blog
===============

Laravel Nova blog resources.

v1.3.4(5y ago)78833MITPHPPHP &gt;=7.2

Since Oct 3Pushed 5y ago2 watchersCompare

[ Source](https://github.com/den1n/nova-blog)[ Packagist](https://packagist.org/packages/den1n/nova-blog)[ Docs](https://github.com/den1n/nova-blog)[ RSS](/packages/den1n-nova-blog/feed)WikiDiscussions master Synced 2mo ago

READMEChangelogDependencies (2)Versions (17)Used By (0)

nova-blog
=========

[](#nova-blog)

Laravel Nova blog resources.

Installation
------------

[](#installation)

Require package with Composer.

```
composer require den1n/nova-blog
```

Publish package resources.

```
php artisan vendor:publish --provider="Den1n\NovaBlog\ServiceProvider"
```

This will publish the following resources:

- Configuration file `config/nova-blog.php`
- Migration file `database/migrations/*_create_blog_tables.php`
- Translations `resources/lang/vendor/nova-blog`
- Views `resources/views/vendor/nova-blog`
- JavaScript assets `resources/js/vendor/nova-blog`
- CSS assets `resources/sass/vendor/nova-blog`

Add `noba-blog` components provided by the package to file `resources\js\app.js` before `Vue` initialization.

```
require('./vendor/nova-blog');
```

Add `noba-blog` styles provided by the package to file `resources\sass\app.scss`.

```
@import './vendor/nova-blog';
```

Migrate database.

```
php artisan migrate
```

Add instance of class `Den1n\NovaBlog\Tool` to your `App\Providers\NovaServiceProvider::tools()` method to display the blog posts, comments, categories and tags within your Nova resources.

```
/**
 * Get the tools that should be listed in the Nova sidebar.
 *
 * @return array
 */
public function tools()
{
    return [
        new \Den1n\NovaBlog\Tool,
    ];
}
```

Serving Blog Posts
------------------

[](#serving-blog-posts)

To serve blog posts append this route to your `routes/web.php` file.

```
Route::novaBlogRoutes();
```

You can define route with prefix.

```
Route::novaBlogRoutes('/blog');
```

You can get url to existing post by using Laravel `route` helper.

```
use \Den1n\NovaPosts\Models\Post;

$url = route('nova-blog.post', [
    'post' => Post::find(1),
]);

// Or you can pass a post slug.
$url = route('nova-blog.post', [
    'post' => 'my-post-slug',
]);
```

Default template
----------------

[](#default-template)

Blog controller will serve posts with `default` template.

Template is published to views directory `resources/views/vendor/nova-blog/templates/default.blade.php`.

Template will receive these variables when processed:

- $post: instance of `Post` model.
- $sidebarPosts: collection of `Post` models.
- $sidebarCategories: collection of `Category` models.
- $sidebarTags: collection of `Tag` models.

You can freely modify `default` template.

Creating a custom template
--------------------------

[](#creating-a-custom-template)

First create a custom blade template in `resources/views/vendor/nova-blog/templates` directory.

For example, `rich.blade.php`.

Then register it in configuration file `config/nova-blog.php`.

```
/**
 * Array of templates used by controller.
 */

'templates' => [
    // ...
    [
        'name' => 'rich',
        'description' => 'A rich template',
    ],
],
```

After that your custom template will be available to select when creating blog post or updating existing one.

WYSIWYG editor
--------------

[](#wysiwyg-editor)

By default package uses default WYSIWYG editor [provided by Nova](https://nova.laravel.com/docs/1.0/resources/fields.html#trix-field).

You can replace default editor. For example, with `froala/nova-froala-field`.

To do this, [install the package](https://github.com/froala/nova-froala-field) and update `editor` settings in `config/nova-pages.php` file.

```
    /**
     * Settings for WYSIWYG editor.
     */

    'editor' => [
        /**
         * Nova field class name.
         */

        'class' => \Froala\NovaFroalaField\Froala::class,

        /**
         * Options which will be applied to te field instance.
         * Key: name of field method.
         * Value: list of method arguments.
         */

        'options' => [
            'withFiles' => ['public', 'nova-pages'],

            // Froala options.
            'options' => [[
                'heightMax' => 800,
                'heightMin' => 300,
            ]],
        ],
    ],
```

Screenshots
-----------

[](#screenshots)

### Posts

[](#posts)

[![Posts](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/posts.png)](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/posts.png)

### Post Form

[](#post-form)

[![Post Form](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/post-form.png)](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/post-form.png)

### Post Detail

[](#post-detail)

[![Post Detail](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/post-detail.png)](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/post-detail.png)

### Blog Example

[](#blog-example)

[![Blog Example](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/blog.png)](https://raw.githubusercontent.com/den1n/nova-blog/master/screens/blog.png)

Contributing
------------

[](#contributing)

1. Fork it.
2. Create your feature branch: `git checkout -b my-new-feature`.
3. Commit your changes: `git commit -am 'Add some feature'`.
4. Push to the branch: `git push origin my-new-feature`.
5. Submit a pull request.

Support
-------

[](#support)

If you require any support open an issue on this repository.

License
-------

[](#license)

MIT

###  Health Score

31

—

LowBetter than 68% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity21

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~15 days

Recently: every ~10 days

Total

16

Last Release

2181d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/072c9e57d17e8bb52f0746cf1591dbf7fb755b9f4999a75999d28c37c85b6c8e?d=identicon)[den1n](/maintainers/den1n)

---

Top Contributors

[![den1n](https://avatars.githubusercontent.com/u/25498109?v=4)](https://github.com/den1n "den1n (37 commits)")

---

Tags

laravelblognovaden1n

### Embed Badge

![Health badge](/badges/den1n-nova-blog/health.svg)

```
[![Health](https://phpackages.com/badges/den1n-nova-blog/health.svg)](https://phpackages.com/packages/den1n-nova-blog)
```

###  Alternatives

[stephenjude/filament-blog

Filament Blog Builder

20317.8k](/packages/stephenjude-filament-blog)[inspheric/nova-defaultable

Default values for Nova fields when creating resources and running resource actions.

51174.8k1](/packages/inspheric-nova-defaultable)[cybercog/laravel-nova-ban

A Laravel Nova banning functionality for your application.

40199.8k](/packages/cybercog-laravel-nova-ban)[datomatic/nova-detached-actions

A Laravel Nova tool to allow for placing actions in the Nova toolbar detached from the checkbox selection mechanism.

11229.2k](/packages/datomatic-nova-detached-actions)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
