4 ms·

Which blogging platform should I use?

• Mrt009 5y ago
  I am using BOWWE, designed my website, and then hosted the blog there. Besides medium, maybe you could also consider Hackernoon.
• gmzi 5y ago
  You might be interested in this bare bones platform I built: https://github.com/gmzi/blog-demo https://github.com/gmzi/blog-demo Hope it helps!!!
• codeptualize 5y ago
  Just to throw it out there; a static site generator with markdown could also work for you. Next.js or Gatsby with markdown or MDX for example, there are many good options. I would say you can't go wrong with any of the options you mention, they all are great in their own way. I suggest to just try a bunch and see what you like.
• thebaer 5y ago
  You might like what we've built with Write.as [0]. It's Markdown-based, but without all the publishing overhead of a static site generator. There are a lot of other great small platforms that are made especially for blogging, rather than being general-purpose like some of the options you mentioned. E.g. Bear Blog [1] and Svbtle [2] [0] https://write.as https://write.as [1] https://bearblog.dev https://bearblog.dev [2] https://svbtle.com https://svbtle.com
• calltrak 5y ago
• kevincox 5y ago
  I think the platform matters a lot less than the domain. Make sure that your blog and feed are on a domain that you control. Then you can always switch platforms later if you find that your current one isn't working for you. After that the most important thing is just to start writing.
• sjtindell 5y ago
  After trying Bluehost + Wordpress (easy to buy and get started, but required learning Wordpress) I set something up with Hugo + Netlify. Free, and super easy. Static, very understandable. Look up a simple getting started guide, there are many. I use namecheap for my domain, you can use any obviously.
• pygar 5y ago
  I ended up building mine with extremely standard html/css (no js but that was by accident). I didn't want to fall into the old trap of the writer who obsesses over his tools and never ends up writing anything. Basically I just copy the previous blog entry, change the content and update the index page with a new link. The entire prep doesn't take more then two minutes. I don't have features like tags/rss, although I guess I could do those manually too, but the way I see it, I'll worry about that when/if I have enough content. I'm hosting it on GitHub pages because it's free but I could copy the folder onto any web server and be good to go. I was just checking out neocities which is pretty cool and works in a similar way. https://neocities.org/ https://neocities.org/
• deleted 5y ago
  [deleted]
• farmin 5y ago
  I'm currently trying ghost. Once you dig into it it has a pretty neat templating system.
• ussrlongbow 5y ago
  Try any and keep blogging. Once you progress in making your content, you will better understand your needs, which will assist in a better decision: either keep current platform or pick a better one for your blogging needs.
• umtksa 5y ago
  jekyll - markdown files pushed , builded and deployed by github pages
• lovelearning 5y ago
  I feel it depends on your audience goal and type of content. If your goal is to build up a list of followers and build connections with potential customers and employers, go with Medium. Its recommendation system gets you followers quickly without any additional effort. Medium articles still show up in google searches if they're somewhat relevant, something I don't see happening with any of the other platforms. One drawback - it sucks for posts that contain code or demos. Alternate goals may be 1) Maintaining a portfolio to send to potential customers and employers. 2) Or maintaining a journal of ideas and learnings primarily for your future self. Turning up in search results may not be your priority with those goals. Then, the type of content becomes the dominant factor... All the SaaS platforms - wordpress.com, Weebly, Webflow, Ghost, Medium - kind of suck for technical content containing code and JS demos. Self-hosted WP is more flexible but you'll often run into formatting and small screen glitches. For tech content, I'd prefer writing in markdown/asciidoc formats and publishing using static site generators like Pelican, Hugo, Gatsby. You have to be ok with using the command-line for them. For non-tech content, any of them is fine. Webflow's layout system seems the most flexible and good-looking among the lot. Free WP.com, Medium offer rather limited customization.
• olaven 5y ago
  If you want to write markdown and use something really simple, I feel it's appropriate to mention Markblog[0], a blogging engine I wrote a while back. I've also written a short guide where I combine it with Github Pages for free hosting and Github Actions for automated CI[1]. [0]: https://github.com/olaven/markblog https://github.com/olaven/markblog [1]: https://olaven.org/out/guides/blog_with_git_and_markdown.html https://olaven.org/out/guides/blog_with_git_and_markdown.htm...
• brtkdotse 5y ago
  Stop. Forget platforms and formats for a while and try to write at least 3 blog posts as plain text files/Word documents/Google doc. If you can’t write those three articles, forget about getting a blog because it will be forever empty. Speaking from experience.