It was recently pointed out that the tutorial entries in howto that cover clearing cookies in different browsers haven't been update since 2003. Because we sometimes refer to these entries in answers to Support requests, it would be much more helpful if the instructions weren't so laughably obsolete.
I'd like to get some volunteers to write up instructions for clearing cookies in a variety of current browsers (see the list of old, old browsers here). Please comment with a draft, or if you have any questions or suggestions for a better way to bring the documentation up to date.
I'd like to move FAQ 176 to an s2howto tutorial. It's very complicated for a FAQ and though I'm not sure on the usage of that particular fact, it seems like it doesn't really "fit" with the rest of the FAQs in the Customization categories. Here's the text:
I have edited the Embedding: JavaScript tutorial to change language="JavaScript" in the examples to type="text/javascript". The "language" attribute has been deprecated since at least HTML 4. I've also shuffled around the closing tags so that the <noscript> tag group comes after, not inside of, the <script> tags.
Now that Release #65 is live, the Manage Settings page can be used to enter the unique code for Google's Webmaster tools. It works for all account levels, but only for personal accounts. Therefore, the Using print_custom_head() tutorial should be modified to say that communities must still go this route, but personal accounts don't.
tamar helpfully pointed out to me that Adding a Header Image -- Overview included a link to the "header image" tag using a plus instead of a space. I've gone ahead and edited the entry but I haven't looked through other entries to see if there may be broken links. If anybody else notices one, please comment here with a link
I have no idea how to format proper names/titles, etc. But this suggested grouping would work best for me when providing information to users who open web-ui requests.
I need someone to tell me how to correctly to fill in the "how to copypasta text from the command prompt/terminal" bit. I could really use this, because it's not uncommon for people to get frustrated and do screenshots instead, and (1) that means that only sighted volunteers can help answer these requests and (2) I personally cannot see the screenshots from many locations. I'm not sure if it's as complicated on MAC OS X as it is in at least some versions of Windows.
This should be filed under the existing Memory Category @ General Tutorials
