Skip to content

Commit a841cb2

Browse files
author
Jakob Jünger
committed
Update asset paths
1 parent 3d68ae0 commit a841cb2

File tree

15 files changed

+30
-30
lines changed

15 files changed

+30
-30
lines changed

docs/devel/backend/controller.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ User settings in Epigraf are either stored in the user record or in the session.
180180
All controllers extend the `AppController` class (`src/Controller/AppController.php`)
181181
which is derived from the base `Controller` class provided by the CakePHP framework.
182182

183-
![Application controller class hierarchy](/devel/assets/img/classes-controller-app.png)
183+
![Application controller class hierarchy](../assets/img/classes-controller-app.png)
184184

185185
On the application level, controllers serve the following purposes:
186186

@@ -199,7 +199,7 @@ The Epi plugin implements an own `Epi\AppController` class (`plugins/Epi/Control
199199
derived from the global AppController, adding functionality for project database handling.
200200
All project database controllers within the Epi plugin extend this class.
201201

202-
![Epi plugin controller class hierarchy](/devel/assets/img/classes-controller-epi.png)
202+
![Epi plugin controller class hierarchy](../assets/img/classes-controller-epi.png)
203203

204204
They Epi plugin controllers serve the following purposes:
205205

docs/devel/backend/model.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ All Tables are derived from `src/Model/Table/BaseTable.php` and all Entities fro
3030
Common methods in the table classes are `findHasParams()` and `findContainFields()`
3131
which are used by the controllers to filter and retrieve data from the database based on query parameters.
3232

33-
![Model class hierarchy (App)](/devel/assets/img/classes-model-app.png)
33+
![Model class hierarchy (App)](../assets/img/classes-model-app.png)
3434

3535
There are some pecularities in the models. You may need to read the section about project database models
3636
to understand the full picture:
@@ -64,7 +64,7 @@ Tables classes are usually derived from `plugins/Epi/src/Model/Table/BaseTable.p
6464
and entity classes from `plugins/Epi/src/Model/Entity/BaseEntity.php`.
6565
Both project database level base classes extend the corresponding application's base classes.
6666

67-
![Model class hierarchy (Epi)](/devel/assets/img/classes-model-epi.png)
67+
![Model class hierarchy (Epi)](../assets/img/classes-model-epi.png)
6868

6969
Some special cases have to be considered:
7070

docs/devel/backend/view.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ different view classes are used.
1313
The ApiView based classes are also used in the export pipelines
1414
to generate TEI-documents and other structured data formats.
1515

16-
![View class hierarchy](/devel/assets/img/classes-view.png)
16+
![View class hierarchy](../assets/img/classes-view.png)
1717

1818

1919
## Rendering HTML for the Browser

docs/devel/frontend/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,4 @@ For interactive trees, tables and other widgets, Epigraf implements an own EpiWi
1313
Bundling JavaScript files, CSS files, language resources and images is done using Webpack.
1414
All bundles can be generated at once by calling `npm run build`.
1515

16-
![Epigraf Editor](/devel/assets/img/epigraf-editor.png)
16+
![Epigraf Editor](../assets/img/epigraf-editor.png)

docs/devel/frontend/widgets.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The base classes of the framework are defined in `htdocs/js/base.js`:
3131
A document consists of several parts such as sections, footnotes and notes.
3232
Document classes hold together the different parts and manage the interaction between them.
3333

34-
![Inheritance hierarchy](/devel/assets/img/classes-widget-basemodel.png)
34+
![Inheritance hierarchy](../assets/img/classes-widget-basemodel.png)
3535

3636
### The Widget Life Cycle
3737

@@ -127,7 +127,7 @@ Frames are HTML elements attached to derivates of the `BaseFrame` class that han
127127
- `TabFrame`: Responsible for tab sheets within in sidebars.
128128
- `PopupWindow`: Responsible for popups and dialogs.
129129

130-
![Inheritance hierarchy](/devel/assets/img/classes-widget-baseframe.png)
130+
![Inheritance hierarchy](../assets/img/classes-widget-baseframe.png)
131131

132132
The frame classes handle dynamic content loading and trigger the respective widget lifecycle methods:
133133
- `loadElement()` displays a DOM element already constructed on the page.
@@ -215,7 +215,7 @@ Both are descendants of the `BaseForm` class supporting features for saving data
215215
- Handle form validation and the form submission lifecycle.
216216
- Emit events for other widgets reacting to content updates.
217217

218-
![Inheritance hierarchy](/devel/assets/img/classes-widget-basedocumentmodel.png)
218+
![Inheritance hierarchy](../assets/img/classes-widget-basedocumentmodel.png)
219219

220220
The `EntityWidget` is used for simple entities, usually displayed in a vertical table.
221221
It inherits all methods and properties from `BaseForm`

docs/devel/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ MariaDB and the file system is used to store [data](/devel/docs/database). There
6767
user accounts and application-wide data. For the research data, multiple project databases are created.
6868
Frontend and database content is cached using Redis. If no Redis server is available, the cache is stored in the file system.
6969

70-
![Epigraf architecture](/devel/assets/img/epigraf-architecture.png)
70+
![Epigraf architecture](devel/assets/img/epigraf-architecture.png)
7171

7272
## Directory structure
7373

docs/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,17 @@
88
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
99
title:
1010
permalink: /
11+
recent: false
1112
---
1213

1314
Epigraf is a research platform for collecting, annotating, linking and publishing multimodal text data.
1415
The data model supports research databases ranging from epistolary editions to social media corpora.
1516
Epigraf is currently used primarily for editing epigraphic data - inscriptions in connection with the objects to which they are attached.
1617
It includes a publication system for various document formats such as Word or TEI, structured JSON, XML and CSV data, and triples in TTL, JSON-LD and RDF/XML.
1718

19+
![Epigraf use cases](assets/img/epigraf-use-cases.png)
20+
21+
1822
- You want to know how Epigraf looks like and what it is good for?
1923
The [user documentation](/user/) provides an introduction to Epigraf,
2024
its configuration and administration.
@@ -25,10 +29,6 @@ It includes a publication system for various document formats such as Word or TE
2529
The [Source code](https://github.com/digicademy/epigraf) is released on GitHub after major updates.
2630
We are open to collaborative development and appreciate getting in touch with you.
2731

28-
29-
30-
![Epigraf use cases](assets/img/epigraf-use-cases.png)
31-
3232
Epigraf emerged from the inter-academic edition project "The German Inscriptions of the Middle Ages and the Early Modern Period".
3333
It is used in the nine inscription research centers of the six participating academies of sciences.
3434
The application is being developed by the Digital Academy of Sciences and Literature \| Mainz and the Digital Media & Computational Methods Research Group at the University Münster.

docs/user/coreconcepts/model.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The Relational Article Model (RAM) distinguishes between the data model and the
2525
- **Properties** are vocabularies or categories that are used for the structured description of a research object and for annotations.
2626
- **Projects** group several articles together.
2727

28-
![Epigraf Datamodel](/user/assets/img/overview_datamodel.png)
28+
![Epigraf Datamodel](../assets/img/overview_datamodel.png)
2929

3030
# Domain model
3131

docs/user/import/api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The following example transforms three cases from a table into the relational ar
4545

4646
That's how the result looks like:
4747

48-
![Epigraf API](/user/assets/img/import_api.png)
48+
![Epigraf API](../assets/img/import_api.png)
4949

5050

5151
The craft functions either map existing columns or fill in values not

docs/user/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ and triples in TTL, JSON-LD and RDF/XML.
1818

1919
Epigraf's modules support the entire research data lifecycle ([Higgins 2008](https://doi.org/10.2218/ijdc.v3i1.48)):
2020

21-
![Epigraf Modules](/user/assets/img/modules.png)
21+
![Epigraf Modules](user/assets/img/modules.png)
2222

2323
- **Collection**: Data sets can be both edited in the application as well as imported from files. The core concepts of Epigraf are articles and properties used in articles.
2424
- **Annotation**: Every article is composed of sections, that can be flexibly combined, containing text and all relevant metadata (descriptions, comments, categorizations via vocabularies) as well as embedded files or images. A configurable toolbar is available for the annotation of texts.

0 commit comments

Comments
 (0)