Poll archive

1.   Fewer than 10 clients (26.3%, 15)
2.   10-50 clients (50.9%, 29)
3.   50-100 clients (12.3%, 7)
4.   100-250 clients (7%, 4)
5.   250-500 clients (1.8%, 1)
6.   More than 500 clients (1.8%, 1)

Total votings: 57

1.   PHP 8.1 (24.8%, 27)
2.   PHP 8.0 (30.3%, 33)
3.   PHP 7.4 (35.8%, 39)
4.   PHP 7.3 (2.8%, 3)
5.   PHP 7.2 (3.7%, 4)
6.   PHP 7.1 or anything older than that (2.8%, 3)

Total votings: 109

1.   A page builder is my go-to approach for building content (26.5%, 31)
2.   I use a page builder occasionally, on a case by case basis (35.9%, 42)
3.   I have used or had a need for a page builder, but only rarely (12%, 14)
4.   Page builders are not my thing, or not useful for my projects (25.6%, 30)

Total votings: 117

1.   I prefer not to use any front-end framework (20.7%, 31)
2.   Foundation – http://foundation.zurb.com/ (5.3%, 8)
3.   Bootstrap – http://getbootstrap.com/ (14%, 21)
4.   Uikit – https://getuikit.com/ (27.3%, 41)
5.   Tailwind – https://tailwindcss.com/ (28.7%, 43)
6.   Something else – please let us know via post comments! (4%, 6)

Total votings: 150

1.   PHP 8.0 (7%, 9)
2.   PHP 7.4 (41.9%, 54)
3.   PHP 7.3 (27.9%, 36)
4.   PHP 7.2 (15.5%, 20)
5.   PHP 7.1 (4.7%, 6)
6.   PHP 5.6 or anything older than that (3.1%, 4)

Total votings: 129

1.   Directly reaching out to prospective clients (5.2%, 5)
2.   Networking with other developers, agencies, and businesses (25.8%, 25)
3.   Search engine marketing and/or other forms of (digital) advertising (2.1%, 2)
4.   Content marketing: videos, blogging, posting guides and e-books, etc. (2.1%, 2)
5.   Direct contacts from potential clients through my own website (16.5%, 16)
6.   Direct contacts to/from potential clients through social media (2.1%, 2)
7.   Contacts acquired through the ProcessWire support forum (6.2%, 6)
8.   Physical location, clients walking straight in (0%, 0)
9.   Freelance marketplaces (3.1%, 3)
10.   Word of mouth (36.1%, 35)
11.   Something else, what? (1%, 1)

Total votings: 97

1.   Can't say that I do – it's been going pretty smooth! (37.3%, 19)
2.   Sometimes, but with a bit of effort it's all good (43.1%, 22)
3.   I do find it a bit difficult – and here's why... (19.6%, 10)

Total votings: 51

1.   Security (10.1%, 46)
2.   Performance (10.5%, 48)
3.   Flexibility – fits different needs and use cases (18%, 82)
4.   Scalability – fits small and large projects alike (9.9%, 45)
5.   Friendly and helpful community (10.5%, 48)
6.   Ease of use for the client (12.5%, 57)
7.   Ease of use for the developer (15.6%, 71)
8.   Steady stream of updates for the core (5.3%, 24)
9.   It's the system that I'm already familiar with (4.2%, 19)
10.   Existing features, such as third party modules (2.9%, 13)
11.   Clients are requesting ProcessWire specifically (0.2%, 1)
12.   Something else, what? (0.4%, 2)

Total votings: 456

1.   Associations and unions (5.6%, 10)
2.   Businesses and companies (32.2%, 58)
3.   Colleges and educational institutions (8.9%, 16)
4.   Governments, public services, and community organizations (7.8%, 14)
5.   Individuals – celebs, politicians, athletes, artists, etc. (17.8%, 32)
6.   Newspapers, magazines, television, or other media (3.9%, 7)
7.   Nonprofit organizations (20%, 36)
8.   Religious organizations (3.3%, 6)
9.   Something else, what? (0.6%, 1)

Total votings: 180

1.   Website design and/or development (23%, 69)
2.   Mobile application development (3.3%, 10)
3.   Custom module development (7.3%, 22)
4.   Graphic design (web or print) (13%, 39)
5.   Hosting and related services (11%, 33)
6.   Customer support (maintenance) (16.3%, 49)
7.   Search engine optimization (SEO) (11.3%, 34)
8.   Advertising and/or marketing (SEM etc.) (4.3%, 13)
9.   Usability and/or accessibility consultation (8%, 24)
10.   Something else – what? (2.3%, 7)

