Currently, the blog is hosted at http://www.itmaybeahack.com/TeamRedCruising/ with a ton of links which depend on this base address. Folks have bookmarked http://www.itmaybeahack.com/TeamRedCruising/travel-2017-2018/ for example. And http://www.itmaybeahack.com/TeamRedCruising/links-and-resources.html.

Also. The old “refit” and “Travel 2012-2013” pages are in a separate blog at http://www.itmaybeahack.com/web/Cruising/Refit/Refit.html and http://www.itmaybeahack.com/web/Cruising/Travel_2012-2013/Travel_2012-2013.html. Also see http://www.itmaybeahack.com/web/Cruising/Team_Red_Cruising.html for the old “home” page for these various blogs.

Of course, we can’t develop over the top of the two original blog(s).

We have two fundamental alternatives.

• Redirects
• Copy Over the Top

Redirects

The .htaccess file allows us to do the following:

• rewrite all /TeamRedCruising/* links to the new blog links. If the link structures are kept in parallel, we can make this seamless.

• rewrite all the really old /web/Cruising/* links to the new blog links, also. These won’t be as neatly parallel, but can be kept similar enough to make the transition seamless.

This requires trying to keep a parallel structure. However, it seems to be workable because the structures are simple and relatively flat.

See https://mediatemple.net/community/products/dv/204643270/using-htaccess-rewrite-rules for a tutorial on the rewrite engine capabilities.

Copy Over the Top

In this case, we build the web site in one place and “simply” copy it to another place. This tends to break all the internal links, unless they’re properly relative to the base of the WordPress site.