I've worked on converting some large sites to AMP and it has been good for the HTML quality on the sites. My sites are generally dynamic, but contain user submitted articles and comments so it's been a two step process. Ensuring that the template and navigation of the site is AMP-friendly. And then working through errors which are flagged in user content. It's been a lot of work, but it has also found a lot of errors which have been on the sites for years in some cases since they would sometimes pass less strict HTML validation.
I recommend the Chrome Extension which can be found in the menu here: https://validator.ampproject.org/ <https://validator.ampproject.org/> For AMP pages it performs an automatic syntax check. It also makes it easy to jump to the AMP equivalent of a non-AMP page. [fletcher] > On Feb 21, 2017, at 7:00 AM, Greg Raven <[email protected]> wrote: > > AMP seems better suited to programmatically-generated web pages, not manually > maintained static pages. The main problem I have with AMP for static pages is > that there is no way to validate AMP code ... each page will generate a bunch > of errors due to AMP's non-standard HTML. Some of my static sites have tens > of thousands of pages, and there's no way I'm 1) purposely creating erroneous > code on each page, or 2) wading through a super-massive syntax error report > hoping to winnow out the few non-AMP errors. YMMV. > > On Tuesday, February 21, 2017 at 3:26:53 AM UTC-8, Bill Kochman wrote: > One way to avoid a lot of the <body> clutter is by converting your website > over to the AMP — Accelerate Mobile Pages — standard, which is what I > recently did with my primary website. > > It was a lot of work — and very challenging and frustrating at times due to > my own lack of knowledge — but I believe I made a wise choice. > > The thing about Google’s AMP specifications is that while most of it is > standard HTML tags that we are familiar with — with a few new ones, or > replacement tags thrown in the mix — it is also VERY strict, and a lot of > standard HTML elements are firmly disallowed. For example: > > java scripts and java applets > background images > gradients > external stylesheets > inline font styles > table summaries > image borders > etc. > > So how does this relate to your case? > > Well, for one thing, you cannot even use the <font> tag in the body of your > AMP-compliant HTML document. All styling MUST be done in the head section of > each HTML. The end result is that you have a MUCH cleaner and LESS > complicated body section, where you will primarily use classes instead. > > Not only will your pages be cleaner by converting to AMP, but they will load > faster as well, which offers its own array of benefits for a webmaster. For > example, with Google’s PageSpeed Insights tool, all of my pages average 87 to > 95 on a scale of 100, depending on whether I am looking at the mobile page > score, or the desktop page score. > > Regarding that long string of closing </div> tags you are experiencing, my > personal approach is to close a <div> tag just as soon as it is no longer > needed, thus avoiding as much as possible, what you are now experiencing. > > I don’t know if any of the above will help you or not, but there it is for > what it is worth. > > If you are interested in AMP, you can get a start here: > > https://www.ampproject.org/ <https://www.ampproject.org/> > > Oh, I also highly recommend that you look into Jim Derry’s “Balthisar Tidy > for Work” in the App Store. It is only $8, and is a very wise investment, in > my view. > > Kind regards, > > Bill K. > > > On Monday, February 20, 2017 at 5:32:16 PM UTC, James Lee wrote: > >> I still have some code created buy Adobe GoLive editing. There seems to have >> been a flaw that caused duplicate vids and extra spaces so the pages have >> become almost impossible to edit. Here is an example: >> ----- >> >> <div align="left"> >> >> <p><font size="4" >> face="Verdana,arial,helvetica,sans-serif"><font size="3"><strong>"One of the >> greatest discoveries a man makes, one of his great surprises, is to find he >> can do what he was afraid he couldn't do." - Henry >> Ford</strong></font></font></p> >> >> </div> >> >> </div> >> >> </div> >> </div> >> </div> >> </div> >> </div> >> ----- >> This index file is not very wide (feet, not inches). I am hoping BBEdit has >> some tricks I have yet to find to fix this problem. Ir maybe there is a way >> to go back to Adobe GoLive and fix them. Any ideas would be appreciated. >> >> -- >> This is the BBEdit Talk public discussion group. If you have a >> feature request or would like to report a problem, please email >> "sup...@ <>barebones.com <http://barebones.com/>" rather than posting to the >> group. >> Follow @bbedit on Twitter: <http://www.twitter.com/bbedit >> <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 bbedit+un...@ <>googlegroups.com <http://googlegroups.com/>. >> To post to this group, send email to bbe...@ <>googlegroups.com >> <http://googlegroups.com/>. >> Visit this group at https://groups.google.com/group/bbedit >> <https://groups.google.com/group/bbedit>. > > > -- > 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] <mailto:[email protected]>" rather than posting to > the group. > Follow @bbedit on Twitter: <http://www.twitter.com/bbedit > <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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/bbedit > <https://groups.google.com/group/bbedit>. -- 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.
