133 rows sorted by Unnamed: 0

View and edit SQL

Suggested facets: How many sites do you have running on Wagtail?

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?
1 0 More than 5 Commercial Multi-language, Better performance, Audit logging I believe proper multi-language support is the biggest missing feature in Wagtail. Wagtailtrans is a solution but doesn't feel like al proper solution. At Lab Digital we are working on improvements on it currently (use wagtail hooks instead of overrides) but I still think this needs to be part of the core-offering of wagtail. Audit logging is a common requirement from our clients and better performance is never bad :-) BTW I'm interested in seeing how we can help develop the multi language part Not really for now :-)
2 1 2-5 Commercial, Non-profit, Education, Public sector UX research & improvements, Multi-language   More features for postgres search backend (filtering, fuzzy search)
3 2 More than 5 Non-profit, Education, Public sector, Media Accessibility, Multi-language, Page editor rewrite (new UI built with React and an API) There are various disparate bits of editor improvements, some are long running ones. Feels like an across-the-board effort would be welcome. There are still a number of a11y issues and we'd need tooling to maintain existing levels -- a big selling work. Last but not least multi-language questions keep cropping up all the time and most modern CMSes have i18n/multi-language out of the box out-of-the box GraphQL support, continued UX improvements
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.
7 6 1 Public sector Multi-language, Better performance, Full multi-tenancy They are useful for the wagtail instance of the greek Ministry of Shipping; also we are thinking of implementing more wagtail sites for organizations that the ministry of shipping supervises. We haven't yet decided if it's better to use the *same* wagtail server (using multiple sites) or a completely different one. Both seem to have various advantages and drawbacks... Maybe full multi-tenancy would resolve ths. Yes, I'd like to see the open issue and PR count go to single digit levels! Definitely try to reduce the open issues and PRs in wagtail github; there were open issues and PRs (some for a vert long time) for almost every requirement we had while developing the Ministry of Shipping portal. I think that it's better to focus on reducing the open github issue count than implementing new and shiny features. Actually my recommendation would be to avoid implementing anything new until the issue count is greatly reduced. Keep in mind that a big issue count makes people double think about adopting an open source project, especially for something as fundamental as a CMS. Having almost 700 open issues and 150 PRs does not look good from a managerial standpoint. I understand that developers rarely want to fix broken things or implement functionality that has a lot of moving parts and instead profer to work on shiny new things. Yes I understand that shiny new things may be useful for some cases but when there are fundamental piece of functionality that's missing from wagtail you should focus on that. A final recommendation would be to *reduce* the requirements for merging a PR. The high number of open PRs means that people want to contribute to wagtail but the core developers do not let them! Also I've seen many very useful PRs that work really great but do not get merged because of some non important DRY or architecture related issues. I fully disagree with that. If the code works *merge it* and then open an issue for refactoring if you think that it is so needed. But merge the PRs to get the functionality. Also the contributor doesn't really care about "having a great code standard"; he wants to implement the functionality for his organization; he even goes the extra effort of creating a contribution for wagtail, don't make it harder for him that it should be.
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.
9 8 More than 5 Commercial Documentation, Multi-language, Wagtail admin API internationalization and using wagtail as a backend for SPA-type websites are big challenges we've struggled with. And docs are always important! specifically draft support via the admin API. Also to note: my company has made an open source package (https://gitlab.com/thelabnyc/wagtail-spa-integration) to add some features to the wagtail admin API. We'd probably be interested in contributing dev time to add similar features to wagtail core, if y'all would be willing to support that.
10 9 More than 5 Commercial Page editor rewrite (new UI built with React and an API), Better performance, Audit logging    
11 10 More than 5 Commercial, Startup, Public sector, Culture Multi-language, Full multi-tenancy Because they are topics with a lot of projects/pitches  
12 11 More than 5 Commercial, Startup, Non-profit, Education, Governments Multi-language, Page editor rewrite (new UI built with React and an API), Live preview Support for translations takes time in every project, can be made way more standardized. Either page translations or for custom defined models. Editorial experience of > 4/5 blocks on a single page is still a thing to worry about. Got more and more comments about the quite large interface elements and non user-friendly of previewing. Way better support for headless setups, currently amount of websites we built headless are > 40%. Alternatives like Contentful are easier to intergrate. Specific parts: - Preview - Control over content in streamfields (APIField are ok, for blocks too much code) - Retrieve pages by path(s) rather than ID's - Integration with other libraries (more hooks in order to provide integration parts), like personalisation/translations
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?
15 14 More than 5 Commercial, Startup Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API) 1. The docs are very good anyway, but I feel like it’s such an essential thing for the uptake and success of any project to have as many people as possible able to access good learning resources. I would personally love a bit more insight into certain aspects of the internals and how to customise things, which I probably could get from studying the source but docs are obviously a great shortcut to that level of understanding for those short of time. 2. On the UX front I think there are maybe one or two areas where certain things aren’t 100% intuitive for our clients. Usability can always be improved with iteration if time allows. 3. The page editor is obviously the coal face of content editing in Wagtail. We were really excited by the Noripyt StreamField project (we chipped in on the crowd funding). The UX improvements (drag and drop, collapsibility, better nesting handling, more consistent UX between StreamFields and Inlines) all sounded great. Not sure what the status of all that is, but would still love to see those improvements make it through to a release. Very much appreciate our needs are a few amongst many though :) Also thanks so much for Wagtail, it’s the absolute bees knees. So amazing to have such a great CMS in the Django world! Better reporting / protecting of Image usages eg. in StreamFields. Direct to S3 uploads.
16 15 1 Commercial, Startup Documentation, UX research & improvements, Multi-language, Page editor rewrite (new UI built with React and an API), Better performance Cause these are critic points of our customer and our developers. It would be nice to see django-filter for API Filtering
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.
18 17 More than 5 Non-profit, Education, Public sector Built in SEO fundamentals    
19 18 1 Education, Research Documentation, UX research & improvements, Live preview There are a couple of things that don’t feel quite right in the page editor, especially with StreamFields and smaller screen sizes, and I wish there were a Publish & Continue button that would keep you on the page editor even after publishing. I chose documentation because I think wagtail is pretty great, and the better your documentation can be, the more people will understand how great it is.  
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.
21 20 More than 5 Commercial, Education, Public sector, Culture, Media Wagtail admin API, Better performance, Full multi-tenancy, Audit logging, Live preview These are all choices that would benefit our clients and thus probably other agencies as well.  
22 21 None Commercial Documentation, UX research & improvements, Wagtail admin API UX is often left behind, documentation is the core of every Open source project, API because SPA  
23 22 None   Accessibility, Documentation, UX research & improvements, Live preview I'm a beginner to wagtail, but would love to explore it Better tutorials
24 23 More than 5 Commercial, Startup Wagtail admin API, Built in SEO fundamentals, Live preview I think everything regarding the CMS UI is functioning very well and I don't think developer time is needed there. Just some easier approach to repetitiveness. Running blogs on various domains with similar content, copying data from one wagtail instance to another. Probably exists a way but some documentation on it. Ability to duplicate a snippet. SVG as an possible alternative when adding images and not having to use FileField. Mass selection of images to remove. Backing up databases from local to production or the other way around creates a bunch of empty images as they reference to a private db storage. Let me easily remove all of them and easily add 10 new images for these. Easen the developer workflow, instead of manually clicking your way through to replicate the live images to the local db.
25 24 More than 5 Commercial Multi-language, Page editor rewrite (new UI built with React and an API) wagtail was used mainly cause its fancy admin interface I would love to see wagtail stay simple.
26 25 More than 5 Commercial, Startup, Non-profit, Public sector Page editor rewrite (new UI built with React and an API), Wagtail admin API, Built in SEO fundamentals As a developer I spend a lot of time working around these I would really like to see a better api for programmatic creating and managing stream blocks
27 26 More than 5 Commercial, Startup, Non-profit, Education, Public sector, Culture, Media, Pretty much everything Better performance, Built in SEO fundamentals, Full multi-tenancy Biggest issue we run into is performance on our site. It's turned into a requirement that we run fragment caching in templates on everything. Our marketing team has also asked for more control over SEO so we had to build more tools for that. Full multi-tenancy would change the game for us. I've been wanting to work on a full redesign of the Wagtail Admin for a long time. I started wagtail-uplift a few years ago but id like to get it closer to looking and functioning like Ghost CMS. Right now Wagtail looks and feels like an open source project to many potential clients and I would love to help shift that perspective.
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)  
29 28 More than 5 Commercial, Startup, Non-profit, Public sector UX research & improvements, Better performance, Built in SEO fundamentals Based on a few issues we've had, I'd say these ones are both high-impact and address most of Wagtail's use cases. I'd love for there to be a couple things: - A way to change a page's page type (filling in only the shared fields) - Pagechoosers should be somehow aware of what site the page is on, so you can clone a site while maintaining the relative paths
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
31 30 1 Non-profit, Education, Media Accessibility, Documentation, Page editor rewrite (new UI built with React and an API)    
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  
34 33 1 Commercial, Startup Documentation, UX research & improvements, Wagtail admin API Builds around core focus vs adding outside features  
35 34 More than 5 Commercial, Public sector, Media UX research & improvements, Multi-language, Page editor rewrite (new UI built with React and an API), Wagtail admin API, Better performance, Built in SEO fundamentals, Full multi-tenancy, Audit logging, Live preview   Full live preview (eg. Craft CMS and Statamic). Clean UI for admin (like CraftCMS, Statamic and Strapi).
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.  
37 36 More than 5 Non-profit, Public sector Multi-language, Full multi-tenancy, Audit logging The multi-tenancy support would help In multiple cases for web apps/sites that I have deployed this way. Same with multi-language support, I haven't had put a single Wagtail instance without language support as it's a core need. These, combined with audit logging, are just basic core features needed for wagtail. The other features on the least seemed like basic 'nice to haves'. If I had the ability to pick a fourth it would certainly be accessibility. The fancy stuff can come after these issues are solved and functionality baked in. Especially multi language support, since while it works with external modules, it is clunky and feels very much like a jury rigged setup for a very fundamental system support. Those would be great, otherwise better linkages to Django admin, the Wagtail interface is great, but it doesn't support some usability areas, I.e. inlines, or dynamic inlines.
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
40 39 1 Commercial, Education Documentation, Page editor rewrite (new UI built with React and an API), Better performance    
41 40 1 Not-For-Profit UX research & improvements, Audit logging, Live preview    
42 41 1 Education Page editor rewrite (new UI built with React and an API), Wagtail admin API APIs to streamline interaction with SPAs are always a good idea!  
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    
47 46 1 Non-profit Page editor rewrite (new UI built with React and an API), Wagtail admin API, Full multi-tenancy    
48 47 1 Commercial UX research & improvements, Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals Product roadmap official cookiecutter maintenance
49 48 1 Startup Page editor rewrite (new UI built with React and an API), Better performance, Built in SEO fundamentals    
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.
52 51 None Commercial, Media Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API) I just did a deep dive to assess Wagtail as a viable CMS for our use cases. Many of our use cases would require writing Wagtail extensions or forking Wagtail to change code, and the code base doesn't seem to follow Django conventions, and doesn't seem well documented enough to make this a reasonable option. The bakery demo code base also gives me pause as to the the quality of code I would have to jump into. built in isomorphic rendering solution.
53 52 1 Commercial, Non-profit, Education, Culture Documentation, Page editor rewrite (new UI built with React and an API), Wagtail admin API These are the areas I have had to do much work in due to it lacking.  
54 53 More than 5 Commercial, Media, Health Care Wagtail admin API, Full multi-tenancy, Live preview Live Preview - This is something my clients have asked for in the past, but its not an easy solution with the current way wagtail is setup. Full multi-tenancy - We recently started development on an application where we needed multi tenancy, and had to "roll our own", going through the process without wagtail made me realize how much I rely on wagtail for a lot of stuff. Wagtail admin API - if this means what I think it does, then this would be helpful in making the admin more flexible, so we could do whatever we wanted to, to the admin.  
55 54 More than 5 Education UX research & improvements, Wagtail admin API, Live preview   I would like to see wagtailmedia become an integral part of Wagtail, with various improvements made.
56 55 More than 5 Commercial Accessibility, Documentation, Full multi-tenancy These are our priorities as an organization, building multi-tenancy and having our websites be as accessible as possible.  
57 56 1 Non-profit, Education Accessibility, Page editor rewrite (new UI built with React and an API), Wagtail admin API I would like to be able to customize the admin more, and to have collapsible stream blocks so that long pages are more manageable to edit.  
58 57 More than 5 Commercial, Public sector, Culture Page editor rewrite (new UI built with React and an API), Full multi-tenancy, Live preview They are the pain points I find when developing Wagtail backed websites for clients.  
59 58 More than 5 Commercial, Startup, Public sector, Culture UX research & improvements, Page editor rewrite (new UI built with React and an API), Wagtail admin API The designers in our team look down on the Wagtail admin interface. UX improvements and the new UI React are obvious choices for resolving their criticisms. I have also selected Wagtail admin API because if the admin were more flexible open to change, it would be easier to adjust the things which frustrate our designers.  
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.
61 60 None Commercial UX research & improvements, Multi-language, Built in SEO fundamentals    
62 61 1 I track and sell my art Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API) Documentation, because lowering the barrier to entry and helping solve problems is always a core goal. The others just sound nicest for my use-case - I'm running a small site with a small userbase.  
63 62 1 Education Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals, Live preview Better interactivity  
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
65 64 More than 5 Commercial, Education Multi-language, Audit logging, Live preview   Security on Collections is number one on our wish list. The multisites aren't working right now because they can see each others files, several people from several company's should use one wagtail setup if possible
66 65 More than 5 Commercial, Non-profit, Public sector, Culture, Media UX research & improvements, Multi-language, Better performance Multilanguage is something that pops up every so often and doesn't have a clear solution. Even our own package I'm hesitant to use since it's so out of date. An out of the box solution would definitely help, when quoting on projects it could be a nice value add. Wagtails UX is good but it can always be better. I've expanded on this in the next section. Performance is always something that can be improved, I don't have any specific examples but it's what I'd prefer over the other options. A nice way to onboard users via Wagtail that isn't written documentation. We spend a bit of time here running workshops about how to use Wagtail. Clients always love it but if there was a short demo that runs when the user logs in for the first time it would help those less competent users. I think splitting User documentation away from Developer documentation, with a way to get to that documentation from the admin would also go a long way to get users the help they need. Some examples of onboarding: https://www.trychameleon.com/tours https://uxplanet.org/creating-an-animated-onboarding-experience-19b0363a1326
67 66 1 Commercial Documentation, Page editor rewrite (new UI built with React and an API), Live preview Documentation - I'm still learning wagtail and frequently refer to docs. More/better is always better. The rest is because our main use is focused around editing since its just an internal portal.  
68 67 More than 5 Commercial, Startup Page editor rewrite (new UI built with React and an API), Better performance, Built in SEO fundamentals, Full multi-tenancy, Live preview Most are just nice to have. Wagtail is a great platform. To compete more with the others out there live preview would go a long way as well as SEO. Performance is a big one for me as pages with a ton of streamfields tend to go much slower in my experience ( but maybe I am doing something that could be optimized) Some sort of extension for Saleor would be a great opportunity for you guys. I recently built a site that needed to be a blog and an ecommerce. Ended up having to go with django oscar (which wasn't the greatest experience) because I could combine wagtail with it. Saleor is pretty monolithic but maybe there is some way to make an extension for it.
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 ...
71 70 1 Non-profit Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API), Audit logging    
72 71 More than 5 Commercial, Education, Public sector Accessibility, Documentation, UX research & improvements, Built in SEO fundamentals, Live preview Based on experience To be able to select multiple pages(articles its.) and move them
73 72 More than 5 Commercial, Startup, Technology UX research & improvements, Page editor rewrite (new UI built with React and an API), Live preview Customers use it, not developers. Customers are happy, developers are happy.  
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
76 75 1 Education UX research & improvements, Wagtail admin API While Wagtail is the best CMS we’ve ever implemented, we still have a few pain points: • Moderation workflow • Programmatic object creation • Tagging improvements • Extensible view restrictions (permissions!) RFC 45: Workflow RFC 28: Tagging improvements RFC 32: Extensible view restrictions (I know this one is on me to fund. I'm just reminding myself that it's out there)
77 76 1 Education Accessibility, UX research & improvements, Built in SEO fundamentals These are areas lacking for our site and would make great core functionality. more plugins
78 77   Education Accessibility, Documentation, UX research & improvements   It would be better if we could see who are the moderators so that we could contact them individually if an approval is needed immediately.
79 78 More than 5 Commercial, Non-profit, Education, Public sector, Culture Multi-language, Page editor rewrite (new UI built with React and an API), Wagtail admin API, Better performance, Live preview    
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.
81 80 None Commercial, Startup, Non-profit, Education, Public sector, Culture Multi-language, Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals These are the basic needs that any modern CMS to compete with WordPress need to fill Admin API
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…  
83 82 1 Commercial UX research & improvements, Multi-language I have had trouble explaining how to navigate the page trees for clients, and I just ran into needing multilanguage after a site has been built and see a difficult path ahead. The ability to have a chooser for other models would be great. I like to wire it up so many to one can be done either from the one or the many.
84 83 1 Media Better performance Because the real thing was not available Sharp Images, Video/Audio handling
85 84 1 Startup, Non-profit, Open Source for worldwide use by doctors; After that Enterprise part. like Odoo, Anaconda and many others Accessibility, Documentation, Better performance The open source needs accessibility by doctors non-programmers. That is needed to create content to question patients before appointments worldwide in all languages for all conditions. Yes, built-in PDF generation at client side, and Latex PDF generation for publication grade PDF generation.
86 85 1 Startup Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API), Wagtail admin API, Live preview Enable our editors to build the pages more intuitively A good book would be a big plus
87 86 None Commercial, Startup Multi-language, Built in SEO fundamentals, Live preview I've been looking into many CMS systems and like Wagtail a lot. Some things that stood out to me that could be better are: (first party) multi language support (like Prismic) and Live preview (like Craft CMS). Built-in SEO fundamentals would be a nice bonus. Keep up the good work!
88 87 None Commercial, Startup, Non-profit Accessibility, UX research & improvements It needs to be nice and simple to use for the page editor  
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.  
90 89 More than 5 Commercial, Startup, Non-profit, Education, Culture Multi-language, Built in SEO fundamentals Seo and multi language are often things I need to add through third party libraries or custom code and I would find it very nice if there is already something I could use.  
91 90 More than 5 Startup, Education, Portfolio Documentation I focus largely on lowering the barrier to entry around Wagtail. Documentation has been credit as the reason why PHP and jQuery grew so fast, and held their market share for so long. I like to think we could do the same for Wagtail. Help or support links (or maybe icons) on pages to help people understand what they're looking at. Like a little question mark icon in the "Snippets Listing View" that either links to documentation, or has a modal popup explaining what a Snippet is (same for settings, pages, etc).
92 91 1 Education Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals Fast build website Udemy course
93 92 1 Education, Public sector Accessibility, Documentation, Better performance    
94 93 More than 5 Non-profit, Culture Wagtail admin API   Support for proxy models, PDF inline view, stabalization of the API
95 94 1 Personal Documentation, Multi-language, Page editor rewrite (new UI built with React and an API) I think this stuff improve wagtail Official tutorial like in django
96 95 More than 5 Commercial, Public sector, Culture Multi-language, Full multi-tenancy Multi language: Many of clients are from Sweden, and since Swedish is a relative nisch language our clients often require English as well, so a well built language support would be great. (I think wagtailtrans is coming along nicely!) Full multi-tenacy: We work a lot with multi tenacy and the support has gotten a lot better the last couple of years, but there are still some kinks to sort out, for example getting page choosers right, permission based collections and site aware promoted_search. - Multi actions in modeladmin and page admin.
97 96 More than 5 Commercial, Non-profit, Education, Public sector UX research & improvements, Page editor rewrite (new UI built with React and an API), Live preview I think the developer experience for wagtail is good. The editor experience is also good, but it is important it stays right up there as a leading choice for the people who use it daily, especially compared against proprietary headless CMS services. Maybe developer tools such as a vscode snippet library. Not really part of wagtail itself though.
98 97 More than 5 Commercial, Education, Culture UX research & improvements, Multi-language, Full multi-tenancy our company is in switzerland where multi language is crucial, half of the website we make are multi language. To be able to use wagtail in more project we need better multi language support (we use typo3 for that kind of project ATM). I happy that there is done some work with wagtail localize, but I should be in the core form my perspective. I want to be sure that I always can use it with the latest wagtail version and that it doesn't get abandoned after a few years. better headless support preferable in the core, and/or to be in the main documentation. So that it can be positioned better against for example directus or strapi.
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! :)

Next page

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
);