Total votings: 300

1.   $1.000 or less (14.7%, 19)
2.   $1.000 - $3.000 (33.3%, 43)
3.   $3.000 - $5.000 (25.6%, 33)
4.   $5.000 - $10.000 (17.8%, 23)
5.   $10.000 - $20.000 (7%, 9)
6.   $20.000 or more (1.6%, 2)

Total votings: 129

1.   All of my work is tied to ProcessWire! (22.6%, 19)
2.   More than half, but I do other stuff as well (47.6%, 40)
3.   Less than half of my work relates to ProcessWire (14.3%, 12)
4.   I do some ProcessWire work, but it's just a tiny part of my job (15.5%, 13)

Total votings: 84

1.   I'm an employee working for a company (25.2%, 26)
2.   I'm a freelancer working primarily as a subcontractor (16.5%, 17)
3.   I'm self-employed and work mostly on my own client work (47.6%, 49)
4.   I run a business, employing others (6.8%, 7)
5.   I don't currently do any professional ProcessWire work (3.9%, 4)

Total votings: 103

1.   I work remotely full time or almost full time (51.1%, 48)
2.   I work remotely half the time or less on a regular basis (22.3%, 21)
3.   I work remotely sometimes (18.1%, 17)
4.   I don't do any remote work, and prefer to keep it that way (5.3%, 5)
5.   I don't do any remote work, but would like to in the future (2.1%, 2)

Total votings: 94

1.   PHP 7.3 (9.5%, 17)
2.   PHP 7.2 (40.2%, 72)
3.   PHP 7.1 (24%, 43)
4.   PHP 7.0 (12.8%, 23)
5.   PHP 5.6 (9.5%, 17)
6.   PHP 5.5 (1.7%, 3)
7.   PHP 5.4 (1.1%, 2)
8.   PHP 5.3 or anything older than that (1.1%, 2)

Total votings: 179

1.   I don't use JavaScript frameworks, period (8.9%, 11)
2.   jQuery (38.7%, 48)
3.   React (10.5%, 13)
4.   Vue.js (28.2%, 35)
5.   Angular (6.5%, 8)
6.   Meteor (0%, 0)
7.   Ember (0%, 0)
8.   Lodash (3.2%, 4)
9.   Mithril (3.2%, 4)
10.   Backbone.js (0.8%, 1)

Total votings: 124

1.   Page builder is my go-to approach for building new sites (26.4%, 28)
2.   I'd like to build a site based on the page builder concept, just haven't had a chance yet (15.1%, 16)
3.   I'd like to build a site based on the page builder concept, but don't know where to start (12.3%, 13)
4.   In some rare cases page builders could make sense – but usually they don't (31.1%, 33)
5.   Page builders are not my thing, or not useful for my typical projects (15.1%, 16)

Total votings: 106

1.   I am well prepared and have already made all the necessary adjustments (27.1%, 13)
2.   I know what I have to do, but I still have plenty of work to do (39.6%, 19)
3.   I have no idea if, or how, GDPR affects my work or business (25%, 12)
4.   GDPR doesn't have any direct effect on my work or business (8.3%, 4)

Total votings: 48

1.   Freemium model: get lite version for free, pay for a full-featured version (19.5%, 31)
2.   Transaction or one-time fee model: pay one fixed fee to get the module and lifetime updates (28.9%, 46)
3.   Subscription model: pay a recurring fee, usually on a yearly basis, for continued updates and support (13.2%, 21)
4.   Crowd funding: fund the development of a module together with other users, after which the module can be publicly released (18.9%, 30)
5.   Free module with commercial addons: the so-called core part of the module is free, but commercial addons can be bought to expand its features (19.5%, 31)

Total votings: 159

1.   Just enough to make sure that the site works for me and my client (42%, 21)
2.   I try to follow industry best practices and do some light accessibility testing (36%, 18)
3.   I always develop my sites with accessibility in mind and aim for basic WCAG compliance (22%, 11)
4.   I do vigorous testing, use a number of accessibility tools, and always try to follow WCAG guidelines to the word (0%, 0)
5.   I have someone else (in-house or a third party) who can provide accessibility expertise for my projects (0%, 0)

Total votings: 50

1.   Absolutely – it's my primary content editing method! (7.8%, 9)
2.   Sometimes, but I still prefer the admin back-end (35.3%, 41)
3.   No, not really (52.6%, 61)
4.   I use a non-core front-end editing module, such as Fredi (4.3%, 5)

