133 rows sorted by Unnamed: 0 descending

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?
133 132 More than 5 Commercial, Startup, Non-profit, Education, Public sector, Culture, Media Multi-language, Wagtail admin API, Better performance, Full multi-tenancy   An abstract / custom Page model base would be a dream. Being able to override or define additional fields on a concrete model would save us a lot of time and code headaches. The ability to pickle Streamfield data would be super helpful too. Also, more for Modelcluster, but being able to prefetch ParentalManyToMany fields and image renditions would be a excellent!
132 131 1 Non-profit, Education, Public sector Documentation, Multi-language, Audit logging Discovered wagtail 3 days ago, and I’m totally convinced. But to my humble opinion, the documentation is still poor. I checked the Multi-Language box because I think you have the potential to natively implement this feature (either with modeltranslation or something else) Feature to 1) easily implement and administrate multi-level tree structure class. 2) translate models, think modeltranslation on steroids and natively integrated with easy frontend integration
131 130     Multi-language, Live preview Multi-language seems like a common (and useful) requirement, Live preview would be a great editor experience improvement (and it looks cool :-) )  
130 129 More than 5 Commercial Page editor rewrite (new UI built with React and an API) Page editor rewrite just sounds like a good idea although it works great just now. Some times I do feel streamfields are difficult to work though going down the page when there's a lot of entries, a pain point for my customers who don't spend that much time in the admin and only do occasional updates, they get lost. Mostly when adding lots of images for a gallery but especially if the stream field has nested stream blocks of a couple of depths. As a thought... I'd like to see at least some type of named navigation towards the top of the page to 'jump down to a section'. Another feature I would like to see is documentation snippets that can be viewed next to each block. I currently try to use the help text but sometimes what you need to say can be quite long.  
129 128 1 Non-profit UX research & improvements, Multi-language, Built in SEO fundamentals My website needs to reach people from different language backgrounds. Admin UI with collapsible sections
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!
127 126 More than 5 Non-profit, Education, Public sector Documentation, Full multi-tenancy, Live preview Anticipated need  
126 125 More than 5 Commercial, Startup, Non-profit Documentation, Better performance, Built in SEO fundamentals I feel like the documentation could be more detailed than it is right now, making it easier for newbies. Additionally, the third-party SEO plugins are not well updated, however they do work just fine.  
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.
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.  
123 122 1 Non-profit, Education Accessibility, Better performance, Live preview User functionality is key, the ability to see a live preview would be really helpful. better search function
122 121 1 Non-profit, Education Accessibility, Better performance, Live preview User functionality is key. Being able to see live preview would be very useful. Better performance especially in Elastic Search. Better search functionality - ability to configure from the Wagtail admin.
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 :)  
120 119 More than 5 Non-profit, Education, Public sector Multi-language, Built in SEO fundamentals, Audit logging Multi-language: this is something that I've had to do implementation work in the last year, and found the available solutions a bit clunky for both developers and editors. Having slicker, out-of-the-box handling for multiple languages would make Wagtail a competitive choice for sites with a more international focus - and possibly help Torchbox win work with more clients outside of the English-speaking world, including UK sites with a mandated requirement for Welsh-language pages. Built-in SEO fundamentals: we have great in-house expertise for SEO who we can work with to make Wagtail a leader in how CMSs do SEO. This is already being looked at for Kitsite, with Kevin and Nick Vines having started a closer collaboration in the last couple of months. Audit logging: this is something that's come up as a nice-to-have in discussions with several clients I've worked with. I suspect that this will become a stronger/more common requirement if we want to work with more highly-bureaucratic clients like government departments - and especially if we're pursuing ISO 27001 compliance and wanting to work with ISO 27001-conscious organisations.  
119 118 More than 5 Non-profit, Education, Public sector, Culture Accessibility, UX research & improvements Accessibility - the work for DIT shows we have lots more to do in this area. UX research and improvements - I think there are some areas that have confusing UX e.g. the page ordering functionality, which clients can never find. Also finding how to get a list of pages using a certain page type is hard to do. Another area where I think UI could be improved is in the streamfield blocks area - if you have multiple nested blocks it becomes hard to tell whether you are adding a component of a block or a new block, and the layout can get messy too. I think writing accessible clean markup is probably more of a priority than rewriting in React although that may achieve the same goal.  
118 117 1 Non-profit Accessibility, Multi-language, Page editor rewrite (new UI built with React and an API) Page editor - big request from our content editors is to be able to breakup text streamfield blocks after they've been created so images etc can be placed between them. Multi-language might become a bigger priority for us given work with Welsh Government Accessibility improvements should always be high up on the agenda! Support for Gifs or other forms of code embed - eg. to embed a tweet without the need to host in an iframe
117 116 More than 5 Non-profit, Public sector Accessibility, UX research & improvements, Built in SEO fundamentals I believe these 3 will have the greatest impact on my clients' ability to create successful website content. Decent content review and workflow improvements
116 115 More than 5 Commercial, Startup, Non-profit UX research & improvements, Page editor rewrite (new UI built with React and an API), Live preview Almost all of our users are WordPress converts. Most of them value the ability to edit independently without developer assistance, that is their #1 concern. As such a beautiful and enchanting UI carries more weight (for better or worse) than virtually any other feature when trying to sell Wagtail, which for most buyers is still an unheard of CMS. Developers on the other hand are already sold and can implement most any other feature into Wagtail as needed. Focus on a competitive and cutting-edge UX is essential for Wagtail to be sought out by non-developers.  
115 114 More than 5 Education, Public sector Page editor rewrite (new UI built with React and an API), Audit logging, Live preview I'd like our editors & moderators to be happy.  
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.
113 112 More than 5 Education Accessibility, Full multi-tenancy, Live preview We run over 200 sites in 3 installs all with the same code base. So full multi-tenancy is vital for us. Similarly, we have gotten threats of being sued over accessibility issues so that is also important to us (all the issues in the threat were problems of our own making, not Wagtail's). And finally, though none of our users have complained about the editor looking very different than the page it produces, I would love to have a live preview. That's something I miss from other CMSs I have built and used. I would love to be able to drag and drop blocks within the page editor. If that is something a React + api rewrite would afford, then change my 'live preview' vote to 'react page editor'
112 111 More than 5 Commercial, Non-profit, Education, Public sector Wagtail admin API, Better performance, Audit logging Wagtail admin API - makes writing third party apps simpler and smoother. Better performance seems like an easy win in terms of query optimization, and something that a lot of people are clearly interested in. Audit logging - now we have the new workflow timeline (when released), similar info for other events seems like a natural extension for users. Simplifying admin template structure and making it more reusable, and continuing to move modeladmin features into core
111 110 1 Commercial, Startup, Non-profit, Education Accessibility, Documentation, Multi-language Critical for what we are launching and where our road map is going.  
110 109 More than 5 Non-profit, Education, Public sector Accessibility, Documentation, Live preview I think they are both realistic and high-impact.  
109 108 More than 5 Non-profit, Public sector Multi-language, Better performance, Audit logging Accountability is very important in the public sector, so audit logging would be a quick win. Better performance, because I feel it can often get overlooked when there are more exciting things to work on, but can make a huge impact. Not every project is well suited to upstream caching, which can often cover a multitude of sins. Multi-language/localisation because I feel it's something that is important for so many sites, but it's so often done badly, which taints developers views of Wagtail unnecessarily. We don't feel far away from having a solid solution figured out. I would say multi-tenancy, but I'm feeling more and more that it's a bit of a red herring. In almost all cases where I've seen projects trying to achieve true separation within the same instance, I've felt it really would have just been better to keep things simple and just host the same codebase multiple times - Support for prefetch_related on ParentalManyToMany - A more complete set of signals for page changes, to better support complex caching strategies
108 107 2-5 Non-profit, Education Documentation, UX research & improvements, Multi-language    
107 106 More than 5 Non-profit, Education, Public sector, Media Documentation, UX research & improvements Documentation wise I feel like it could be nicer then readthedocs, docs are another way to show off how wagtail works. UX research - a few projects I've worked has seen me making small updates to wagtail core for some cms UI tweaks. Small things like capital case for all field labels etc. Similar to django-admin a default view showing tags, if the Taggit functionality is being used.
106 105 1 Public sector Page editor rewrite (new UI built with React and an API), Wagtail admin API We're making a lot of in-house UX changes to the editor and admin flows. We've found ways to achieve what we need so far with a combination of template tags, js, and custom view endpoints, but it would be much easier to achieve the features on our roadmap if we could have a decoupled page editor with an API.  
105 104 More than 5 Commercial Page editor rewrite (new UI built with React and an API), Live preview Everything else is done very well. Streamblocks just need some better UI so content editors can unleash their creativity in a more straightforward way. Admin CP might use some popular CSS/JS framework like Vue/React & Bootstrap, so it will be much easier to develop additional modules with the same look & feel!
104 103 1 Startup, Non-profit UX research & improvements, Multi-language Multi-language is daunting. Diffing versions with streamfield/rich text is not user-friendly  
103 102 1 Education Documentation, Multi-language, Wagtail admin API I'm working in a multi language environment where every page needs to be in at least two languages. To customize wagtail to my needs documentation and admin api are key. Better image and file integration into admin. I tried to work on the file and image list pages last year, but couldn't quite get my head around the permission system. I'd like to see a wagtail dev channel in slack, where one could ask questions according to wagtail development.
102 101 1 Public sector Accessibility, UX research & improvements, Live preview These are the most important things I am missing when trying to design content/UX for sites. Functionality including: • a progressive disclosure accordion pattern, as at here: https://design-system.service.gov.uk/components/accordion/ • amend formatting of bullets so that font size is same as body content and bullets are black, not grey • expand numbered bullets to also include letters and numbers, for example, 1, 2, 3, a, b, c, i, ii, iii - this will become increasingly important as we do more council policy content • amend spacing issue - between paragraphs/bullets and headings, both have a padding issue
101 100 1 Education Page editor rewrite (new UI built with React and an API), Wagtail admin API   • Moderation workflow • Programmatic object creation • Tagging improvements • Extensible view restrictions (permissions!)
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! :)
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
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.
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.
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.
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
94 93 More than 5 Non-profit, Culture Wagtail admin API   Support for proxy models, PDF inline view, stabalization of the API
93 92 1 Education, Public sector Accessibility, Documentation, Better performance    
92 91 1 Education Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals Fast build website Udemy course
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).
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.  
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.  
88 87 None Commercial, Startup, Non-profit Accessibility, UX research & improvements It needs to be nice and simple to use for the page editor  
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!
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
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.
84 83 1 Media Better performance Because the real thing was not available Sharp Images, Video/Audio handling
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.
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…  
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
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.
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    
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.
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
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)
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
74 73 2-5 Commercial, Startup, Non-profit, Media Multi-language, Better performance Based on things we had to do by ourselves  
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.  
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
71 70 1 Non-profit Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API), Audit logging    
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 ...
69 68 2-5 Commercial, Startup Wagtail admin API, Full multi-tenancy, Live preview    
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.
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.  
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
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
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
63 62 1 Education Page editor rewrite (new UI built with React and an API), Built in SEO fundamentals, Live preview Better interactivity  
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.  
61 60 None Commercial UX research & improvements, Multi-language, Built in SEO fundamentals    
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.
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.  
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.  
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.  
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.  
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.
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.  
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.  
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.
51 50 2-5 Media, Intertainment Documentation, UX research & improvements, Wagtail admin API   Theming for admin.
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.  
49 48 1 Startup Page editor rewrite (new UI built with React and an API), Better performance, Built in SEO fundamentals    
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
47 46 1 Non-profit Page editor rewrite (new UI built with React and an API), Wagtail admin API, Full multi-tenancy    
46 45 2-5 Non-profit, Public sector, Sport club UX research & improvements, Multi-language, Full multi-tenancy    
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  
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
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.
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!  
41 40 1 Not-For-Profit UX research & improvements, Audit logging, Live preview    
40 39 1 Commercial, Education Documentation, Page editor rewrite (new UI built with React and an API), Better performance    
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
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.  
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.
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.  
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).
34 33 1 Commercial, Startup Documentation, UX research & improvements, Wagtail admin API Builds around core focus vs adding outside features  

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