@Shiftless are you seeding the content? Or what do you mean with PageFactory?

yes i was trying to seed a pages for tests

@Shiftless if you want to have twill behaviors when seeding, you need to use the module repository, not the model directly

I was expecting this. means factories are not possible?

By 'pages', you mean module records with slugs or?

yes it has slugs, translations, revisions.

You can check this example if this helps you.

But Im not sure if all features are testable like that

Hi! I'm newbie in twill. I have a question. Do I need create the blade files to the default blocks or twill has a default implementation?

Also good inspiration would be Twill tests.

Twill has 2 default blocks registered in config file which you can also use in your editor.

image

and

text

https://github.com/area17/twill/blob/2.x/config/blocks.php#L22 Block source is here https://github.com/area17/twill/tree/2.x/src/Commands/stubs/blocks

Oh, yeah. I forgot... I mean the site blades not the admin blades.

If you need to create custom blocks for your module, you can follow Twill documentation. All of that is explained there. https://twill.io/docs/block-editor/ Or I didnt understand your question completly. Please be more specific if that's the case. 🙂

I think @Levente Farkas is talking about frontend rendering of the blocks content

there are no defaults for that

Thanks, I get it now, its more clear to me what he wants to achive haha

Yes, exactly. Sorry for the mistake.

In twill 3.x you can generate dummy preview files, but you still need to update them to your needs.

Some days ago I discovered Twill, and I must say, Wow ! I am in a process to experiment with 3.0 beta to try to build my needed cases. One piece is not easy. For the project I need the role translator: this role can edit text or textarea inputs in one language only, but "nothing else". Is this doable with configuration and templates or does it require deep re-engineering?

Hi @KUS! very valid use case and I think achievable by config/templates customisation. we'll be happy to support

you could even build modules dedicated to translators on top of your "full" modules

Just want to give my 2 cents here. I've had similiar task in past, which is on 2.8.x version of Twill. On that version module approach was not ideal, since with enabled multilang I couldnt enable specific langs, only all were available. So I went with custom role, with specific option on user profile (admin view) to select languages which he can translate. So with custom pages I was able implement translation dashboard, and on module (admin view) I had an browser which selects specific user which is assigned to that translation task. I really hope that there is some easier way in 3.x with the new permission system to achive this. 🙂

Ok, you believe customisation will do the job.

yeah like @kalle said it's not necessarily easy per se but it is possible.

@kalle i would love to look at this closer with you if you don't mind

I could share that snippets with you, but full project I cant. Company project. 😦

If you could share some snippets it would be great

Maybe I make a package out of it

I have already described logic behind it. Which part you are you interested in?

I read three parts from your explanation: 1) make some input fields accessible and other not based on gate/roles 2) put users into roles 3) generate the roles