Skip to content

Commit a16303d

Browse files
authored
Create README.md
1 parent f10a529 commit a16303d

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Hasidic Stories Browser
2+
This is the code for the Blazor WASM client that allows close and distant reading in a TEI-XML repository hosted on an eXist-db server.
3+
## eXist-db Dependencies
4+
The client makes use of custom endpoints developped on the eXist-db that aggregate information and send it out as an XML field in a JSON stream. Examples include ``api/get-storyinfo`` called in ``Index.razor.cs``.
5+
## TEI-Publisher Dependencies
6+
The client integrates TEI-Publisher HTML5 components to display text fragments that has been processed by an ODD. The secret sauce comes from including the following lines in ``index.html``:
7+
```
8+
<script src="https://unpkg.com/@webcomponents/[email protected]/webcomponents-loader.js"></script>
9+
<script type="module" src="https://unpkg.com/@teipublisher/pb-components@latest/dist/pb-components-bundle.js"></script>
10+
```
11+
This allows building a pgae, very similar to a TEI-Publisher template, where a ``<pb-page`` contains ``<pb-document>``, ``<pb-view>`` etc. - see ``Edition.razor``. Another neat possibility is the Blazor component model, so a component such as ``StoryTEI.razor`` which includes a TEI-Publisher template in a ``<pb-document>`` HTML5 component, can be included in other components or pages.

0 commit comments

Comments
 (0)