This article was originally posted by Ryan at the original HillRunner.com Blogs.
I’m going to attempt to explain what will be going on without getting into too many technical details. Hopefully, this won’t sound intentionally vague. Sorry if it does.
HillRunner.com has been around for over 18 years. In that time, I’ve always built upon what has already existed, not wanting to rock the boat or even temporarily take away things that you have become used to having available unless absolutely necessary.
Unfortunately, that leads to a lot of old code that I wish I could clean up but, without major disruption, feel like I can’t. It also leads to problems in other behind the scenes ways, meaning I spend more time on maintenance and less on either writing for HillRunner.com or developing new features.
I’ve been looking for a few years at making some major coding changes. I’ve also wanted to beef up the security at HillRunner.com in response to security leaks other sites have faced. I don’t think I ask you for information that is all that sensitive but we can’t be too careful these days.
In recent months, certain developments on the Internet have forced my hand and I’m now left with no option other than cause significant disruption to HillRunner.com in one way or another. I have to make changes before October or HillRunner.com will be tagged “unsafe” by a major industry player and you’ll be warned that HillRunner.com is unsafe every time you do almost anything interactive at HillRunner.com.
As long as I have to make these disrupting changes, I’m also going to move forward and make the coding changes I’ve been hesitating to make. Essentially, HillRunner.com is going to be rebuilt from the ground up.
As a result, HillRunner.com will be undergoing a significant transition in September. I’m going to attempt to make this as seamless as possible but to make it completely seamless is impossible, which is why I’m devoting a weekly blog post to this.
Tentatively scheduled for Thursday and Friday, September 21st and 22nd, HillRunner.com will be moving to a new server. I will attempt to have as much of the site as possible, especially relatively static pages like the Treadmill Pace Conversions and the Calculators, up and running as soon as the change has been made. However, there may be some issues that need to be worked out. Specifically, I’m concerned about training logs and blog posts.
I’m concerned about training logs because you will need to create a new account to log on to HillRunner.com. I’m working on ideas on how to relink your account to your training log data. I’ll come up with something, even if it involves a lot of work for me. I’m going to make sure nobody who has entrusted their training logs to HillRunner.com loses their history.
I’m concerned about blog posts because we’re going to be on a new blogging software. I’m working on plans to import blog posts so we don’t lose the hundreds we already have but I’m not sure how this will work or if they will be up immediately.
I know this is a concerning transition. I’ve not done this for so long because I’ve constantly been searching for better solutions or hoping one might be built. However, my hand is being forced. Something needs to be done now, I can’t wait any longer for a better solution to be made. I apologize up front for any problems this will cause. Please know I’ll be working as hard as possible to minimize the problems.
As always, I appreciate your support and understanding. We’ll get through this and have a HillRunner.com that is better than ever in the end. Hopefully, we’ll also have one that is easier for me to maintain so I can commit more time to improving the site and adding more content to help you be the best runner you can be.