 I'm actually just a web developer that works both Drupal and WordPress. I've been doing Drupal since Drupal 5 and I've been doing WordPress like nine years, since like nine years ago, and it's still going. I'm kind of an odd one. I kind of like both of them. I don't have this kind of preference which one you like most or whatever. I like both of them in a sense, like both of them has different capacity and actually challenged me a different way. So I prepare a very generic what suits best for individual WordPress or Drupal. So very obvious, Drupal, very good with for medium to large build. And as for WordPress, it's only for small to medium. There is a lot of component in there that sort of not very friendly for developers. So it's really hard to get extension and also it's not really a bug. Like they always have lots of bugs and things coming through. And obviously, Drupal doesn't have e-commerce at the moment for Drupal 8. So I really missed the Drupal 7 ones. That was really good. WordPress has e-commerce and obviously that one is just like an extension for it. And it has been doing really, really well and it's always out there. People start, you know, when new startup they need e-commerce, they will go with WordPress. That's what I see because that's how easily it can be started off from there. For Drupal, it's more complex on data structures and workflow, so it works really well with that. But for WordPress, it's only works well for simple data structure and minimal workflow because WordPress doesn't build for that and everything that they have over there is very minimal because it's all based on marketing strategy kind of stuff and also SEO kind of element. So that's the reason why it's really different when I work with Drupal or WordPress. When it comes to design, Drupal is always, you know you have to design based on the Drupal structure otherwise things doesn't work pretty well that way. But obviously you can do headless Drupal. That's another section for it. For WordPress, it works with any design because it's just sort of like a plug and play. So that's a lot of design out there. You can just do it with theming and stuff. And they already do headless WordPress. So a lot of developers, a lot of designers start going into a dead path. And when it comes to budget, so obviously Drupal require bigger budget and it's more expensive to develop in that sense. But when you compare to WordPress, it's cheaper. It can, you know, it's just easy install and then get it up and running and then off you go with all the themes and stuff that you can do with it. So both are customizable. You can do a lot of extension plugins, module and anything that you want to do. You can just do that from there. But one thing I really see is like Drupal has a really steep learning curve. You know, when somebody new coming in even though they have PHP background or my SQL background, but they still need to learn the structural way of Drupal how it works and stuff. But when it comes to WordPress, it's really easy to pick up, easy to learn because everything is just function, just PHP. Basically that's it. And I'm just coming through with this, you know, Drupal versus WordPress in a whole structure way. So first thing first, looking at the core files. WordPress is very lightweighted. It's only like 14 Mac with the zip file compared to Drupal 9 core is 28.3 Mac. And that is like, you know, the thing to see like how small and how lightweight it is WordPress compared to Drupal. So that's what you can see from here. And then when it comes to database, WordPress like to use serialized format. So all the, that's the reason why they are really compact because they use serialized. And it's, and also another way of like, it's really hard to sort of create a data structure from that because everything is serialized. It's really hard to debug when you need to debug as well. And also for the config structure, it actually have one table store all the config in there and all with serialized. You need to like find the name of it and then you need to go and pinpoint and get through it. Webis and Drupal is really clear. All the database is relational databases. It's all out there. You, if you want to debug back and it's easily to debug, you don't have any, you know, you don't have to worry about something that might corrupt it or whatsoever because it's really unlikely. Well, where I, you know, WordPress because it's serialized if, you know, one part is like extra semi-colonel, whatsoever, it's not going to be working. So that is another different pro and cons in there. And when it comes to security, it's always hands down with Drupal. Drupal always better security compared to WordPress. But WordPress rely on external plugins which you call WorkFence. And that one actually works really well with WordPress and make it really secure. And WordPress is already well-known easily being hacked and a lot of malicious codes. So that's another hands down for Drupal. And yeah. So moving forward to core modules and plugin updates. For WordPress, I really like it when they have auto updates, which means that the module, you know, when the core needs to be updated, it's just auto update. You don't have to worry about it. But obviously that's another downside of it when doing the automated update, in a sense like you wouldn't know the newest version will work well with your plugins. So for example, I think during 5.0 versions comes out, that wasn't really fully tested. And a lot of other plugins was like broken. So what happened is like the core team has to like really roll out the second version like within two or three days just to fix that. So it's kind of like that section, they have that, you know, perfect for auto update, but at the same time, they're not fully tested. So that's another issue at WordPress, but whereby in Drupal, everything has a security tested. So everything has to be tested 100% before rolled out. And obviously, you know, as a developer, you know, you just have to go in there and then making sure it works for you before you release to the production side. So that's the pro and cons on the auto update. I like it in a sense if it's really minimal, like for example, just update plugins or module that will be great. And that way, you know, minimal way to manage and then making sure everything is fine is going through because it's the module update. Obviously, when it comes to like bigger version, everything has to be precautious in that way. And next one is actually the modules and plugins, how is actually the difference that I see in the sense that the community spirit in a way. For WordPress, everyone seems to do their own work, like they just create multiple plugins. You can see multiple, like if you search Instagram, you can see multiple Instagram plugins out there. Like there's no sort of like saying which one is the best one to do, which one is the, you know, is a great one because there's nobody sit there and say like, this is duplicate, you shouldn't believe that and those kinds of stuff. But compared to Drupal, because it's restricted in a sense that, you know, if it's duplicated, people will say it's duplicated, you shouldn't go with that or showing which one is the best plugin to use for. And because of Drupal has the security testing going on, it's actually very robust. You know, when you don't have to worry about that plugin will ruin your site or will actually introduce some malicious code or whatsoever. But for WordPress, there's no security testing. It only able to test like which version of core that it works for and which PHP version that it will works with and stuff like that. And then off you go, you are the main tester. If anything's that being hacked, then you are the one that, oh no, this is the module that's not good for me. I have to get rid of it. I have to clean my site now. So that is the pro and cons on that. But the pro on WordPress that I see, the way that they structured the module, they even have those tabs in the different tabs, like, you know, having the installation info telling you how to install it and also having the support channel over there, which means that people who find any bugs, they just go to that support and then just immediately, you know, put in their comments and what they find and stuff and it's all condensed in one place. So it's easier for the maintainer to look into it and then to pick it up and respond. And obviously the difference is, through code you can actually create a patch. So you can do patching and stuff, but for WordPress, there's no capabilities to do that. So it all depends on the support channel that you talk to the creator and then the creator will do the patch on that side. So that's the difference on what I see as a module. And as for REST API, WordPress core came with it and it's already enabled by default. Where by Drupal you need a module, you know, to hook onto it and then get it working. So WordPress is already there, it's out there and people has been using this concept to create headless WordPress or, you know, headless theming, all those kind of stuff and it works really well with a lot of API integration that's go around it. So you can actually do a lot of integration easily just with WordPress. So when it comes to content migration, I find that WordPress content migration is very, very simple. You can just easily export the content and it's actually in XML format. And for example, WordPress version three and WordPress version five is such a huge different version. But if somebody wants to upgrade it straight away to version five, what we need to do is actually just export the XML file, do an import into the new platform and then off you go. But obviously when it comes to, if there's certain custom content type that's been created or whatsoever, that will be need an extra step to do migration. So, and then comparing with Drupal that I have some experience with which is migrating Drupal seven to Drupal eight. It was a little bit of a nightmare and it's required a lot of time. But although thanks to the Drupal migration module, it's sort of not that bad, but obviously hopefully it's not gonna have this kind of headache in the future. So that is the only thing that I want to raise that for. So when it comes to media library, this is the one I'm pretty excited with. I find that WordPress is very simple, the way that they deal with media library, the way that you can list and look at if it's a thumbnail, you can look at the picture straight away or you can list it out, that's not a problem. But only thing that they don't have file revision, so which means that if the file being deleted or you need to replace a new file, it just deleted immediately and there's no source of finding out what happened to the old file or is a mistake of removing it, you couldn't get it back. So the only thing you can get it back is actually through your backup file, but obviously depends on how long you backup your file or how often you do that. And also they haven't easily replaced images, which means you go to the media and then you just remove the image and then you just upload a new file and off you go. So which is really cool. And they do have like both upload as well. So when the the con is actually, you can't create a custom media types, but you can't say that I want to create an album, album one, but you can't do that. So it's only restricted to library and it's as a whole include video. So you can't even say that I only want video in that section, I only want this one in images, you can't do that unfortunately. And also you can't create a custom view. So anything that you want to expand from there, you can't do it, it's all defaulted with WordPress. So that is the difference between Drupal, Drupal, we can do that, that's not an issue. We can just modify based on what we want, based on the field and everything. So which is great. So this is how it looks like for the media library and that's how it is. And then you can search, you can do a box select just to do something else. And then when it comes to embedding file, it's pretty cool. You can actually create a gallery, you can create an audio playlist, video playlist, and then you just embed into the body content and it just be there. And also you can embed like vmail, YouTube using the insert from URL, and it just do responsively. So it's all there as a core and it's pretty cool. And then for each images, there's already a pre-sets of fields that they give it to you. Like what I mentioned previously, you can't create a new custom field. It's all pre-made over there. So obviously this is very useful for SEO, marketing as well and all this kind of stuff. And that's why it's there. So let's move to user row. User row, hands down with Drupal, Drupal, amazing. I wanna take it away. Rows is the best to do work on any CMS whereby WordPress is not that great. You need to go through an external plugins to get it work on commission row. But obviously it's not that straightforward like what we see on Drupal. The way that they do the rows is very minimal. You can, like it's just saying that you can edit, view or delete and that's it. So it's not really like something comprehensive that was done in Drupal. So that's the totally hands down for Drupal to having that sawed out and it's like the best thing ever. And when it comes to content type, well, Drupal comes with it. It's already part of the core. You can create multiple content type, multiple custom fields, not an issue. It just work as it is. But for WordPress, you have to install an external plugins just to make it work. And same thing, you need to, not only install one, you have to install two because one is to create a content type. The other one is actually to create a custom field. It's like you just walk down with two plugins. So it's like extra overhead in that sense. And when it comes to path auto or parmolink, they call it parmolink in WordPress, is actually comes with it. So WordPress comes with it with the core, but the only downside is like, you can't configure it based on content type. So everything is just very level one. There's no level two, level three. Unless you actually define that saying parents, then you will get the parents URL and then append to the child URL, that kind of stuff. So it's not that great. I would still like Drupal, although it's extension on the module, but it still works great for Drupal in that sense. Now, when it comes to content workflow, I wouldn't stress more. Drupal is the best on content workflow, having the way that we create, how to drive, publish, and then archive, or whatever content workflow you wanna create, that's fine. But for WordPress, it's not that great. It's very, like I say, it's very level one. What you can do is only like publish, unpublish, or send it to Drive, but the only cool thing that they have is actually sex scheduling, unpublish, like for example, you create a content, but you don't wanna publish it now, but you wanna publish it tomorrow at six o'clock. You can schedule that, and then just work brilliantly for you. But obviously, if I could, I would prefer WordPress to have like a workflow like Drupal. That way, you know, when whoever creates something that is already published, and then if there are any changes, we can just save it as Drup, so that the new change will not be reviewed by anyone, and then the old change will still be out there, as a system, but unfortunately, WordPress doesn't do that. You can either publish or Drup or delete, so that is the downside of it. And my conclusion comes in, in a sense like, if a website, if you need a website that is small, with a really tight budget, WordPress is the best choice to go for, and if you need e-commerce and stuff, WordPress is the way to go, but if you have a complex design, bigger budget, if you can afford it, Drupal is the best choice to go for, and that's the only thing I can think of. And also one thing is a silly thing that I think, if one day, Drupal and WordPress decide to collaborate together, it would be great to see a hybrid at CMS, because both of them has a pro and cons in that sense, and it would be great to really see the hybrid going on, but I don't think that will be happening.