39 rows where How many sites do you have running on Wagtail? = "2-5"

View and edit SQL

How many sites do you have running on Wagtail?

  • 2-5 · 39
Link rowid ▼ Unnamed: 0 How many sites do you have running on Wagtail? What kind of organisations are your Wagtail sites for? What are your priorities for Wagtail's direction in the next year? Please choose a maximum of three Why have you made these choices? Is there anything else you'd like to see in Wagtail?
2 1 2-5 Commercial, Non-profit, Education, Public sector UX research & improvements, Multi-language   More features for postgres search backend (filtering, fuzzy search)
4 3 2-5 Commercial, Culture, Media Page editor rewrite (new UI built with React and an API), Wagtail admin API, Full multi-tenancy These would be the priorities for my clients, a new page editor could help resolve the 'lost in streamfields' issue that they often report, an admin API could help me build custom interfaces for more unique requirements, and some of my clients are running in the limitations of the multi-tenancy support as it is so far. Easier to customise StreamField blocks (i.e. supporting and documenting the process to allow a custom React component be used), hierarchical collections, a way to use all the features of Pages without the hierarchy
5 4 2-5 Commercial, Startup, Personal UX research & improvements, Built in SEO fundamentals, Full multi-tenancy These are the points I find a little lagging. Integration of frontend tools. Such as django-webpack-loader
6 5 2-5 Commercial UX research & improvements, Page editor rewrite (new UI built with React and an API), Wagtail admin API I believe that the best way to improve Wagtail is make it more usable out of a box for small websites. If one makes a small site he doesn't want to spend much time to struggle with the basic tasks. Wagtail is the finnest but there are a couple of improvements I would like to see. For instance, I want to add 5 pictures at a time via an inline panel as I need to select 25 pictures and this forces me to click "Add image" and atter that I pick an image but it would be significantly better if I chose 25 images from a collection at a time and add to my page.
8 7 2-5 Education UX research & improvements, Wagtail admin API, Built in SEO fundamentals The websites purpose is to generate customers so SEO is essential. A better Admin interface means less calls from users to the developer. Our sites lack consistency across platforms so we are prioritising that as well. Number 4 would have been language support, our customers use several local languages. Better support for pulling data out of Streamfields, mostly the first element of a specific type. Imagine creating a blog, but pulling the data for the Index page from a streamfield. First title, paragraph and image for example.
13 12 2-5 Commercial, Education, Media Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API)    
14 13 2-5 Commercial, Startup Documentation, Multi-language 1. I feel like first party multi language support that works properly would be a huge gain. I see this some custom implementations that work reasonably well. 2. Django-quality docs / getting started guide would improve the experience for beginners, like I once was. Modernise the frontend tooling perhaps?
17 16 2-5 Non-profit, Public sector Accessibility, Page editor rewrite (new UI built with React and an API), Live preview My most common pain points are in helping my users deal with with some of the little nuances of the editor that may not be intuitive to some users, so that's why I selected Page Editor Rewrite and Live Preview. And Accessibility is a critical concern for both a U.S. government entity and a church that aims to be as inclusive as possible. Probably my absolute #1 top request is having a way to use the link chooser modal that is currently available in the rich text editor as a standard field or as a StreamField block.
20 19 2-5 Commercial, Startup, Non-profit, Education, Public sector Documentation, UX research & improvements, Wagtail admin API, Better performance We love Django, and Wagtail makes the most sense if we're building sites for our clients. Yes, I'd like to see more fine grained control in the Wagtail Admin (for example granular control on wagtail ModelAdmin to include button on each rows, to add actions which will run on multiple rows, to add more custom views, etc) This is really important as almost all clients need some level of customization for which we need to write custom views/functions.
28 27 2-5 Commercial, Startup, Non-profit Accessibility, Page editor rewrite (new UI built with React and an API), Better performance Using the new react streamfield has been working great, like to see that continue, accessibility is a big issue with most clients, always better performance (or some good caching options, or examples)  
30 29 2-5 Commercial, Startup, Non-profit, Education Page editor rewrite (new UI built with React and an API), Wagtail admin API, Live preview Customer pain points Better/easier story around automated testing and "linking" the homepage row
32 31 2-5 Startup, Non-profit Page editor rewrite (new UI built with React and an API), Wagtail admin API, Built in SEO fundamentals I am react-django dev, so I would love to have admin API to built my own admin interface or have built-in react admin.  
33 32 2-5 Commercial, Non-profit Multi-language, Built in SEO fundamentals To write applications faster and easier  
36 35 2-5 Commercial, Startup, Non-profit Accessibility, Built in SEO fundamentals Accessibility is a huge priority for me as an indivudual, and increasingly more companies are pushing for it on their site after the Domino's lawsuit. However resources on best practices are all over the place and dated, so if more accessibility considerations were baked into the CMS that would be a huge deciding factor & benefit for me.  
38 37 2-5 Commercial, Non-profit Page editor rewrite (new UI built with React and an API), Better performance, Built in SEO fundamentals While great, Wagtail isn’t the snappiest out there. I would like to see a more dynamic page editor so my customers have an easier time editing their site.  
39 38 2-5 Commercial, Non-profit Documentation, Page editor rewrite (new UI built with React and an API), Better performance Streamfield performance issues in production when using many block types, need of documentation concerning programmatic access to streamfields and streamfield migrations Built-in generic model choosers, optional title/slug fields, being able to access page context fron within streamfields
43 42 2-5 Startup Documentation, Page editor rewrite (new UI built with React and an API), Full multi-tenancy I'm pretty new to using Wagtail, so I'd like to see more thorough examples for the concepts in the docs (though, the docs are generally good enough to get a basic site going). In the Page editor, I'd mainly like to see drag and drop ordering and collapsible areas for the fields. Lastly, I have a client with multiple, relatively low-traffic, sites, and I'd like to be able to host them all more centrally. More on the wishlist side, I'd like to see a site importer (at least to be able to import Page templates) for converting clients from WordPress sites into Wagtail, but I know that's a pretty hard thing to accomplish, especially given the different philosophies in the projects.
44 43 2-5 Commercial, Startup, Education Page editor rewrite (new UI built with React and an API), Live preview Make the cms more client (ie 100% non technical) friendly I like the codered cms pre built components . One click heroku install
45 44 2-5 Commercial, Non-profit, Culture Documentation, UX research & improvements, Multi-language, Built in SEO fundamentals Wagtail is great but it needs to be easier for end users. Many people in my country are used to wordpress and wordpress only. For documentation, sometimes it's a struggle to find how to "correctly" implement stuff  
46 45 2-5 Non-profit, Public sector, Sport club UX research & improvements, Multi-language, Full multi-tenancy    
50 49 2-5 Public sector, Personal UX research & improvements, Page editor rewrite (new UI built with React and an API), Live preview I'm not necessarily strongly tied to these options, but I always love a better user experience. Wagtail has one of the best user experiences out there, but I've seen better, especially in the Statamic CMS framework. I also debated about including multi-tenancy, since it's something that could have been very useful.  
51 50 2-5 Media, Intertainment Documentation, UX research & improvements, Wagtail admin API   Theming for admin.
60 59 2-5 Health Care Accessibility, UX research & improvements, Built in SEO fundamentals In using wagtail those are the issues I run into most often Better Child Parent page UX / structure in the admin. I like the simple clean folders but come on lets see a dropdown or something, and also the ability to keep the dropdown state if you had to drill down, edit a page, and then return to the menu. Going through pages feels clunky.
64 63 2-5 Commercial, Non-profit UX research & improvements, Page editor rewrite (new UI built with React and an API), Live preview I think the ui for editors would be better if there was a live preview Nothing springs to mind. Keep up the good wo4k
69 68 2-5 Commercial, Startup Wagtail admin API, Full multi-tenancy, Live preview    
70 69 2-5 Commercial, Startup, Education, Culture Multi-language, Live preview Almost all website we make are are multi language, and we always use API so live preview is nice. We currently use wagtailtrans for translations. I think its a good model. Live preview so you can edit you page while seeing what you edit. Sometimes client can get lost. Also better document and image management. For example limiting what images to a collection for certain pages. Subfolders in images ...
74 73 2-5 Commercial, Startup, Non-profit, Media Multi-language, Better performance Based on things we had to do by ourselves  
75 74 2-5 Non-profit, Education, Public sector, Personal Blog! Page editor rewrite (new UI built with React and an API), Wagtail admin API, Better performance The needs I've heard from our editors and authors. • RFC 45: Workflow • RFC 28: Tagging improvements • RFC 32: Extensible view restrictions
80 79 2-5 Commercial, Non-profit, Education, Culture Accessibility, Documentation, Page editor rewrite (new UI built with React and an API) Documentation: The documentation, while fairly comprehensive is organized in an odd way. Accessibility: We're always interested in better accessibility for our users. Page Editor: It's currently strong, but this is the heart of wagtail for us, and any work towards a better workflow is always welcome. An official version of modelchooser or wagtail-autocomplete that's included with wagtail.
82 81 2-5 Non-profit, Education, Public sector, Culture Documentation, Built in SEO fundamentals Documentation: the core documentation is sparse for beginners (who I assume, like me, just use Kalob's tutorials instead). As more new users start to adopt Wagtail, broader coverage of basic topics (such as blogging, themes, templates, deployment, etc.) is going to become more important. Many of the Wagtail questions on StackOverflow are relatively basic, so it's clear that many people are coming from other platforms and just need a little nudge to get all the way to a successful launch. The documentation on deployment is particularly sparse and would really benefit from more details. It seems to me that you are now in the position of broadening Wagtail's scope from a platform that is built by developers (and for consumers) to one that is also starting to be built by non-developers (people like me) who have perhaps built Drupal or Wordpress sites in the past and want to adopt this newer technology. This is not a huge hurdle, as Wagtail is relatively straightforward, but it's easy to get stuck in various places if you are not a professional developer. So, to reach this newer demographic, it might be useful to develop some in-house documentation that is just a bit more basic. To take one specific example: the "Your First Wagtail Site" tutorial takes readers to the point of having blog categories -- but no way to click through the categories and aggregate posts by categories. Consequently, the categories have no real use. And, since everyone wants clickable categories, the non-developer will be stopped right there, and will (as I did) spend a very long time hunting down other, external resources to figure out how to get categories working properly. The information is out there, and others have created it, but it might be a good idea to bring some version of those external resources into the main documentation so that beginners have a slightly easier ride. SEO: This is just something I'm interested in, as the next step for my own project. Overall, Wagtail is great, and I'm enjoying it very much. Thanks for creating…  
89 88 2-5 Commercial, Media Documentation, UX research & improvements, Wagtail admin API Documentation is often a short code example with no explanation of what it does or what is possible (e.g., the ModelAdmin documentation). I've often ended up looking at the source code to find answers or asking on Slack.  
99 98 2-5 Commercial, private family real estate operations Accessibility, UX research & improvements, Page editor rewrite (new UI built with React and an API) I really have no input on direction - except you are doing great. love ability to have tables on plain pages - impossible with streamfields
100 99 2-5 Tech agency UX research & improvements, Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals * great admin user experience differentiates Wagtail & we need to keep investing in it as competitors improve their UIs * SEO capabilities come up in every CMS pitch & think some of the competitors do a nice job here WASS! :)
108 107 2-5 Non-profit, Education Documentation, UX research & improvements, Multi-language    
114 113 2-5 Commercial, Agency UX research & improvements, Live preview Because I use it most as an editor and see some glossy features in other systems that I'd like us to have. Auto-save, more personalisation features.
121 120 2-5 Education Accessibility, Built in SEO fundamentals, Live preview got to get the basics right - and that includes being able to send preview links to clients :)  
124 123 2-5 Non-profit Accessibility, Multi-language, Page editor rewrite (new UI built with React and an API) Multi-language and improved page editor are things my projects would immediately benefit from. Accessibility just seems like an ethical good.  
125 124 2-5 Public sector Accessibility, UX research & improvements, Multi-language We are building a large network of sites for our county on wagtail. Accessibility is important because with it being a large government site, the more users able to access it with ease and work with it is obviously a good thing. UX research & improvements because I've had to do things like write custom conditional logic managers, and i feel like on a CMS platform thats already this versatile, conditional logic could stand to be implemented into core. Then again, I could always just write my own which is nice :P I think also the general UI could be slimmed down a bit to include less padding, and mobile responsiveness would be good out of the box too. I personally feel like when i have a streamfield with a ton in it on the page, theres just so much scrolling to navigate the content there. We have applied our own css rules to cut back on the padding, but this is just a personal nitpick haha. Just throwing it out there. Multi-language support would also be an amazing feature to have built into core, again for accessibility reasons. We are currently in the beginning stages of figuring out our own multi lingual solution because its a requirement for these government sites often times. Better support for nested orderables. I frequently encounter bugs when nesting more than one level deep. I plan on posting some bug reports but I haven't had time just yet. They also are just a little buggy, I had to write a script to add missing values that weren't being added when a min_num was set. Itd be awesome if orderables could just get a little revamp/better support for more situations like nesting. It would be nice if every type of panel had the ability to add classes. For example, its weird that I can add a class to a DocumentChooserPanel by default, but not an ImageChooserPanel by default. Some level of out of the box theme-ability on the admin side would be pretty nice too.
128 127 2-5 Non-profit, Education, Public sector, Culture, Media Accessibility, Documentation, Better performance In brief: Accessibility: Because it's a particular focus for a lot of our clients and better accessibility benefits us all Documentation: We have found that new developers have struggled to find what they need in the docs. Performance: Not that the performance is bad per se but like accessibility, better performance benefits us all (these answers may be too brief. Happy to elaborate if needed) Nothing specific, we've been able to build things in Wagtail that we could never dream of in Drupal. We've been officially using Wagtail for client work for a couple of years now and we absolutely love it. Keep up the good work!

Advanced export

JSON shape: default, array, newline-delimited

CSV options:

CREATE TABLE "wagtail-survey-responses" (
"Unnamed: 0" INTEGER,
  "How many sites do you have running on Wagtail?" TEXT,
  "What kind of organisations are your Wagtail sites for?" TEXT,
  "What are your priorities for Wagtail's direction in the next year? Please choose a maximum of three" TEXT,
  "Why have you made these choices?" TEXT,
  "Is there anything else you'd like to see in Wagtail?" TEXT
);