A LaTeX class implementing the formatting guidelines on scientific writing of the art history institute (Kunstgeschichtliches Institut) at Ruhr University Bochum.
Specifically at this point the class aims to implement the guidelines of July 2023, available at https://kgi.ruhr-uni-bochum.de/wp-content/uploads/2023/04/Anleitung-zum-Erstellen-von-Hausarbeiten-im-Fach-Kunstgeschichte_Fassung-Juli-2023.pdf at the time of writing.
Just type
\documentclass{rub-kunstgeschichte}to use the class in your LaTeX document.
The full documentation of the latest version can be found on CTAN and of any version on the GitHub release page in the release assets as rub-kunstgeschichte.pdf.
You can also find a simple example called rub-kunstgeschichte-example.tex which you can use as a template for your own project alongside a compiled pdf version rub-kunstgeschichte-example.pdf as part of the release assets.
On release, the latest version of this class is automatically published to CTAN. Therefore it should be included in the latest version of the major Tex distributions a few days after the CTAN release.
If you want to manually install any version of this class, the simplest solution would be to download the rub-kunstgeschichte.cls file from the release assets on the GitHub release page and place it in the same folder as your document.
A more advanced manual installation would be to take the rub-kunstgeschichte.tds.zip, unpack it and place it in the texmf tree to get a full installation including documentation and example files.
Furthermore you can download the rub-kunstgeschichte-ctan.zip and run pdflatex on the .dtx file to produce the documentation, as well as tex or latex on the .ins file to obtain the derived class file from the source files.
This work is maintained by Joran Schneyer [email protected] and released under the LaTeX Project Public License v1.3c or later. See https://www.latex-project.org/lppl.txt or the LICENSE file.
You are very welcome to contribute to this project.
The easiest way to contribute (even without technical knowledge) is to go to the Issues tab of this repo and create a new issue in which you describe a feature you would like to see implemented or a bug or an error in the current implementation.
For more information see CONTRIBUTING.md.