Before going liveBefore allowing the public to see your new page (or major edits) go through the following steps: Avoid common errors
Don't resize really large images to fit. Images greater that 50 kb can make the page take longer to load and is a big problem for those on dial-up connections. Also large images take up space on our server. Typically, images should be 10 kb to 30 kb. See manual for simple image procedure. Keep Images or tables 468 pixels or less. Anything wider and the page gets distorted. And it can really mess things up for older versions of Internet Explorer!!! where the page is displayed blank at the beginning. Watch out for text-wrapped images without proper spacing around them. See manual for simple image procedure. Forgeting to link an image or linking to the wrong place. Verify your links after posting. Gaps in the text, especially at the end. Remove extra spaces. Apply best practicesFollow veg.ca styles. Use the default paragraph style and other set styles for body text, heading, captions, etc. Note: you can use the eraser button to clear formatting. Identify the author if the text is in the 1st person. Respect the rules of a blog. Don't change the order of posts to keep something at the top. Instead use a sidebar or header to highlight an event or announcement. Don't make an image into a link, without also making a text link as well. Include an image (or at least a quote). Avoid excessive use of tables. Remember to save (or cancel) the page once you are finished. Otherwise the page will be locked, preventing anyone else from editing it. Apply best practices (less important)Provide links to other TVA pages when mentioned. See our Common links page for a ready list of links that you can copy from. Avoid ALL CAPS. Bolding is better. Place small images as case "right" or "left" to allow text to wrap. For really long blog posts consider breaking the page up so there a "read more" link. Break up large blocks of text with images, subtitles, etc. Self proofProofing is very important because our brain easily ignores its own mistakes. For this reason it is best to find someone else to proof your writing, but there are some techniques and tricks that can make self-proofing relatively effective.
Here is a really cool and easy way to self-proof. Get your computer to read your writing back to you. On a Mac: Open up System Preferences and go to Speech, then click the second tab called Text to Speech. Check the “Speak the selected text when the key is pressed“. Then press “Set key” and hold down on your keyboard the key (or combination of keys) that you desire (be sure not to add a combination already in use by another shortcut). I personally use F2 to make it really easy. ctrl+command+s can work if you don't have F keys. Not sure how to do this on a PC – try a google search. Get someone else to proof or at least look it over |



