Choose tools for the work, not the wishlist.
A useful way to evaluate software starts with the task you repeat, not the feature comparison chart.
A long feature list makes a tool easy to admire and surprisingly hard to evaluate. A more useful starting point is a specific task you need to complete repeatedly.
Write down the ordinary day
Describe the work in plain language. For a blog, that might be drafting an article, checking a preview, correcting a sentence, and publishing the result. Be specific about the steps that cause friction.
Then try the tool against that sequence. How many decisions does it introduce? Can you recover from a mistake? Is it clear what has been saved and what has been published?
Test the exit as well as the entrance
Importing content is only part of the decision. Look at how you would export it, move it, or read it without the original application. Familiar formats can make a future change easier.
Keep the evaluation small
Use one representative piece of work. Complete it from beginning to end. Note where the tool helped and where it got in the way.
The right tool is the one that supports your actual routine well enough to keep using. A feature you never need cannot compensate for friction you encounter every day.