Hi, our company is planning to build a new tool for content management and it's going to be used a lot. It will need a lot of customisation and we are planning to use it for a long time. We are currently choosing between twill v3 and statamic. Statamic looks like a more mature product with paid long term support compared to twill and statamic has a code coverage close to 100%. So on paper statamic sounds like a better choice. Maybe you guys have experience with statamic and maybe there are some limitations which are not aparent with twill? Would love to hear some opinion. Maybe working with statamic is hard or something. We will be using database of course, nothing will be static, so we don't need these static pages and caching features from statamic, but what I can see from documentation statamic works great with databases too and I hope it can be as dynamic as twill. e.g. I hope we will be able to render each page block with custom php code and tailor block experience based on customer data. Anyway, hope you can help us to make this big decision as we will be willing not only to use this software but also to contribute to this community.

Hi @Aidas (KasValgyt) creating a thread for this discussion. My opinions are biased as the creator and maintainer of Twill, so I'm hoping that community members will share some feedback with you too in this thread. Give me a moment to get back to you later today, but I'll say one thing now: Statamic is a great product, no doubt, but, 1. it is not free, 2. it uses its own templating language (Antlers) that only Statamic uses (you're not forced to use it, but a lot of resources about Statamic are), 3. the eloquent driver (used in their database approach) only reached 1.0 a couple months ago and has quite a few issues, because Statamic was initially built only for the static files use case.

Thanks ifox for all this input, greatly appreciated! Can't wait to hear more.

Hey @Aidas (KasValgyt) regarding customizations Twill is very open. It is your Laravel application and you can use any composer package. The whole frontend can be customized with Vue.js or vanilla JS, or even Alpine or Livewire if you're into that, you can create new form fields, etc... Regarding code coverage we have made immense progress in the past 2 years, and Twill 3 is now covered by a lot of end to end browser tests with Laravel Dusk. We even exposed test helpers for your own Twill modules tests. Statamic and Twill share a lot of awesome features in regards to content editing, like live previews and image cropping, though I would qualify Twill as less opinionated and more open to a fully custom CMS organization. Twill also doesn't use a "proprietary" format to store configuration, everything is controlled through code with Laravel provided features, allowing you to structure your code, use dependency injection, etc... as you see fit. Regarding long term support, we are very active here and on GitHub, and are here for the long run. Twill was created in 2016, open sourced in 2018, and we have invested a lot since then, with the upcoming Twill 3 being our biggest release since launch. We have a lot of ideas in the roadmap and will continue maintaining and improving it for years to come. The community is growing every day and we can't wait to have thousands of people in this space. Now, I don't think Statamic is hard to work with and it is a great product overall, so the decision is really up to you in the end, but know that we will always be there to answer your questions regarding customizations and will be excited to bring your ideas into the product if we feel like everyone can benefit from them.

Thanks a lot @ifox, I do feel stronger now with this decision. We already started building our product based on twill and we are planning to incorporate some really fancy features to it.

awesome! I'm curious to hear more about / see what you're building