Adobe InDesign supports creating digital and print documents such as flyers, stationary, posters, and other types of media, with rich graphics, images, and more. Adobe InDesign is available standalone or as part of the Adobe Creative Suite collection of media management and creation products.
$31.49
per month
Drupal
Score 7.0 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Pricing
Adobe InDesign
Drupal
Editions & Modules
Monthly Plan
$31.49
per month
Annual Plan, Prepaid
$239.88 ($19.99)
per year (per month)
Annual Plan, Paid Monthly
$251.88 ($20.99)
per year (per month)
No answers on this topic
Offerings
Pricing Offerings
Adobe InDesign
Drupal
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe InDesign
Drupal
Features
Adobe InDesign
Drupal
Security
Comparison of Security features of Product A and Product B
Adobe InDesign
-
Ratings
Drupal
8.1
74 Ratings
1% below category average
Role-based user permissions
00 Ratings
8.174 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Adobe InDesign
-
Ratings
Drupal
7.6
69 Ratings
2% below category average
API
00 Ratings
7.264 Ratings
Internationalization / multi-language
00 Ratings
8.160 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Adobe InDesign
-
Ratings
Drupal
6.5
78 Ratings
18% below category average
WYSIWYG editor
00 Ratings
6.171 Ratings
Code quality / cleanliness
00 Ratings
8.175 Ratings
Admin section
00 Ratings
6.878 Ratings
Page templates
00 Ratings
5.577 Ratings
Library of website themes
00 Ratings
5.468 Ratings
Mobile optimization / responsive design
00 Ratings
6.572 Ratings
Publishing workflow
00 Ratings
6.876 Ratings
Form generator
00 Ratings
6.372 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Adobe InDesign is very well-suited to creating professional-looking page designs. If you want a newspaper or magazine to have attractive pages that go beyond simple templates, InDesign is the best option out there, to my knowledge. It's less suited to scenarios where people without page design skills are responsible for creating pages, as it requires some training and skills to use effectively.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Customization - With Adobe InDesign, as well as many other applications in the Adobe Creative Suite, I can fully customize my workspaces and save different workspaces. This makes it easy to navigate through my project and have the panels and tools I need easily accessible and configured based on my project needs.
Styles - Adobe InDesign has character styles, object styles, and tables styles. This speeds up my workflows and allows me to easily apply the same format across multiple elements. This is super helpful, especially when working with length documents.
File compatibility - I can easily export my files into so many different file types.
The Book feature - This feature is really helpful when creating books or very long documents with multiple sections.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
I've had great experiences with the product and plan to continue to use it. It has been my go-to product for designing and creating materials. I have had great luck with it and have been able to create all of the needed marketing materials that have been requested for our company.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
If you know what you are doing it is an amazingly granular and powerful application. You can control pretty much any aspect of the design and layout of your documents and make changes globally and rapidly. But, if you don't know what you are doing...you will be staring at your screen in bewilderment for a long time. You can learn it, but be ready for a hefty time investment.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
Adobe support is ok but not great. Chat support often doesn't initially understand the question at-hand and it takes awhile to get to the right agent. Phone support has long wait times, and though I've had more luck there, it does take quite a time investment if you are looking for help. However, Adobe does have some online learning solutions available as well as a knowledgebase for frequently asked questions. If you're looking to learn how to use the platform, there are lots of resources which can typically be found in a few Google searches. If you have a technical issue with the system, that's going to be a bit more of a time investment as far as getting a tech's assistance to resolve the problem.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Microsoft products do not match the aesthetic tools that [Adobe] InDesign offers, cannot support the customizable options available for export, and do not produce documents with as high a degree of accessibility. That said, they do have their place in collaboration in a team- I'd consider Office to be the first step and [Adobe] InDesign to be the final product.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
A great ROI for time in my small architectural practice, [especially] when a design has been updated and a report needs to be submitted. We can be submitting many reports that all look similar, clean and beautiful. We just save as the file and replace the images with more updated images. This way the client finds it easy to navigate updated reports, as many as they can be.