This is the documentation page for the Portal pages and its components.

The portal and front pages are constructed out of multiple components. Each of these components can be edited individually and is auto-magically rendered with the right background.

Portal v2.0

The Portal system has undergone significant changes especially to the front-end CSS. This update is a huge jump forward in end-user interaction.

This Portal v2.0 primarily consists of a update to the UI which is inspired by Microsoft's Metro design. As such, most components have been updated to feature a background. The glossy semi-transparent Aqua-inspired look of Portal v1.0 has been reduced to a simple opaque and rectangular look. Each component now includes a background to give the components a specific look and feel. The #Slider component has the previous and next button removed. Instead each slide now has a back button that returns the user to the #Main slide. This represents a shift from a gallery styled slider system to a tree structured one.

The #Transformer template has not been changed. The #Transformer template already supports the style attribute and Portal v2.0 leverages this by using the "metro" style tag.

The scripts has been extended to support the vertical tabs used by the #Slider component. There are no other changes.

The component naming convention has been updated from Template:Portal/Component/<Name> to Portal:Component/<Name>

Portal v2.0 is a web based UI and does not support mobile devices in its current iteration.


The creation of containers and elements of the portal box is handled by {{PortalSection}}. It's design adds the necessary class so that the css can apply the correct style to the elements. You can move the elements about, but keep in mind that it might not look good unless you can also edit the common stylesheet, the wikia and the monobook specific stylesheet.


{{PortalTransformer}} is the transformer that takes the layout and converts it into {{PortalSection}} much like our {{ItemTransformer}} does. It can also transform a portal section into a frameless section called a {{PortalPage}}.

As of v2.0, it now also supports {{PortalMetro}} which is the Metro look and feel.


The following is a list of the components which can be used to make up a page. Simply transclude them into a page like so {{Portal:Component/News}}.

Portal Components

A portal is a unique type of component in that it is designed to fit within a certain width and height. It needs its fixed width as it is designed to be a tab in #Slider or as a standalone in the fallback #Portal Pages.

Portal Pages

Portal pages are actual portals - if javascript fails and as a fallback position, Portal:Component/Main will link to each of these portal pages without sliding. Therefore, even though these pages are seldom used, they must be created in the event the user does not have javascript enabled, or if javascript fails to load. The previous feature has been depreciated in Portal v2.0. It is still possible to create non-javascript portals for users that do not have javascript enabled but it is no longer within the scope of this help file.

These portal pages transclude #Layout and passes #Portal Components as a parameter. This basically tells wiki to use the layout but instead of using #Slider, use a static Portal Component instead.

The following is a list of Portal Pages


There is only one current layout for the page and it is Dragon Age Wiki - this wiki's main page. Its layout uses a unique component called the Portal:Component/Slider unless it is transcluded and passed an anonymous {{{1}}} parameter. This page is only transcluded by #Portal Pages.


There is one unique component called Portal:Component/Slider which is a component that consists of the other portal components. Its primary purpose is create a page with multiple pages of portal. Only Portal:Component/Main is shown and the rest is hidden. If javascript is enabled, then the user can slide through these pages. If javascript is not enabled, then clicking on links in the main page will take you to the #Portal Pages.

In order to add new pages, you must do two things

  • Add the following code to the top of the page. X must be a number in the sequence.
  • Add the following code to the middle part of the page. A content can be anything but should be a #Portal Components
<div id="portal_content-4" class="ui-tabs-hide">CONTENT HERE</div>


There are two versions of Portal:Component/Twitter.

The first version does not require any javascript, but it is unreliable. It uses the rss markup in Wikia which often fails to load.

The revamped Portal:Component/Twitter calls MediaWiki:TwitterWidget. This in turn uses Twitter's Widget API to asynchronously update the feed. It is far more reliable. Use this version.

When creating this component using the second method, you will need to copy and edit MediaWiki:TwitterWidget.

Main Portal

The main portal is the first thing the reader sees when they enter the wiki as it is the first page of the #Slider. It should contain normal links to pages or portals.

In addition, if the link is to a #Portal Components, it should also contain

<div class="portal_sliderlink_X">CONTENT HERE</div>

If javascript is enabled, this will cause the code to slide to the page X instead of opening the portal. If javascript is not, then as a fallback, the user will be taken to that link location.

Random Pages

This page is here to distract you and cause confusion.


A few other wikis have adopted the use of Portal and the sliders. They are listed here.


Previous version of the Sliders available at


This is a change log. If you adopted the portal system prior to these dates, you will need to update your components accordingly.

v2.0 - 19th October 2014

  • A complete list of changes is available at #Portal v2.0
  • Significant changes to the CSS and UI
  • Minor changes to the javascript to support vertical tabs
  • No changes to the templates
  • Changed naming convention from Template:Portal/Component/<Name> to Portal:Component/<Name>
  • Update Portal:Component/Images style to override gallery and allow the image to use the complete component

v1.5 - 20th July 2013

v1.4 - 3rd October 2012

v1.3 - 11th September 2011

v1.2.1 - 3rd September 2011

  • Updated documentation with #Twitter. No component changed.

v1.2 - 16th August 2011

v1.1 - 2nd June 2011

v1.0 - 7th November 2010

  • Release
Community content is available under CC-BY-SA unless otherwise noted.