On Feb 22, 2017, at 1:58 AM, Fletcher Sandbeck <[email protected]> wrote:
> The trick is to figure out what the problems are and then apply those fixes > to all your pages using BBEdit's multi-file search/replace. However, finding > the errors is easier than fixing them. Exactly. I have massively used BBEdit’s multi-file search and replace option countless times over the past few weeks as I have updated to the AMP and SSL/TSL standards. I have also learned a few important lessons along the way as well. One thing I would tell anyone who has a mature, aged website, and who is thinking of converting to the AMP standard and specifications, is to follow what I personally refer to as consistency, continuity and standardization. In my case, my website is twenty years old. Over the years, as my HTML coding skills have improved, I have changed styles and techniques many times. As a result, until I recently fixed everything -- by standardizing my code across the entire site using BBEdit’s multi-file find and replace — my HTML code was very uneven. Because of the uneven code, there have been a number of times where performing a certain global find and replace would correct something, but break something else, thus doubling my own work. For example, having absolute URLs in some places, but relative URLs in other places, can wreak havoc on your site, if you are not careful when you perform global find and replaces in BBEdit. After conducting a lot of online research, and seeing what a divided camp exists, I finally just decided to use absolute URLs everywhere. That way, I know for sure where things are pointing to, and Googlebot will know as well. What I soon realized is that it is a lot wiser to work on individual directories — as opposed to the entire website at once — and make very specific, targeted changes incrementally. In short, before you even consider converting your site to meet AMP standards, take the time to standardize your HTML code, particularly if it is a very old site with a lot of different coding styles and approaches. It will be a lot easier to convert to AMP specifications if you do that first. This is precisely where using BBEdit and Balthisar Tidy for Work together has saved me so much time and effort. They are both invaluable tools for the webmaster. > As someone else mentioned what you might consider is modernizing the code > generally. If you search for that face="Verdana..." string you'll probably > find that it has been inserted many times in your code. Instead you can > create a class in your CSS and work through the site applying that style to a > new <span> or even to the surrounding <div> and cleaning out the old code. > That will make a more maintainable site moving forward. > > [fletcher] I agree, Fletcher. Modernizing and standardizing all of your HTML code is definitely the way to go. Doing so will indeed save you a lot of headaches and frustration in the future. Kind regards, Bill K. -- This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/bbedit.
