Ezvid Wikimaker Style Guide Part Two
This is part two of the Ezvid Wikimaker Style Guide. Here you will find more of our editorial standards for writing and image selection along with techniques for how to incorporate Wikimaker's features to create entertaining and informative videos. If you are ever unsure of something, always refer back here and read the full style guide. Make sure you've watched part one, and after you're done here, move on to part three to learn more. This video was made with Ezvid Wikimaker.
What Rules Are Covered In This Section Of The Style Guide?
- Don't Use Full URLs
- Don't Use Exact Prices
- Avoid Dashes
- Don't Randomly Capitalize Words
- Learn When To Use An Apostrophe
- Don't Write Marketing Copy
- Don't Use Repetitive Language
- Don't Directly Refer To Images
- Use Acronyms With Caution
- Don't Upload Low Quality Images Or Image With Text
- Use Screen Captures Instead Of Logos To Represent Companies
- Use Landscape Photos, Not Portrait
Where Can I Find Some Examples of Well-Made Wikis?
You can find previously published wikis made with Wikimaker on this page. It's always a good idea to watch other videos to get new ideas for making your articles and videos more entertaining.
What Are Some Good Additional Resources On Grammar?
- An article on the passive voice and how to avoid it
- The rules for capitalization in English
- A guide for when to use an apostrophe
- The Chicago Manual of Style
Where Can I Find The Other Sections of The Style Guide?
Ezvid Wikimaker has many standards that you should be familiar with. If you've already watched part one of the style guide, you're ready for more in-depth rules regarding wiki creation.
You may reference websites in your wiki, but when you do so, shorten the URL to remove elements like "http." For example, if you are discussing Apple's website, instead of "https://www.apple.com," which takes a long time, simply say, "apple.com." This avoids slowing down the video with cumbersome text.
When discussing products or services, don't use exact prices like $19.95 or $79.99. These are likely to go out-of-date quickly, and become inaccurate. Instead, use general amounts like "about $20" or "less than $100."
When discussing products or services, don't use exact prices like $19.95 or $79.99.
When possible, avoid the use of hyphens or dashes. Our voice synthesizer often has trouble working out how they should sound. Generally compound words like "pain-free" might work, but writing "five-ten people" when referring to the number of people present will not work well, because it can't figure out how to vocalize the dash. Instead, write "5 to 10" and make sure to listen to the vocalizations.
In addition to being heard on the video, everything you write will also be read as text in your wiki. That's why it's crucial to use proper grammar. Don't capitalize words that shouldn't be capitalized. You should also be familiar with the difference between "It's" and "its," as well as the different forms of "your" and "there." Read up on these rules and always proofread your work.
Your tone must be neutral, balanced, and well-considered. It should never sound like you are advertising a product or regurgitating marketing copy. Any sentence that sounds like something you'd hear in a commercial probably isn't right for your wiki.
Any sentence that sounds like something you'd hear in a commercial probably isn't right for your wiki.
Repetitive language is an easy mistake to make when discussing products. If you're writing about iPhone apps, every sentence should not have the words "iPhone apps" in it. In fact, not every paragraph should say "iPhone apps." It sounds very repetitive when "iPhone apps" is repeated through vocalization. Find another way besides "iPhone apps" to talk about iPhone apps. Look at this paragraph to see the problem.
Some people may wish to read these without watching the videos. Therefore, the text of your wiki needs to be able to stand alone, without the accompanying video. Never use vague or time-specific references to things happening on-screen. Saying things like "Next, you'll see this screen" won't be helpful. Be specific and describe the screen for anyone who won't be seeing the image. For example, "Next, you'll see the iCloud login screen."
Our voice synthesizer is good, but not perfect. For example, with acronyms like FWIW and IMHO, it can get confused. Sometimes it might try to pronounce these as words, instead of one letter at a time. Listen back to your Wiki, and if you notice this problem, try inserting periods between each letter of an acronym, like T.G.I.F. and A.S.P.C.A., which will sound correct.
Our voice synthesizer is good, but not perfect.
Images that you upload to Wikimaker must be directly relevant to your subject matter. If you're writing about PayPal, don't add general images of computers and money. Instead, show the actual PayPal website. Don't upload obvious clip art or anything low quality. You should also avoid images with text on them. In general, it is always preferable to use screen captures and recordings of specific actions described in your wiki.
Avoid the overuse of logos to represent companies. If your wiki is about a Facebook product, you'll be talking about Facebook quite a bit, and simply using the Facebook logo or Facebook messenger logo will make for a really boring video. Instead, do some screen captures of the Facebook website and mobile app or some screen recordings of you actually using the Facebook website to demonstrate it for the viewer.
You should always use landscape photos, not portrait ones. Landscape images are defined as images that are significantly longer than they are high. Images uploaded to Wikimaker should ideally be in the 16:9 aspect ratio. Images of other aspect ratios will be rendered into video with black borders around them, which doesn't look as good as using the entire screen.
Images of other aspect ratios will be rendered into video with black borders around them, which doesn't look as good as using the entire screen.
Also pay attention to the resolution. Ideally, you should be using 1280x720 or better to avoid "fuzzy" images.
When dealing with historical topics where better-quality photos aren't available, using portrait-formatted pictures or those with a lower resolution are better than not using any pictures at all. What's most important is that they are relevant to your topic and convey the necessary information.
Don't attempt to use external editing software to "squash" images into landscape format. A few images with black bars are better than pictures that look stretched. We do recommend that you use Wikimaker Capture to gather the majority of your uploaded images. As long as you frame the image correctly with the software, you won't ever have to worry about issues with aspect ratio.