Skip to content

Feature/#169 html performance

Michelle Weidling requested to merge feature/#169-HTML-performance into develop



This MR provides a solution for making the display of HTML pages more performant.

Instead of creating the relevant HTML files on the fly they are now stored in one file per manuscript page and text type. This file is stored in /db/data/textgrid/html and updated by a database trigger each time the respective file gets updated.

Compliance to “Definition of Done”

  • Unit tests passed
  • Code reviewed
  • Product Owner accepts the User Story


  • I updated the README (if applicable)
  • I provided my functions with appropriate documentation
  • I updated existing documentation


Are we able to test this new feature?

  • Yes, everything can be done via unit tests.
  • Yes, you can test by following these steps:
  1. build the database locally
  2. publish the Arabic and Karshuni collection to your local database
  3. after having published them each page of each TEI document has a *.html serialization in /db/data/textgrid/html.


  • I added a statement to the CHANGELOG.

Version number

  • I bumped the version number in


Closes #169 (closed) .

/cc Mathias Göbel, Frank Schneider, Michelle Weidling

Merge request reports