Issues With a Magento Blog in WordPress
The great thing about WordPress is that it’s very easy to set up and offers an abundance of features. If you wanna blog about anything—be it Magento, e-commerce, or any other fun topic you fancy—you can just go to the official WordPress website and set one up.
However, if you’re also running a site based in Magento, running a blog in WordPress can be a little tricky. Here are a few of the issues that our bloggers often encounter…
In WordPress, making bullet points isn’t as straightforward as you would think… In this point alone, it’s a problem. Here’s how to fix it:
Switch the tab on the top right of your WordPress article from ‘Visual’ to ‘Text.’ That way you can go into the CSS and add those <li> tags that you need for the bulletpoints to go in. Then, make sure you save the post in the ‘text’ tab. If you switch back to ‘visual,’ the bulletpoints will just get messed up again…
By the way, this is probably the most common problem when writing in WordPress.
Headings are a weird thing, but it depends on the style of your blog. If you want to read about the differences between the H1, H2, and H3 tags, Yoast has a lot of good resources.
On our blog, the main problem is our H1 tags look dangerously close to the title of the blogs… So if I make the next text
something like this
you’ll notice that it looks too much like the title of this blog post, which is something that we like to avoid.
Finally, the weirdest thing about a Magento blog in WordPress is scheduling the blog posts. You’ll notice under ‘Publish,’ there’s an option that will allow you to publish the posts whenever you want. Usually we just schedule a lot of our posts ahead of time because we happen to write a few of them a day, so we like to keep them running on a day-to-day basis.
But if you decide to do this for your company, you have to be careful, because accidentally scheduling a post on a day that you don’t want them… Well, let’s just say that enough of our bloggers got a looooooong talk from the boss about such a mishap.
You must be logged in to post a comment.