https://github.com/tina4stack/tina4-cms

CMS module for Tina4
https://github.com/tina4stack/tina4-cms

Last synced: about 1 month ago
JSON representation

CMS module for Tina4

• Host: GitHub
• URL: https://github.com/tina4stack/tina4-cms
• Owner: tina4stack
• Created: 2020-11-16T23:17:02.000Z (about 4 years ago)
• Default Branch: master
• Last Pushed: 2024-04-25T07:38:18.000Z (9 months ago)
• Last Synced: 2024-04-25T08:39:15.324Z (9 months ago)
• Language: JavaScript
• Size: 27.1 MB
• Stars: 5
• Watchers: 2
• Forks: 17
• Open Issues: 6
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Tina4 CMS Module

Welcome to the Tina4CMS module, how does it work?

```

composer require tina4stack/tina4cms

composer exec tina4 initialize:run

```

Sqlite is recommended for small to medium websites

```bash

composer require tina4stack/tina4php-sqlite3

```

Add the database connection to your index.php file which would have been created

```

require_once "vendor/autoload.php";

global $DBA;

$DBA = new \Tina4\DataSQLite3("test.db","", "", "d/m/Y");

echo new \Tina4\Tina4Php();

```

Run the CMS

```commandline

composer start 8080

```

Open up the CMS to set up the admin user

http://localhost:8080/cms/login -> will get you started

### The Landing Page - home

You need to create a landing page called "home" as your starting page for things to working properly.

### Customization

Make a  *base.twig* file in your */src/templates* folder, it needs the following blocks

```

    {{ title }}

    

    

    

    

    

{% block headers %}

    

{% endblock %}

{% block body %}

{% block navigation %}

    {% include "navigation.twig" %}

{% endblock %}

{% block content %}

{% endblock %}

{% block footer %}

{% endblock %}

{% endblock %}

```

or an example which extends the existing base in the tina4-cms

```

{% extends "@tina4cms/base.twig" %}

{% block headers %}

    

{% endblock %}

{% block body %}

    


{% block navigation %}

    {%  include "navigation.twig" %}

{% endblock %}


{% block content %}

{% endblock %}

    


{% endblock %}

```

#### Example of a navigation.twig which you can over write

Create a *navigation.twig* file in your *src/templates* folder

```

{% set menus = Content.getMenu("") %}

    


        {% for menu in menus %}

            


{{ menu.name }}

                {% if menu.children %}

                    


                        {% for childmenu in menu.children %}

                            


                                {{ childmenu.name }}

                            

                        {% endfor %}

                    

                {% endif %}

            

        {% endfor %}

    


```

### Including your snippets in the CMS

 

There are two ways you can do this:

When you want to include content as it is, and not have the snippet parsed with Twig you can simply use the following:

Use the raw filter when you want to have scripts or other things included correctly

```

{{snippetName | raw}} or {{snippetName}}

```

The following is how you would include a snippet where you want variables in the page for example parsed in the snippet

```

{{ include(getSnippet("snippetName")) }}

```

#### Example:

Page content of "home"

```

  {% set world = "World!" %}

  

  {{ include (getSnippet("mySnippet")) }}

```

Snippet content of "mySnippet"

```

  Hello {{world}}!

  

```

Adding articles into a page

```

{% set articles = Content.getArticles ("", 8) %}

{% for article in articles %}{% include "snippets/medium.twig" with {"article": article} %}{% endfor %}

{% set params = {"tag": "all", "skip": 4, "limit": 4, "template": "medium.twig"} %}

{% include "load-more.twig" with params %}

```

Overwriting the default CMS twig namespace - your own namespace

```

CMS_TWIG_NAMESPACE=""

```

## Page Builder

The page builder should implement GrapeJS and allow you to build pages using blocks and components. The blocks and components should be simple to load.

We need to flag off pages that have been edited by the Page builder so the generic CMS does not try to render them.

## Themes

Use with care, this is currently experimental but will be introduced into the CMS at some point as a base for the pages

Current thoughts are as follows:

### Theme Structure

```

src

    templates

        themes

            theme-name

                blocks

                    block-name-1.json

                    block-name-2.json

                components

                    component-name-1.json

                    component-name-2.json

                theme.twig

``` 

The default theme can be cloned to make other themes.

### Examples of extending the CMS Page Builder

In your index.php file where your config is initialized you can define the following.

```php

$config = new \Tina4\Config(function(\Tina4\Config $config) {

    (new Content())->addCmsMenu("/backend/program", "Products"); //Menu example

    $config->addTwigGlobal("Menu", new Menu()); //Adding a twig global class

    (new Theme())->addTwigView("product", "Products", "examples/products.twig"); //Adding different snippets for use in CMS views

    (new Theme())->addTwigView("menu", "Menu", "examples/menu.twig");

}

```