Skip to content

Supported code

If you wrote your own code, or copied and pasted code from another source, and it disappeared after publishing your page then it is most likely being removed by our content management system (CMS).

HTML markup

The Webpartner CMS is a WYSIWYM type (What You See Is What You Mean) rather than a WYSIWYG type (What You See Is What You Get) and emphasises the correct use of HTML markup - so a header is marked as a header rather than being paragraph text that is increased in size, and so on. Using valid and semantic HTML markup is helpful for both website users and search engine robots.

The CMS is designed to support a subset of HTML to ensure that your web pages retain the professional and consistent 'house style' that we create when we first build your website. Code that could cause changes to the website look and feel is automatically removed before pages are published.

We therefore recommend that website editors limit the HTML code entered to the basics:

p, h2, h3, table (and its various sub tags), ol, ul, li

Please contact us for help and advice about things like forms, videos etc.

Image sizes

If you try to use the width and height attributes of the img tag to resize an image this will be removed by our CMS. Please see our related article: Image resizing is worth the effort.

JavaScript and Flash embeds

Website editors are not permitted to add JavaScript to pages within the CMS. It could interfere with the scripts we use for your website and CMS. Third-party JavaScript can also be used for malicious purposes, which has resulted in various high-profile websites being taken offline in the past.

If you are looking to add any "widget" to your site that requires JavaScript, please contact us for help and advice. That way we can vet (no pun intended!) what you are planning to put on the site and ensure that nothing harmful is added to your site.

The same applies to Flash embeds. Your intentions may be innocent, but third parties might try to use such embeds to damage your site.

Opening links in new browser windows

If you try to use target="_blank" to force a link to open in a new browser window this will be removed by our CMS.

The theory goes that forcing a link to open in a new browser window will keep users on the original site, but there are two problems with this thinking:

  1. The tactic hijacks the user's machine and overrides standard browser behaviour, which is not user friendly.
  2. Doing this disables the Back button, which is the normal way users return to previous sites/pages.

Users don't always realise that a new window has opened, especially if they are using smaller screens where the windows are maximized to fill up the screen. So a user who tries to return to the original site will be confused by a grayed out Back button.

Links that don't behave as expected serve to undermine users' understanding of their own system. In most cases a link should be a simple hypertext reference that replaces the current page with new content. This gives users the choice of whether or not to open the link in a new window, which they can do via the command in their web browser (so long as the link is not a piece of code that interferes with standard browser behaviour).