Hi All. I was wondering what is the preferred way to build pages in Twill? Would each page be a capsule? Or a pages module? I think the module is overkill for client work as they should not really need to add pages directly especially when all pages are super custom (css) I see there is a homepage capsule in the twill github, but was wondering if there was anything to build that homepage as well as others in a similar way where each page gets their own form field

Hi @User! There are many ways to go about it, check out this thread which should help: https://github.com/area17/twill/issues/54#issuecomment-433988352

Great Thanks, will have a read 🙂

Also helpful: https://spectrum.chat/twill/help/pages-how-to-examples~18c5242c-80d8-4f16-b674-45a526ebcc7b?m=MTU4NDUyNTM3MDA2OA==

I think best approach is from the github discussions above and save a page template and do the logic based on that. Can make the template map to a blade layout too.

yep, we do that often. when the page is really bespoke in the CMS and has a lot of fields and/or relationships, we don't hesitate to use a dedicated table, like in the Homepage capsule, but if they share most of their fields, a model/table for multiple pages is totally fine.

nice 🙂 Agree here, Home pages are usually more bulky as well as landings etc. But privacy policy etc is simple enough for this approach

you can hide/disable functionality for your clients on a module too, if you still wanted to show a listing of pages instead of explicitly adding the form link to your nav

say you have a couple of "generic detail pages" for legal pages and so on, you can still have a listing of those in the CMS but disable create and delete.

yeah I noticed that already, we would disable create and delete for granular control. this way only a seeder/custom code can build a page. Clients shouldn't be allowed the option 😅

exactly

I noticed a bug on creating capsules

Added in github here

I wonder if this is still a newish feature?

thanks! looking into it. so you responded yes to all except translations?

it is! just released it

Here is my ouput 🙂

I think this feature is a game changer 🙂 especially when the --require is done too

modules are more mature, though capsules rely on the module architecture, they are kind of an organizational pattern on top of them, to make them shareable/installable. The bug you have shouldn't be on a module, it seems to be only on capsules.

totally! Props to @antonioribeiro 🙂

Yeah this is correct, on a module it works well. on capsules it does not. Idea here is that we can install the pages capsule on multiple projects and update the capsule only (once it is tied to git naturally) modules work great, however a small update on one module means an update on all projects which can get messy if I start making money again lol

But I guess this is just teething for the new feature 😄

totally hear you, we have the same goal with them

Noice! I will fork the package and take a dive in, perhaps I may contribute 😄

awesome

Thank you @User

Hi so I've got an issue with repeaters working since upgrading to 2.2 . You can see from this image how a repeater now looks after the upgrade. The form elements within the repeater just don't appear.

Hi @AdamCord, yeah I see. Can you share the name of the blade file for that repeater, and the repeater item config array from twill.php?