We're actively working on that https://github.com/area17/twill/issues?q=is%3Aissue+label%3A%22type%3A+documentation%22+is%3Aclosed+sort%3Aupdated-desc

Also this may help https://twill.io/docs/api/2.x/

No problem! I know that sometimes it can be hard to get behind.

Devs enjoy reading docs, not writting them lmao 😄

its not too bad to write them I think

it helps when writing code sometimes as you figure out you are doing stupid stuff when documenting it 😄

HI, is it possibile tu use a singleton in a secondary_navigation? i'm trying to

'pages' => [
        'title' => 'Pages',
        'route' => 'admin.pages.pages.index',
        'primary_navigation' => [
            'pages' => [
                'title' => 'Pages',
                'module' => true,
            ],
            'homepage' => [
                'title' => 'Homepage',
                'singleton' => true,
            ],
            'markets' => [
                'title' => 'Markets',
                'module' => true,
            ],
            'solutions' => [
                'title' => 'Solutions',
                'route' => 'admin.pages.solutions.index',
                'secondary_navigation' => [
                    'solutions' => [
                        'title' => 'Pages',
                        'route' => 'admin.pages.solutions.index',
                    ],
                    'callToActions' => [
                        'title' => 'Call to Action',
                        'module' => true,
                    ],
                    'pageSolution' => [
                        'title' => 'Archive Page',
                        'route' => 'admin.pages.solutions.pageSolution.index',
                        // 'module' => true,
                    ],
                ],
            ],
...

Route::group(['prefix' => 'pages'], function () {
    Route::module('pages');
    Route::singleton('homepage');

    Route::module('solutions');

    Route::group(['prefix' => 'solutions'], function () {
        Route::singleton('pageSolution');
        Route::module('callToActions');
    });
    Route::module('markets');
});

callToActions works pageSolution return error** Route [admin.pages.solutions.pageSolution.index] not defined.**

you don't need the .index suffix with singleton, and you can use

'singleton' => true

without using

'route'

my mistake 🙂

How can I Add a custom css to edit something in admin ?

i do not want to publish vendor with php artisan vendor:publish --tag=twill

Hi @User, you can inject custom CSS in your

form.blade.php

like this :

@push('extra_css')
    <style>
      ...
    </style>

    /* or */

    <link rel="stylesheet" href="...">
@endpush

any way to set this globally?

@push('extra_css')
    @if(app()->isProduction())
        <link href="{{ twillAsset('css/custom.css') }}" rel="preload" as="style" crossorigin/>
    @endif
    @unless(config('twill.dev_mode', false))
        <link href="{{ twillAsset('css/custom.css') }}" rel="stylesheet" crossorigin/>
    @endunless
@endpush

i do not need this only in form view

I think a simple solution to have this globally is to override only the

head

view from Twill. Github seems down at the moment, but essentially you can copy this file:

vendor/area17/twill/views/partials/head.blade.php

to:

resources/views/vendor/twill/partials/head.blade.php

Then add your custom styles below the

@stack('extra_css')

line

Maybe there's a more clever solution without any overrides, but I can't really think of one...

thank u!

Hi! My frontend is located in another project and I want to make the link from the CRUD module lead there. Can you tell me how to change this link in the CRUD module?

Hi @Gvido Blue Fox! You can use

customPermalink

in your

formData

, or override

getPermalinkBaseUrl()

.

in your module's controller

Thanks!

Any way to load content part in closed state? Like this

What I did to achieve that was to disable it and create my custom Content section

php
// form.blade.php
@extends('twill::layouts.form', [
    'disableContentFieldset' => true,
])

@section('fieldsets')
    <a17-fieldset id="content" title="Content" :open="false">
  //...
</a17-fieldset>
@stop

It worked like a charm, thanks. 🙂

Hello, I am trying to get settings in helpers like the photo bellow. I want that when user hasn't translated the fields to return the fields in default language.

Hi @zoi, I would recommend checking the documentation of the package that is underlying twill for translations. there are a lot of different approaches you could take. https://github.com/Astrotomic/laravel-translatable

There was a question recently about fields not being rendered. Anyone know what it was? 😄

happens on prod, not local. No errors in laravel log nor console.

@Harings Rob for @kalle it was a syntax error in the markup due to dynamic form fields labels

in my case it has something with translatable locale on inputs and labels. 😄 Sorry but I didnt debug it fully. But for my use case, it was dynamic inputs and labels so it was expected that something like that happens