Golden rule: upload the images natively to TNWiki and keep them shining. You'll quickly notice that this kind of patient will have performance issues, load slowly or will not show the images anymore. Good news: you'll get the credits for it too!Īnother typical disease that TNWIki articles suffer from are embedded images with links to 3rd party platforms. Tip: write an technical article fit for TNWiki so that the community can contribute and improve your article.
Idem for personal signatures in an article. So, personal stories ("Hello everybody, I'am. TNWiki is a community, and one of the basic rules if you publish to TNWiki: you are the initial publisher, you get the credits. One of the major advantages of TNWiki is also a major disadvantage, it's open to anyone. You'll notice that the articles greatly benefit from using COLORĪdditional advices, minimize the color variations to a strict minimum. Medic Ninja Richard Mueller has dissected the issue here:
#ENTER THE NINJA CLEAN VERSION OFFLINE#
Some of the offline editors have the nasty habit to dump FAULTY, redundant, overloaded HTML. This also applies to copy/paste from any dummy HTML editor (you know some of these nice editors to create OFFLINE documents ARE NOT fit to write HTML online documentation). USE SIMPLE HEADERS to put sections in your Wiki Article.ĭO NOT replace headers with any variation of font-sizes, for the simple reason that you won't be able to use the, at all. SIMPLE FIX: replace ALL tags with a reversed paragraph tag:Ī very simple advice: do NOT use any special fonts, font sizes, special spacing, font-heights, line-height. Some edits will simply duplicate the tag, resulting in a pretty messed-up article when you hit the Edit button. One of the current issues with the TNWiki (no actually it's TNWiki vs some browsers) is the HTML tag. Resist to the urge to make it fancy and complex. Simple layout, basic default fonts, easy structure. (slow load times, broken links, slow save times, TNWiki engine issues.)
What I mean is: the more complex, redundant, overloaded HTML you got, the worse the performance of your article.
#ENTER THE NINJA CLEAN VERSION CODE#
There is a very simple rule of thumb: if your HMTL code is as simple as the layout of your article, you're good! The good news: in a few weeks Wiki is migrated to a next generation platform, count down has started.ĭid you ever check tha HTML content of your article, did ya? That's exactly what I'm going to cover in this article. So keep out of the way of these known issues, it will make you're life easier. In some case, you can't change it, in some other cases you can use alternatives. Some of the scripts can harm the system, so there's an obvious reason to strip certain code.Īnd as we know the TechNet Wiki has some caveats. You'll notice that the engine strips certain parts of your article or unsupported HTML code. Most famous check is advanced layout, complex CSS features and scripts. When you publish articles, the content is being evaluated against some common threats and unsupported features. So put on your rubber gloves, get everybody out of the room, because we're going down to the dissection of the ideal Wiki article, including the bloody details. In this article we'll deep dive into some Wiki internals to explain how you can get the results you like to have.Īnd more important to KEEP it the way you LIKE IT, avoiding future edits to ruin your patient. On the TechNet Wiki and on this blog you'll find plenty of hints and tips with guidance to publish. When you're publishing articles to TechNet Wiki, you'll see some cases where the content you want to publish doesn't seem to display the way you like. First published on TECHNET on Jul 15, 2015
0 kommentar(er)
