MadCap Flare vs. Sanity

MadCap Flare has its problems, but it serves our team well as an authoring software. This would not be the case if we needed to regularly collaborate on articles, as Flare is prone to conflict issues when another person dares to breathe near an open topic. When working individually, though, it's fine. I'd love to see improvements to design, performance, and stability, but Flare remains one of the best softwares on the market for our needs as an authoring team. MadCap Central is well-suited to internal reviewing when every member is comfortable with Flare (the errors it tends to introduce set aside). SMEs, though, tend to find it hard to use. It's cluttered, some styles don't render, and it just seems like a failed attempt to reproduce Google Docs. I'd love to see improvements there, to help get our SMEs to want to use Central.

Incentivized

Suited for - Headless CMS - when your blogs are less in number and you want to only work within free tier - when you only want to use their dedicated location to host your CMS Less appropriate - when you need to host your cms on your cloud

Incentivized

• Organizing articles via an overall project outline.
• Syncing with teammates.

Incentivized

• GraphQL support.
• Nice Intuitive Web interface to write blogs.
• They provide us a subdomain on their cloud so that we can start testing our things directly on the web.

Incentivized

• Reviewing by internal users / Feedback from customers
• CSS - easier to use an external tool
• Skin styles and management

• CMS can be a bit hard to work with for the new users
• Documentation should include more examples of the output and code along with the output.
• Custom inputs are quite difficult to start and work with.

Incentivized

MadCap Flare is in desperate need of an overall redesign. It relies heavily on dozens and dozens of tiny buttons that contain dozens of nested features. Clicking the wrong button can cause your software to freeze and crash. Building targets can be an absolute mystery, as far as all the files involved. It also has a tendency to freeze and crash. There's typically a huge learning curve for new hires who've never used it--nothing is intuitive.

Incentivized

MadCap Flare provides for proper single-sourcing of content for an array of needs. Wikis are incredibly limited, static and hard to manage, and content quickly becomes obsolete.

- There is no fear of hitting a limit and suddenly having to start paying 500$ per month when you have been using it for free for a while - You don't have to worry about infrastructure because datasets are available as a service - With an open-source UI based on React, you don't have any limits to what you can build - For some reason, I could not find a service that provided schema as code before Sanity, and I cannot understand how anyone could think this was a good idea.

Incentivized

• Negative: Wasted hundreds of hours troubleshooting madcap bugs or quirks.
• Positive: We have a robust Help website we can update with ease.

Incentivized

• It helped us to create an excellent developer experience and good experience for their editors as well
• Sanity has created an incredible platform that effortlessly balances good DX for content modeling and good UI for content editing.
• Pay-as-you-go hybrid service, no need to worry about reaching a cap and having to suddenly pay $500

Incentivized