What I find so nice is that it makes developing JSON based AJAX API:s and traditional "untemplates"* in pure PHP equally easy.
For an AJAX API, just a few ProcessWire API calls and JSON serialisation, and for PHP "untemplates", just drop in your HTML/CSS/JS design and intersperse a few lines of ProcessWire API calls here and there, and off you go.
To me, this is as close you'll come to both the designer and the developers dream, in one simple system.
Sure, you can build technically more performant systems with Node or Go, but I think that is overkill for 90% or more of websites out there, which simply needs flexible content modeling, and flexible design, paired with a flexible API for any corner cases, and integrations with other systems.
Re:ProcessWire: CMS with a jQuery inspired content API
by MatthewSchenker on Wednesday October 07, 2015 @09:57PM
(#10350426)
ProcessWire is the most natural and intuitive PHP framework and CMF I have ever used! And the development community around it is amazingly friendly and knowledgeable, and always ready to help you learn.
Re:ProcessWire: CMS with a jQuery inspired content API
by clsource on Wednesday October 07, 2015 @04:18PM
(#10348775)
processwire is awesome. I made an intranet system with more than 2K users and shines. ever after 1 year in full usage with 2 mobile apps and a website making queries to the system.
Re:ProcessWire: CMS with a jQuery inspired content API
by hliyan on Wednesday October 07, 2015 @08:39AM
(#10345597)
PHP promises? I can't quite put my finger on it, but this makes me feel very strange. As if they're not supposed to exist or something. I hope someone can articulate the reason (if there is one) better than me...
https://processwire.com/api/concept/
What I find so nice is that it makes developing JSON based AJAX API:s and traditional "untemplates"* in pure PHP equally easy.
For an AJAX API, just a few ProcessWire API calls and JSON serialisation, and for PHP "untemplates", just drop in your HTML/CSS/JS design and intersperse a few lines of ProcessWire API calls here and there, and off you go.
To me, this is as close you'll come to both the designer and the developers dream, in one simple system.
Sure, you can build technically more performant systems with Node or Go, but I think that is overkill for 90% or more of websites out there, which simply needs flexible content modeling, and flexible design, paired with a flexible API for any corner cases, and integrations with other systems.
* (no need for a template language)