Skip to main content

Graph Modeling Linked Data Frontend Template Guide

31/03/2026

This guide details the file structure of Graph Modeling's Linked Data Frontend templates.

Note

Graph Modeling (PoolParty) 10.1 announces a critical Content Security Policy (CSP) update that disallows unsafe-inline styles and scripts, requiring developers to refactor all inline code, especially within Velocity Templates (.vm files), to external CSS/JS files. Refer to our guide on Content Security Policy Compliance for more information on how to comply as well as how to whitelist certain analytics tools for LDF.

The templates for the Linked Data Frontend reside in the frontendRoot directory that can be found at /var/lib/poolparty/data/frontendRoot for on-premise installations of Graph Modeling; and inside the Docker image for Docker installations. For more information on Docker installations of the platform, refer to LDF Configuration with Docker.

The basic folder and file structure is as follows:

default

Default template delivered with a Graph Modeling installation.

  • conf.vm - common settings. Here, common variables and configuration options are defined.

  • vars.vm - variables used in all templates. Here you can find URI definitions shortcuts.

  • foot.vm - footer of the template used in all page setups

  • head.vm - header of the template used in all page setups

  • makros.vm - set of shared functions that are used in other templates

  • server.vm - html view of the server page

  • lang

    • de.vm - German labels

    • en.vm - English labels

  • js

    • script.js - collection of JavaScript functions. E.g. showIndex formulates a SPARQL query to collect all concepts of a project, starting with the respective character.

  • project

    • html.vm - html view of the project

  • resource

    • html.vm - html view of a resource. Distinction between concepts and concept schemes

    • visual.vm - visual view of a resource (concept, concept scheme)

    • concept.vm - view of a concept

    • conceptscheme.vm - view of a concept scheme

    • map.vm - covering available languages

custom

Templates in the custom directory overwrite templates in the default directory. Different templates can be defined down to the project level.

To have a different template for a project you have to create a directory for the project in the custom directory named like the projectID of the project.

This only works if the projectID does not contain signs that are not allowed while creating Linux folder names.

For example a projectID like 'project/myThesaurus' would not work because of the '/'.

In brief,

  • custom/projectID/server.vm overwrites

  • custom/server.vm

and

  • custom/server.vm overwrites

  • default/server.vm

As you can see from the default structure you can have a template per

In this section: