README

Installation

You can install the package via composer:

composer require daikazu/welcome-bar

You can publish the config file with:

php artisan vendor:publish --tag="welcome-bar-config"

This is the contents of the published config file:

return [
    /*
      |--------------------------------------------------------------------------
      | Storage Path
      |--------------------------------------------------------------------------
      */
    'storage_path' => storage_path('app/welcome-bar.json'),

    /*
    |--------------------------------------------------------------------------
    | Route Middlewares or Security
    |--------------------------------------------------------------------------
    |
    | For example, you could specify a route middleware group here that your
    | "update" route uses for authentication or token checking.
    |
    */
    'middleware' => [
        'update' => ['api'], // Or anything your app uses, e.g. 'auth:api', or a custom 'welcome-bar-auth'
        'fetch'  => ['web'], // Or 'api'
    ],
];

Optionally, you can publish the views using

php artisan vendor:publish --tag="welcome-bar-views"

Usage

Add this to your layout file (e.g., resources/views/layouts/app.blade.php) after the opening body tag:

  <x-welcome-bar />

or alternatively you can use the blade directive

 @include('welcome-bar::welcome-bar')

Schedule the cleanup command to run in your console routes file

Schedule::command('welcome-bar:prune')->daily();

Data Structure

This package uses a JSON array of “message objects” to display one or more stacked bars at the top of your webpage. The order of the array determines the vertical stacking order: the first element in the array appears at the very top, the second beneath it, and so on.

[
    {
        "message": "Random Message 1",
        "cta": {
            "label": "More info",
            "url": "http://google.com",
            "target": "_blank"
        },
        "schedule": {
            "start": "2025-01-01T00:00:00",
            "end": "2025-01-05T23:59:59"
        },
        "behavior": {
            "closable": true,
            "autoHide": false,
            "autoHideDelay": 5000
        },
        "theme": {
            "variant": "prominent",
            "background": "#0099ff",
            "text": "#ffffff",
            "button": {
                "background": "#ffffff",
                "text": "#82ff38",
                "contrastStrategy": "auto"
            }
        }
    },
    {
        "message": "Random Message 2",
        "cta": {
            "label": "Another link",
            "url": "https://example.com",
            "target": "_self"
        },
        "schedule": {
            "start": "2025-01-02T00:00:00",
            "end": "2025-02-01T23:59:59"
        },
        "behavior": {
            "closable": false,
            "autoHide": true,
            "autoHideDelay": 10000
        },
        "theme": {
            "variant": "subtle",
            "background": "#0066cc",
            "text": "#ffffff",
            "button": {
                "background": "#ffffff",
                "text": "#000000",
                "contrastStrategy": "manual"
            }
        }
    }
]

Field Explanations

message

• Type: string

• Description: The main text shown on the bar. This is required.

cta

• Type: object (optional fields)

• label (string): The text on the button.

• url (string): The link destination.

• target (string): _blank or _self. Defaults to _self if omitted.

If cta.label and cta.url are both provided, a button will appear.

schedule

• Type: object

• start (string, ISO datetime): When this message first becomes visible.

• end (string, ISO datetime): When this message stops being visible.

Messages are only displayed while the current date/time falls between start and end. If you omit these fields, the message is always considered valid.

behavior

• Type: object

• closable (boolean): Whether to show a close (×) button.

• autoHide (boolean): Whether the bar should automatically hide itself after some time.

• autoHideDelay (number): The duration in milliseconds (e.g., 5000 = 5 seconds) before the bar hides if autoHide is true.

theme

• Type: object

• variant (string): Arbitrary descriptor for the style theme (e.g., "prominent", "subtle").

• background (string): Hex code for the bar’s background color.

• text (string): Hex code for the bar’s text color.

• button (object): Further styles for the CTA button.

• background (string): Button background color.

• text (string): Button text color.

• contrastStrategy (string, "auto" or "manual"):

• If "auto", the bar can compute the best contrasting text color based on background.

• If "manual", the text color is taken as-is from text.

How to Update the Data

You can update this JSON array via:

• A POST request to your application’s update route (e.g. POST /welcome-bar/update), or

• Directly saving a JSON file in the configured temporary storage location (depending on your setup).

How Data is Rendered

Each entry in the array is displayed as a stacked bar at the top of the page, in the order provided. The package checks:

Is now() between schedule.start and schedule.end**?**
Is the data valid? (e.g., do we have a message?)

If valid, the bar is rendered with the specified colors, CTA button, and behavior rules.

Tip: If you want to hide all existing bars, simply remove (or empty) this JSON array.

API Routes

Fetch Current Bar Data

Endpoint: GET /api/welcome-bar/data

Description: Fetches the current welcome bar data.

Middleware: Uses the middleware specified in welcome-bar.middleware.fetch.

Response:

200 OK: Returns the current welcome bar data in JSON format.

Update Bar Data

Endpoint: POST /api/welcome-bar/update

Description: Updates the welcome bar data from an external source.

Middleware: Uses the middleware specified in welcome-bar.middleware.update.

Request Body:

Content-Type: application/json
Body: JSON array of message objects.

Response:

200 OK: Returns a success message.
400 Bad Request: Returns an error message if the request is invalid.

Ping

Endpoint: GET /api/welcome-bar/ping

Description: Pings the site to check if the welcome bar is installed.

Middleware: Uses the middleware specified in welcome-bar.middleware.fetch.

Response:

200 OK: Returns a success message indicating the welcome bar is installed.

Testing

composer test

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

The MIT License (MIT). Please see License File for more information.

daikazu / welcome-bar

Maintainers

Details

README

Installation

Usage

Data Structure

API Routes

Fetch Current Bar Data

Update Bar Data

Ping

Testing

Changelog

Contributing

Security Vulnerabilities

Credits

License