brightly/mango-core

The Mango CMS's core functionality to be able to work alone without admin UI.

v1.1.0 2021-11-11 10:18 UTC

Requires

• php: >=7.1.0
• facebook/graph-sdk: ^5.7
• spatie/eloquent-sortable: ^3.8
• spatie/laravel-medialibrary: ^7.0

Requires (Dev)

• doctrine/dbal: ^2.10
• orchestra/testbench: ^5.2

proprietary

• Balázs Ercsey
• Egon Stefán
• Rebeka Zsákai
• Tímea Tóth

README

Mango Nova ("Next Summer" edition)

Intruduction

Install

As you started your project with brightly/mango-starter Mango Core is added to your composer.json, and prepared to use.

Migrations

To migrate Mango's files, first you have to publish migration files.

artisan vendor:publish --tag=mango-core-migrations

...and then migrate:

artisan migrate

Usage

Basic build blocks

Mango Core provides Menu, structure of Links and Content binded to that.

Menu

Menus are "placeholders" for Link trees in templates. Menus can be shown in the templates like this:

@componentfirst($menu->templates('main'), ['menu' => $menu->menu('main')])
...
@componentfirst

Links

Links provides URLs for pages. So page itself is not exists in Mango, a page provided by a Link and a Content object. The link describes the URI and handles publishing information.

Content

Provide content of a given page.

Frontend

Homepage (a.k.a Main Page, or Welcome Page)

You can set up a "page" - a Link and a Content - for that. The link's slug will be de identifier of the current page. After that, you can use the identifier of the link in the config file.

array(
    ...
    'routes'    => [
        'index' => 'your_link_slug'
    ],
    ...
);

Contribution

After updating this project, you should rebuild private packages index! Please check this!

License

All of the Brightly projects licensed under propietary license.