48 rows where How many sites do you have running on Wagtail? = "More than 5"

View and edit SQL

Suggested facets: What kind of organisations are your Wagtail sites for?

How many sites do you have running on Wagtail?

  • More than 5 · 48
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 :-)
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
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
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.
18 17 More than 5 Non-profit, Education, Public sector Built in SEO fundamentals    
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.  
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.
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
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).
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.
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.  
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.  
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
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.
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.  
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    
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).
94 93 More than 5 Non-profit, Culture Wagtail admin API   Support for proxy models, PDF inline view, stabalization of the API
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.
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!
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.
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
110 109 More than 5 Non-profit, Education, Public sector Accessibility, Documentation, Live preview I think they are both realistic and high-impact.  
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
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'
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.  
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
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.  
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.  
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!

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