Total votings: 116

1.   Most of my projects depend on custom-built modules (20.9%, 18)
2.   I have, but custom modules are not a part of my typical workflow (29.1%, 25)
3.   I've never really felt the need to build a custom module (10.5%, 9)
4.   I've wanted to, but building a module seemed too difficult for me (15.1%, 13)
5.   I've considered it, but found the documentation lacking (12.8%, 11)
6.   I've considered it, but couldn't find a good example to go by (11.6%, 10)

Total votings: 86

1.   Blank site profile (26%, 47)
2.   Blog site profile (12.2%, 22)
3.   Multilingual site profile (17.1%, 31)
4.   Uikit based blog site profile (2.2%, 4)
5.   Uikit based starter site profile (13.3%, 24)
6.   Non-Uikit based starter site profile (3.9%, 7)
7.   Starter site profile based on another front-end framework (please specify via the comments) (2.2%, 4)
8.   An online installer for selecting additional site profiles (22.7%, 41)
9.   Something else (please specify via the comments) (0.6%, 1)

Total votings: 181

1.   No, never (12.5%, 13)
2.   Have considered it, but haven't done it yet (38.5%, 40)
3.   I have used ProcessWire as a REST API endpoint (17.3%, 18)
4.   I have used ProcessWire as a GraphQL API endpoint (3.8%, 4)
5.   I have used ProcessWire as a custom JSON API endpoint (23.1%, 24)
6.   I have used ProcessWire as an endpoint for some other type of API (please tell more via comments!) (4.8%, 5)

Total votings: 104

1.   I use ProcessWire for my own, non-commercial projects (16.6%, 26)
2.   I work as a freelancer / own my own one-man business (44.6%, 70)
3.   I work for a micro business or non-profit organization (< 10 employees) (16.6%, 26)
4.   I work for a small business or non-profit organization (10-50 employees) (8.9%, 14)
5.   I work for a medium sized business or non-profit organization (50-250 employees) (8.3%, 13)
6.   I work for a large to enterprise scale business or non-profit organization (250+ employees) (5.1%, 8)

Total votings: 157

1.   Shared hosting (43%, 68)
2.   Managed VPS hosting (13.3%, 21)
3.   Self-managed VPS hosting (22.2%, 35)
4.   Managed dedicated hosting (3.2%, 5)
5.   Self-managed dedicated hosting (10.1%, 16)
6.   Cloud based hosting (8.2%, 13)

Total votings: 158

1.   PHP 7.2 (10.9%, 15)
2.   PHP 7.1 (32.6%, 45)
3.   PHP 7.0 (28.3%, 39)
4.   PHP 5.6 (21%, 29)
5.   PHP 5.5 (2.9%, 4)
6.   PHP 5.4 (2.2%, 3)
7.   PHP 5.3 (2.2%, 3)
8.   PHP 5.2 or anything older than that (0%, 0)

Total votings: 138

1.   AMP is great, and I have used it on my ProcessWire projects (3.8%, 4)
2.   AMP is great, but I haven't used it with ProcessWire projects yet (7.7%, 8)
3.   Still trying to decide whether AMP is really worth it (40.4%, 42)
4.   I have decided not to jump on the AMP bandwagon (30.8%, 32)
5.   What's an AMP? (17.3%, 18)

Total votings: 104

1.   I have developed one or more PWAs involving ProcessWire (9.8%, 6)
2.   I have developed one or more PWAs, but not using ProcessWire (9.8%, 6)
3.   I'm interested in developing a PWA, but haven't had the chance yet (57.4%, 35)
4.   I don't really know what PWAs are and/or what one would use them for (23%, 14)

Total votings: 61

1.   Weekly Newsletter (17.2%, 41)
2.   ProcessWire Weekly (31.4%, 75)
3.   ProcessWire News and Updates Blog (23.8%, 57)
4.   News & Announcements at the ProcessWire Support Forum (10.9%, 26)
5.   ProcessWire Twitter account (12.6%, 30)
6.   ProcessWire Facebook group (4.2%, 10)

Total votings: 239

