How to best swap from old web page to...

User 2658826 Photo


Registered User
1 post

Old web page is hand coded - I want to start creating the new page using your tools. Do I create a new set of fake directories and create all the files and then just dump them onto the web when complete - or

create them 1 by 1 in my real directory and they can replace the old ones as they are complete and there will be a mix of new and old? How would that work. The old files are a mix of dreamweaver, Home site, hand code, and other.. It works, and not too bad - but pretty ugly to look at, and just too difficult to update anymore, and looks ancient.

TIA -

>>>Rod<<<
User 122279 Photo


Senior Advisor
14,567 posts
Online Now

What I often do, is creating a test folder on your server and then upload everything to that, including the folder structure you want, thus leaving the current site in peace until the new one is ready to go live. Then I wipe the server clean and upload the new site to where the old one was.

My reason for doing it this way is simply because of possible errors, I don't want to be without a working site while I trace and debug those errors.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 2147626 Photo


Ambassador
2,958 posts

And I'd make a backup of the original site, just in case, before you wipe it from your server...:D
Graphics for the web, email, blogs and more!
-------------------------------------
https://sadduck.com
User 474778 Photo


Registered User
215 posts

rkenly,
If all of that site history makes you not so confident about which files are actually getting visited / used online, consider "scraping" your site:
  • Indeed, SAVE THE EXISTING SITE just in case of error.
  • Create a new directory to house your new, cleaned-up site.
  • Visit the existing, old site page by page via browser. For each page actually in use, use the browser's source-examination tool to copy the HTML, then paste it into an appropriately named new file in that new directory.
  • Use other built-in browser tools to learn the names of CSS, image, Javascript and other resources that the page depends upon. Methodically copy these into the new directory. (You may have to create some sub-directories in order to put everything where it belongs.)
  • Temporarily rename the directory containing the exisiting site, so that code in your new site can't find the exisiting site's contents. (This is to prevent confusion.)
  • Visit every page of the new site exhaustively to ensure that everything you need is in place.
  • Now you can give the new site's directory the name you had been using for the old site. By all means, test again before you blow away the old directory.
The beauty of "scraping" is that it uncovers exactly which resources are relevant.

No prep is needed in order to use the CC HTML Editor. It speaks all HTML and CSS dialects.
halfnium -AT- alum.mit.edu
Yes, I looked just like that in 1962.

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.