Website templates

Website templates control the presentation of a Portal's public website. The website content belongs to the Portal, while template ownership belongs to the Organization.

Ownership and Portal access

An Organization owns a template once it has been claimed or a paid license has been activated for that Organization. Every current and future Portal in the Organization can use it at the same time. Assigning a template to one Portal does not consume the license, and switching templates, deleting a Portal, or changing the plan's Portal allowance does not remove ownership.

The initial official templates are:

Official template pricing is product data in Forgeport Shop and is shown in EUR.

Paid purchase and activation

A paid checkout creates an unactivated license, an activation code, and access to the available downloads. Checkout does not assign the license to an Organization.

1. Purchase the template in Forgeport Shop.
2. Choose Activate in Forgeport, or copy the activation code for manual redemption.
3. In Organization → Website Templates, select the intended Organization if Forgeport cannot determine it securely.
4. Review the activation warning and choose Activate Template.

Activation permanently assigns the license to that Organization and is the normal refund cutoff. Activated licenses cannot be transferred. Mandatory rights under applicable law remain unaffected. Organization Owners and Organization Admins can activate templates; the user's existing Portal permissions still determine who may configure and publish a Portal website.

Claiming Aurelian

Choose Activate for free under Organization → Website Templates. Forgeport creates the free Shop claim using the authenticated account and assigns it to the selected Organization without a payment checkout. New Organizations do not own Aurelian until this intentional claim. Organizations created before the template-ownership migration receive Aurelian automatically so their existing websites continue without interruption.

Choosing and publishing a template

Open Admin portal → Website for a Portal. Only templates owned by its Organization can be selected. A template change follows the existing workflow:

1. Choose an owned template and hosted version in the draft.
2. Configure its template-specific appearance.
3. Preview it with the Portal's actual website content.
4. Publish when it is ready.

Selecting a template does not change the live website. Shared content — including news, server information, rates, features, rankings, downloads, social links, SEO, branding, gallery, and supported live game data — remains with the Portal. Template-specific settings remain stored when switching away, so an Aurelian → Arcane → Aurelian sequence restores the previous configuration for each template.

The first time a template is selected for a Portal, Forgeport initializes that template from its own shipped appearance defaults. It does not copy the theme, hero artwork, or other presentation settings from the previously selected template. After an administrator changes those settings, Forgeport stores them for that Portal + Template and restores them whenever the Portal returns to the template. This initialization rule applies to every official template, not only Aurelian and Arcane.

Versions and updates

Template updates are included. A new hosted version is never applied automatically: the published website stays pinned until an administrator deliberately selects the new version, previews it, and publishes the draft. Owners retain protected access to updated Static and Forgeport-Integrated downloads in Forgeport Shop.

Deployment modes

Every current official template license includes:

• Forgeport Hosted — rendered by Forgeport's trusted hosted-template runtime.
• Static Self-Hosted — a content snapshot deployed on infrastructure you control.
• Forgeport-Integrated Self-Hosted — self-hosted presentation that reads published content and supported live data from Forgeport.

Shop downloads are generic purchased artifacts. Forgeport's Website export can additionally produce a Portal-aware package using that Portal's owned template and content. Downloads and exports are authorization-protected. A static deployment does not depend on Shop or Forgeport availability; normal Forgeport-hosted page rendering never depends on a live Shop request.