Pierre-Luc

Nice trick! Yeah my use case was to show last updated images from a specific page mixed with a bunch of other "regular" pages, couldn't seem to get it working. Also there was some pain in merging both arrays (didn't seem compatible), plus sorting with dates on different field names (native created + custom date for some of the content) at the same time.

This, and hopefully pageimage at the same time. Got bit a little last week.

I do multi language websites all week long in PW, what exactly do you think is missing?

To be honest, the level of flexibility and structure freedom in PW is not something you'd really understand at first, especially coming from the likes of WP, Joomla or whatev'. You only really get the feel of it when going to production with it.

That would be a welcome addition on my part too. If you add this request to GitHub let me know so I can vote on it.

I just pushed version 1.0.3. This version introduces a new option: "Do not detect language if GET parameter is set". You can now set a GET parameter to prevent language redirection on some requests with this parameter. For example, if this parameter is set to "nodetect" and the user requests "http://example.com/de/?nodetect", the plugin will not redirect the user to the user's preferred language or fall back to default.

I'd really be interested to know how complex your ProcessWire "schema" is, if you will (mapping of templates/fields). That's surprisingly small!

For those interested, I have put my vector and bitmap versions on my (way-too-in-progress) website: http://plauclair.me/processwire/logos/

The Google Trends analysis IMO isn't of much help, it doesn't show the inherent "value" of PW as a CMS/CMF, it just throws hard to analyze numbers at the wall. In sheer numbers, WordPress should be the "B357 3V4R" solution out there. WP also benefits from having a LOT of marketing and PR involved, which the PW community doesn't really have (yet?). Look at the ecosystem around Laravel.. Laracasts, dedicated podcasts and blogs, training sessions and communities all over. It didn't get to be known with no effort, there has been a lot of time (and money?) put into it, the creator and his team have explained this numerous times. On another note, I actually have a two-pager to introduce PW to clients, unfortunately it's in French and heavily branded and I don't have much time to translate it right now. But it might be of interest. The main selling points I see and discuss in it — and I'd be very interested to know what's your opinion on this and what has worked well or not so well for you — go like this: Ease of use (for users and devs alike) — self documentation, data validation, fast development cycle Extremely fast — w/o caching, it's fast. With caching, it's fast as hell. Still need moar speed?! Throw ProCache at it and bingo! Static websites with all the benefits of a dynamic system and none of the pain of static generators. And fast websites mean better SEO, better visibility and better conversion rates! Win-win-win! Scalability — Does small and large scale sites really well. Hierarchical structure, when necessary, make it easy to manage content (plus it's built-in search system). Stability and security — Costs less to maintain and isn't very prone to attacks due to its inherent architecture. You don't need to update it every other day. Efficient development — Up to date development paradigms, easy to maintain and develop with growth in mind, content "agnostic" (i.e. it not targeted at one kind of use/market). Most things are already in core, no need to extend the core to do things I consider basic in this day and age, and pay annual fees for them on top of that.. I prefer to invest that time and money helping PW the best I can, that's how open source is best IMO. Relational content — It's hard to explain to clients, but it's seriously what generally cuts in when I need to select a platform for a client and really, PW wins hands down on this. Everything is a page and a page can be related to any other page in the way that pleases you. This enables really powerful contextual information, advanced "member" sections and such. I think that sums it up, then I usually add one or two paragraphs at the end that describes further why PW is a good choice for this project. Most of these arguments have been working well so far.

Actually, it's very easy to clear cache for a whole website. In cache settings, for a page, you can select to clear the whole site at once when you save that page. I will typically set that on the home page, because nothing ever gets changed on that page, it's just a template that will pull data from other templates. Whenever I need to force a cache reset, let's say after modifying some code that won't automatically be shown, I'll just save the front page to force a full website refresh.

Adding to todo and required fees : - WP Vulnerabilities Maintenance Tax

It's still something I want to get going, but recently I've had pretty much no time for myself. Between moving, the job and other things, I'm pretty late on most things. More pairs of hand would definitely be a plus.

That's pretty cool! Yep the special need is indeed modes.

Thanks a lot for your input, I'll find a way to make it happen. My use case is a bit different though, and GD's limited abilities to composite images with modes will probably exclude it, but you give me a good idea how to tackle the problem!

I have an incoming project that will require automatically adding overlays in multiply mode to images uploaded by the clients. Would you say it'd be easier to use the PHP Gmagick/ImageMagick classes on PW's size() output or go all in into extending the PageImage class? I'm kind of concerned on how to approach caching in this case.. If you have any pointers from your experience, I'm a taker!

@BernhardB, yup, the PR I submit on database creation that Ryan accepted is directly linked to making the setup much, much faster. I'm still looking into Vagrant and/or Docker automatic setups, but time being limited, it's still far from being there.

Thanks for letting me know @OrganizedFellow!

This is the organization we've put in place at work. The structure is pretty much fixed now, we're still grabbing parts of things we like elsewhere. It's basically a bootstrap kit. Workflow goes at this : 1) clone latest pw and setup project with https://github.com/plauclair/pwscripts 2) clone our site profile 3) remove extra, configure grid or else from less mixins, select which layout to use and import html presets that match these 4) marvel at all the time saved 5) code 6) ?? 7) happy customers, happy devs! templates/ |-- styles/ | |-- styles.less // general styles, calls parts in inc/ | |-- styles.css // compiled from styles.less | |-- inc/ | | |-- layout-one-pager.less // standard layouts | | |-- layout-standard.less | | |-- content.less // regular h1, p, ul, etc.. | | |-- template-name.less // each template has its own less file | | |-- template-...less | | |-- vendor/ // decoupled parts from different frameworks | | |-- bootstrap/ | | |-- grid.less // decoupled grid system, generator w settings | |-- images/ // images called from css | | |-- scripts/ | |-- main.js // main js stuff for global things | |-- vendor/ | |-- vendor-name/ | |-- files... | | |— inc/ // php includes, has ready-made classes like a recursive menu generator and other helpers |-- views, controllers, classes, etc../ // depends on the project's complexity | |-- _header.php | _init.php // config->prepend |-- template-name.php // typical PW template files |-- template-...php

You can now download it from GitHub ! Click here!

@LostKobrai, well in general terms type hinting is a good sanity check when developing anything remotely complex. The fact that you can hint any class but not string, arrays, int or else has always been an annoyance of mine (not passing the right type will give a fatal error). Most of these are niceties I agree though. I'm mostly excited to run benchmarks on non cached PW instances. Can it really get any faster ? Will the page load before even clicking links ? ;P

Hey guys! You probably have been following the recent announcements regarding the next PHP version, 7.. I'm pretty excited about scalar type hinting, return type declarations (although void didn't pass ) and much improved performance! What are you most looking forward to, what are you sad isn't there? Some extra reading: - PHP RFCs — https://wiki.php.net/rfc/howto - Fun little infographic from Zend — https://pages.zend.com/TY-Infographic.html

To do that use my super awesome AutoDetect Language module! Does that automagically for you!Sorry no link, writing from my iPad.

ProcessWire is mostly a model with handy functions attached to them. You provide the views and the controllers. Simple as that. You can do what the heck you want with it. If you want to make a page have multiple possible states, suit yourself, it's possible. That being said I think we're being trolled and falling pretty hard for it.

Sure thing, it's pretty much the same for me.

I'd say, first let's set common goals; what do we want to achieve at the end of this. Then after that make a roadmap of what order we should tackle things, define how we share the work that needs being done. I would really like more input on what people want to see in the docs, we can probably use the forum and search for the most popular discussions for that, but there are limitations to this. Some topics have barely been discussed so it's hard to say apart from personal experience.