[dangerface]

Good question. I like perch its quick and easy to build with, I moved from wordpress to perch last year and it has cut development time in half.

It's super flexible no need for dodgy third part plugins that's no longer maintained. Instead of plugins I just build everything I need custom with the tools perch provides, I end up with something thats perfect for the client and its a lot faster than trying to modify some third party plugin.

Clients are initially scared of perch, they want wordpress because thats what they are used to and "thats what every one else uses". Five minutes into their perch training their attitude is "This is great. Why does every one else use wordpress?".

Sure its not free like wordpress but its only £50 and its worth every penny, you will easily make that money back in development costs in a day.

https://grabaperch.com/

[mercer]

I use Wordpress + ACF Pro, without any extra ACF 3rd party plugins. I also write all the front-end stuff that interfaces with ACF.

With that in mind, what would be the biggest timesaver(s) of using Perch?

[SippinLean]

>an open-source CMS

[dangerface]

It meets the original definition of open source as in the source code is open and modifiable, you know the opposite of closed source.

If you mean the OSI definition of open source which defines how free the licence is, rather than how open the source code is then I suggest you check out the FSF they are the original OSI and advocate for free software and generally don't feel the need to change an existing definition and make it theirs.

[FlipperPA]

I don't believe it is "open" - although you have the code to modify, the license will make it very clear that it is anything but "open."

[dangerface]

If you have the code to modify then its open source, thats all that open source is it has nothing to do with the license unless you are talking about an OSI license in which case its just an OSI license and nothing to do with the source code or its openness.