1.   Simpler Repeater Creation via API (processwire-requests #95) (5.8%, 8)
2.   Tab support inside repeater items (processwire-requests #93) (3.6%, 5)
3.   Add mime-type checks to WireUpload (processwire-requests #88) (0.7%, 1)
4.   Simultaneous page editing capability (processwire-requests #23) (4.4%, 6)
5.   Add official support for nginx (processwire-requests #7) (8.8%, 12)
6.   Group fieldtype that allows sharing groups of fields between templates; similar to Repeaters, but without repeating or the need for separate pages behind the scenes (9.5%, 13)
7.   Changelog support in ProcessWireUpgrade module (8.8%, 12)
8.   LDAP / Active Directory integration (3.6%, 5)
9.   Strategy for flexible content types in a template (https://processwire.com/talk/topic/7477-strategy-for-flexible-content-types-in-a-template/) (7.3%, 10)
10.   Image Compression Engine / System in Core, that is open and simple to extend for 3party modules (3.6%, 5)
11.   Uikit 3 Admin Theme (6.6%, 9)
12.   WebP support (0.7%, 1)
13.   Multilanguage Image fields (0.7%, 1)
14.   A clean and ready module for login, logout, and registration with and without social login (2.9%, 4)
15.   Category or tagging system across pages, not just tagging for images (0.7%, 1)
16.   Simple user management as part of the core installation for creating/maintaining user accounts, and members-only content. Sign up, login, logout, update password. Also, exporting/importing users. (5.1%, 7)
17.   Extended search capabilities to include the content within files, improving ranking and relevancy factors. Since GCS is going out some of us are left looking at difficult options like elastic search etc. (1.5%, 2)
18.   A robust system for publishing changes from one PW instance (e.g. staging) to another (e.g. production) (2.9%, 4)
19.   Completely custom Admin which is built to be lightweight, rather than using loads of external plugin's such as jQuery UI. (0.7%, 1)
20.   Ability to configure any custom permission to be added/revoked at the template level (1.5%, 2)
21.   Simple forum module (2.2%, 3)
22.   Using a field across templates and when updated in one page will updated in all pages. This should be possible for any kind of field. (0.7%, 1)
23.   2 Factor Authentication (0.7%, 1)
24.   Data structure migrations (0.7%, 1)
25.   Ability to select a region within an image without cropping, so we can implement an ImageFocus Area function (0.7%, 1)
26.   Something else, what? (15.3%, 21)

Total votings: 137

1.   I have already participated, and would definitely do it again (4.3%, 4)
2.   I haven't had the chance to participate yet, but would like to (38.7%, 36)
3.   If there was one, I would seriously consider participating (49.5%, 46)
4.   Meetups are really not my thing, so I'd probably pass (7.5%, 7)
5.   I have already participated, but wouldn't do it again (0%, 0)

Total votings: 93

1.   I'm a designer with basic development skills (21.3%, 19)
2.   I'm a developer with some basic design know-how (43.8%, 39)
3.   I specialize in content marketing or search engine optimization (0%, 0)
4.   I'm a sysadmin at heart, managing servers makes me feel all warm and fuzzy (2.2%, 2)
5.   None of the above – I am a leader, project manager, or involved in some other way (0%, 0)
6.   You can't put me in a box – I do a bit of this and that, and I do it all more than well! (32.6%, 29)

Total votings: 89

1.   Fieldtypes or inputfields: modules that add new or improved ways to store and input data (25.9%, 50)
2.   Markup generating modules: modules that produce visible output on the site – carousels, galleries, forms, feeds, and so on (8.8%, 17)
3.   Admin helpers, enhancements, or extensions: modules that extend the admin tools of ProcessWire with new or improved features (17.1%, 33)
4.   API level utility modules: modules that add useful features to the API of ProcessWire, without automatically generating any markup (11.9%, 23)
5.   Modules that run on the background, adding to or improving ProcessWire's existing features: mailers, schedulers, backup tools, etc. (12.4%, 24)
6.   Access or permission management: modules that add new ways to manage users and their permissions, limit access to the site, etc. (9.3%, 18)
7.   Development tools: modules that add tools intended mainly for developer use – migration and importing tools, debuggers, and so on (14.5%, 28)

Total votings: 193

1.   3.0 (54.8%, 80)
2.   2.8 (13%, 19)
3.   2.7 (14.4%, 21)
4.   2.6 (6.2%, 9)
5.   2.5 (5.5%, 8)
6.   2.4 (3.4%, 5)
7.   2.3 (2.1%, 3)
8.   2.2 (0.7%, 1)
9.   2.1 (0%, 0)
10.   2.0 (0%, 0)

Total votings: 146

1.   ProcessWire is my only game (35.3%, 53)
2.   WordPress (23.3%, 35)
3.   Drupal (3.3%, 5)
4.   MODX (8%, 12)
5.   ExpressionEngine (2%, 3)
6.   Craft CMS (4%, 6)
7.   Bolt CMS (0.7%, 1)
8.   Concrete5 (1.3%, 2)
9.   Joomla! (4.7%, 7)
10.   Kirby (3.3%, 5)
11.   Grav (4.7%, 7)
12.   Liferay (0%, 0)
13.   Sitecore (0.7%, 1)
14.   SharePoint (2%, 3)
15.   Something else – please let us know via post comments! (6.7%, 10)

Total votings: 150

1.   I don't really use ProcessWire, I'm just an interested bystander (3.2%, 4)
2.   A year or less, I'm just getting started [0-1] (17.6%, 22)
3.   Two to three years, been here for a while already [2-3] (38.4%, 48)
4.   My gosh, it's been three to four years already [3-4] (16.8%, 21)
5.   Four to five years, got plenty of experience [4-5] (12%, 15)
6.   Five years or more, I'm old school! [5+] (12%, 15)

Total votings: 125

1.   Enable one or more of ProcessWire's built-in caching methods (11.6%, 24)
2.   Install and enable a third party caching module, such as ProCache (7.7%, 16)
3.   Image optimizations: minifying, lazy loading, CSS sprites, etc. (16.9%, 35)
4.   Minify and/or combine HTML, CSS, and JavaScript files (18.8%, 39)
5.   Inline bits and pieces of critical CSS and/or JavaScript (4.3%, 9)
6.   Use font icons instead of images whenever applicable (11.1%, 23)
7.   Enable prefetching, preloading, and/or prebrowsing (2.9%, 6)
8.   Leverage browser side caching for static files and assets (12.1%, 25)
9.   Fetch common CSS and JavaScript files from a CDN, such as BootstrapCDN or jsDelivr (6.8%, 14)
10.   Set up a full blown CDN service, such as CloudFront or Cloudflare, in front of your site (2.4%, 5)
11.   Considerable server side optimizations, manually or with tools such as the PageSpeed Module (5.3%, 11)
12.   Something else – please let us know via post comments! (0%, 0)

Total votings: 207

1.   New admin theme (11.7%, 12)
2.   New bundled site profile(s) (5.8%, 6)
3.   Predefined crop settings for image fields (7.8%, 8)
4.   Custom properties for image/file fields (7.8%, 8)
5.   New website (4.9%, 5)
6.   Front-end JS $pages API (18.4%, 19)
7.   Tools for exporting and importing of pages (30.1%, 31)
8.   Expanded image capabilities in CKEditor (5.8%, 6)
9.   More multi-language fields (2.9%, 3)
10.   New cheatsheet (4.9%, 5)

Total votings: 103

1.   Of course, I'm a big fan of Composer! (30.1%, 28)
2.   Not yet, but I'm planning to use it in the near future (17.2%, 16)
3.   Not really, I have no use for a tool like Composer (34.4%, 32)
4.   What's a Composer? (18.3%, 17)

Total votings: 93

1.   I'm against the whole idea of commercial modules (2.2%, 2)
2.   I don't necessarily like the idea, but I get why they are needed (34.1%, 31)
3.   They are a valuable addition to the ProcessWire ecosystem (61.5%, 56)
4.   I really don't have an opinion on this one (2.2%, 2)

Total votings: 91

1.   I don't use a front-end framework (21.7%, 25)
2.   Foundation – http://foundation.zurb.com/ (11.3%, 13)
3.   Bootstrap – http://getbootstrap.com/ (18.3%, 21)
4.   Uikit – https://getuikit.com/ (23.5%, 27)
5.   Materialize – http://materializecss.com/ (1.7%, 2)
6.   Semantic UI – https://semantic-ui.com/ (0.9%, 1)
7.   Pure – https://purecss.io/ (0.9%, 1)
8.   It depends entirely on the project I'm working on (14.8%, 17)
9.   Something else – please let us know via post comments! (7%, 8)

Total votings: 115

1.   Flexible and powerful API (32.8%, 38)
2.   Easy to use Admin interface (6%, 7)
3.   Custom fields and data structures (48.3%, 56)
4.   Markup agnostic output approach (6%, 7)
5.   Hook system and/or the module architecture (2.6%, 3)
6.   Technology: performance, scalability, and/or security (3.4%, 4)
7.   Something else – please let us know via post comments! (0.9%, 1)

Total votings: 116