133 rows sorted by Is there anything else you'd like to see in Wagtail?

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? ▼
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  
13 12 2-5 Commercial, Education, Media Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API)    
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.  
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  
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)  
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  
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.  
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!  
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    
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.  
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.  
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.  
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  
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.  
69 68 2-5 Commercial, Startup Wagtail admin API, Full multi-tenancy, Live preview    
71 70 1 Non-profit Documentation, UX research & improvements, Page editor rewrite (new UI built with React and an API), Audit logging    
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  
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    
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…  
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.  
93 92 1 Education, Public sector Accessibility, Documentation, Better performance    
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  
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.  
108 107 2-5 Non-profit, Education Documentation, UX research & improvements, Multi-language    
110 109 More than 5 Non-profit, Education, Public sector Accessibility, Documentation, Live preview I think they are both realistic and high-impact.  
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.  
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.  
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.  
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.  
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.  
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.  
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.  
127 126 More than 5 Non-profit, Education, Public sector Documentation, Full multi-tenancy, Live preview Anticipated need  
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.  
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 :-) )  
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.
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
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
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
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
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!
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
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!
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.
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.
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.
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.
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.
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.
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.
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.
23 22 None   Accessibility, Documentation, UX research & improvements, Live preview I'm a beginner to wagtail, but would love to explore it Better tutorials
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
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
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
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
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
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).
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
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).
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
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.
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'
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
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
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.
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
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.
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
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.
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!
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 ...
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.
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?
2 1 2-5 Commercial, Non-profit, Education, Public sector UX research & improvements, Multi-language   More features for postgres search backend (filtering, fuzzy search)
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.
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 :-)

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