3 ms·

For this sort of application I always recommend a hosted blogging service (wordpress.com, tumblr.com, blogger.com, etc) so that if something affects your server

• dkokelley 19y ago
  Good point. Both arguments (mine regarding hosting your own blog, and yours) are quite valid. I assume this means linking to it on your site. But if your server goes down, your users won't be able to get to it anyways, unless they have your blog address memorized or bookmarked. Your site should never be allowed to go down for long, unless something major happens, in which case a backup plan is ideal. I would host my own blog, and if my server does go down, redirect the domain to a stable site with a brief explanation of what's going on, and then when every thing's back to normal post about it in the company blog.
  • lacker 19y ago
    Users will be able to find it, because if your blog is on a different domain, it will probably be somewhere on the first page of google results when you search for your company. I would just keep the blog somewhere like wordpress because they will have a more fully functional blogging engine. Don't spend your time managing your blog software, spend it making your product better.
    • dkokelley 19y ago
      I guess the best way would be to have blog.yourdomain.com redirect to yourblog.bloggingwebsite.com.
• brlewis 19y ago
  That's good reasoning, and is what I would have done, until I realized that I'm competing with blogging platforms almost as much as I'm competing with photo-sharing sites.