ProcessWire CheatSheet Poll - How much do you use it?

[Soma]

Yah! First poll!

For fun, but also seriously...

[MadeMyDay]

rhetoric question ;-)

[Pete]

Well somewhere between not that much and every day. Maybe a few times a week.

After a while some of it sticks (or so I tell myself), so I don't ened to refer to it all the time

It is invaluable though for when I draw a blank and want to check whetner I can do something a certain way.

[apeisa]

You have pretty extreme options soma I'd say few times in a week and I most often find what I was looking for very fast. Great resource!

[slkwrm]

Usually use it a couple of times a week and find it extremely helpful! Thanx, Soma.

[arjen]

Same here. Couple of times a week it comes in handy!

[tiagoroldao]

Extremely helpful! Between that and the ocasional thread searching in the Forum, I'm basically set!

[Martijn Geerts]

The cheatsheet was one of the things what really grabbed my attention. And get me really interested in Processwire. These weeks I promoted Processwire on my job & the next website to build will be with PW. Big thanks for putting the sheet together!

BTW is there a reason why "$user->language" is not on the list ? ( or do I say something weird )

[Soma]

Thanks for the post Martijn. Glad to hear it serves its purposes.

One reason it's not in there, is because language support was still in development and moreover it's not core, it's a third-party module and need to be installed (although it's in the distribution). There's couple things not in the cheatsheet that are not permanent modules i.e. like the comments, pager etc.

I'm not sure if those distributed modules should be added somehow or make a separate sheet. What you guys think?

[diogo]

maybe they can be there filtered, just like the advanced things

[apeisa]

Thanks for the post Martijn. Glad to hear it serves its purposes.

One reason it's not in there, is because language support was still in development and moreover it's not core, it's a third-party module and need to be installed (although it's in the distribution). There's couple things not in the cheatsheet that are not permanent modules i.e. like the comments, pager etc.

I'm not sure if those distributed modules should be added somehow or make a separate sheet. What you guys think?

I wouldn't say that language support is a third-party module. I think all modules that come by default are core modules (some of them permanent, some of them installed by default and some of them not installed by default).

I think language stuff should be in cheatsheet, but not sure about things like comments, pager etc.. Probably the more the better!

[Pete]

I think comments and pager should be too - they'd both be useful or blog/news/magazine sites and that's a large portion of the web right there.

Although if there are lots of things to add for these core modules then perhaps they should go under a separate page for modules, and maybe separated by module type?

Might be getting a bit too complicated there but it's an idea.

[tiagoroldao]

Extra information on the cheatsheet would be nice, and in terms of complicating the experience, I really don't see any problems - I agree with Diogo:

maybe they can be there filtered, just like the advanced things

The only issue I can think of is when/where to stop (i.e. which modules are worth keeping, and should one even make that judgement) /how to add information... But I would love to have even third party modules not in the distribution acessible - provided they don't overcomplicate the cheatsheet - filters that could be off by default, maybe?

Afterthought: would it make sense for someone who make a third party module to submit entries to the cheatsheet? This may be completely off, and ruin the whole concept of the cheatsheet, i dunno.. Just tossing out ideas

[Pete]

Might be easiest to have them on a drop down so it switches to a module-specific cheat sheet page.

That said, now I think about it there aren't all that many modules that would have more than a handful of cheat sheet functions anyway.

[Martijn Geerts]

Where to stop is a good question, maybee to stick with what is delivered with the core & what is preinstalled, filtered like how the is "advanced" is filtered. Never the less, what is already shown in the cheatsheet is impressive.

[Soma]

Thanks guys. Originally I had some special stuff in there and things like pager etc. , but because Ryan had some gripes with it, I removed it. So I'm interested what Ryan thinks too.

[apeisa]

I would say it is another cheatsheet or then just another tab/page on the current one. It have to be very clear what stuff is part of the API and what are from modules.

[Pete]

Could even have a different colour scheme for modules to avoid confusion (thus creating more work because that's just what Soma needs ).