metafacture · fsteeg · May 23, 2024 · Mar 27, 2024 · Mar 27, 2024 · Mar 28, 2024
diff --git a/Gemfile b/Gemfile
@@ -0,0 +1,7 @@
+source 'https://rubygems.org'
+
+gem "jekyll", "~> 4.3.3" # installed by `gem jekyll`
+# gem "webrick"        # required when using Ruby >= 3 and Jekyll <= 4.2.2
+
+gem "just-the-docs", "0.8.1" # pinned to the current release
+# gem "just-the-docs"        # always download the latest release
diff --git a/README.md b/README.md
@@ -2,71 +2,16 @@
 
 # Metafacture Documentation
 
-Metafacture is a toolkit for processing semi-structured data with a focus on library metadata. It provides a versatile set of tools for reading, writing and transforming data. Metafacture can be used as a stand-alone application via CLI or as a Java library in other applications. There is also a playground where you can test workflows.
+Metafacture is a toolkit for processing semi-structured data with a focus on library metadata
+For the documentation see: http://metafacture.github.io/metafacture-documentation/
 
-[Have a look here for a quick intro into metafacture.](./MF-in-5-min.md)
+This repo is the central place for the documentation about Metafacture that we render using the jekyll template [Just the docs](https://github.com/just-the-docs/just-the-docs).
 
-This is the central place for the documentation about Metafacture.
-
-Metafacture comprises three main parts: **Framework**, **Flux** and one of the **Transformation-Modules Fix and Morph**. It can be extended with modules.
+The content pages can be found [here](/docs/)
 
 > [!NOTE]
 > With regard to the Transformation-Modules this documentation focusses on Fix instead of MORPH. If you want to find out more about MORPH. Have a look at [the old documentation](https://github.com/metafacture/metafacture-core/wiki/Metamorph-User-Guide) and the german cookbook by [Swissbib](https://swissbib.gitlab.io/metamorph-doku/).
 
 
-Our goal with this repo is to collaboratively create comprehensive documentation on Metafacture in the [issue tracker](https://github.com/culturegraph/metafacture-documentation/issues?q=). Feel free to open issues not only for bugs or enhancements, but also questions about Metafacture usage, or to share your experiences. We hope that over time, in that way we can create useful tutorials, how-tos, and collect good practices for using Metafacture.
-
-__________________
-
-Deciding which parts are relevant to you depends on the way you are using Metafacture:
-
-## Using Metafacture via playground or CLI
-
-> [!NOTE]
-> No Java-Code is necessary!!!
-
-While working with the playground or the command line you only need [Flux](#flux) and the transformation module [Fix](#fix).
-Have a look here for [Getting started](/Getting-Started.md).
-
-## Framework for Java integration/development
-
-If you plan to use Metafacture as a Java library or if you wish to add commands to Flux. You should get familar with the [Framework](#framework).
-
-__________________
-
-## FLUX
-
-Flux is a scripting language to easily build and run processing pipelines. No Java programming is necessary - it's used as a command line. To use Flux you may download the binary distribution of Metafacture.
-
-For more information on how to use Flux, see the [Flux User Guide](/Flux-User-Guide.md).
-
-See [here a list for all available FLUX-Commands](/flux-commands.md).
-
-__________________
-
-## FIX
-
-Metafix is a domain specific language for metadata transformation based on Catmandu FIX. The FIX object performing the transformation is used as part of a processing pipeline.
-
-If you are using **Metafacture with CLI or Playground** and therefore the Flux scripting language to build and run pipelines, use the `fix` command in your FLUX-Pipeline. 
-
-If you are using **Metafacture as a Java library**, just create a Metafix object and add it to your pipeline (see also the [Framework User Guide](#framework)).
-
-The transformation itself is declared in a fix-object which can be a file. For more information on how to declare transformations see [Metafix User Guide](/Fix-User-Guide.md).
-
-See [here a list for all available FIX functions and a cookbook for using fix](/Fix-function-and-Cookbook.md).
-
-> [!NOTE]
-> PS: There is also the transformation modul MORPH. Have a look at[ the old documentation](https://github.com/metafacture/metafacture-core/wiki/Metamorph-User-Guide) and the german cookbook by [Swissbib](https://swissbib.gitlab.io/metamorph-doku/).
-
-__________________
-
-## Framework
-
-> [!NOTE]
->Relevant for developers
-
-The framework includes the interfaces and abstract classes which form the foundation of the data processing pipelines. This part of Metafacture is only relevant for you if you plan to use Metafacture as a Java library or if you wish to add pipe elements to Flux.
-
-For more information see the [Framework User Guide](/Framework-User-Guide.md).
+Our goal with this repo is to collaboratively create comprehensive documentation on Metafacture in the [issue tracker](https://github.com/metafacture/metafacture-documentation/issues?q=). Feel free to open issues not only for bugs or enhancements, but also questions about Metafacture usage, or to share your experiences. We hope that over time, in that way we can create useful tutorials, how-tos, and collect good practices for using Metafacture.
 
diff --git a/_config.yml b/_config.yml
@@ -0,0 +1,51 @@
+title: Metafacture Documentation
+description: This is the central place for the documentation about Metafacture.
+theme: just-the-docs
+
+url: https://metafacture.github.io/metafacture-documentation
+
+aux_links:
+  Metafacture Documentation on Github: https://github.com/metafacture/metafacture-documentation
+
+# Set a path/url to a logo that will be displayed instead of the title
+logo: "/assets/images/metafacture_small.png"
+favicon_ico: "/assets/images/favicon.ico"
+
+# Footer content
+# appears at the bottom of every page's main content
+
+# Back to top link
+back_to_top: true
+back_to_top_text: "Back to top"
+
+footer_content: "Metafacture Documentation is maintained by the <a href=\"https://lobid.org/team-en/\">Open infrastructure team of hbz.</a>"
+
+# Footer last edited timestamp
+last_edit_timestamp: true # show or hide edit time - page must have `last_modified_date` defined in the frontmatter
+last_edit_time_format: "%b %e %Y at %I:%M %p" # uses ruby's time format: https://ruby-doc.org/stdlib-2.7.0/libdoc/time/rdoc/Time.html
+
+# Custom colors, see _sass/color_schemes/metafacture.scss
+color_scheme: metafacture
+
+# see https://just-the-docs.github.io/just-the-docs/docs/search/#search-granularity
+search:
+  heading_level: 6
+  previews: 6
+
+# Callouts, see https://just-the-docs.com/docs/configuration/#callouts
+callouts_level: quiet # or loud
+callouts:
+  highlight:
+    color: yellow
+  important:
+    title: Important
+    color: blue
+  new:
+    title: New
+    color: green
+  note:
+    title: Note
+    color: purple
+  warning:
+    title: Warning
+    color: red  
diff --git a/_sass/color_schemes/metafacture.scss b/_sass/color_schemes/metafacture.scss
@@ -0,0 +1 @@
+$link-color: #4183c4;
diff --git a/_sass/custom/custom.scss b/_sass/custom/custom.scss
@@ -0,0 +1,4 @@
+h4 {font-size: 1rem !important;}
+h5 {
+    font-size: 1.5rem !important;
+}
diff --git a/assets/images/favicon.ico b/assets/images/favicon.ico
diff --git a/assets/images/metafacture_small.png b/assets/images/metafacture_small.png
diff --git a/...hing a transformation with metafacture.md → ...hing a transformation with metafacture.md b/...hing a transformation with metafacture.md → ...hing a transformation with metafacture.md
@@ -1,3 +1,9 @@
+---
+layout: default
+title: Approaching a transformation with metafacture
+nav_order: 4
+---
+
 Every approach to transform metadata with metafacture is quite similiar:
 
 - You need to know the type and source of the input and the type and destination of the output:

diff --git a/Documentation-Maintainer-Guide.md → docs/Documentation-Maintainer-Guide.md b/Documentation-Maintainer-Guide.md → docs/Documentation-Maintainer-Guide.md
@@ -1,7 +1,14 @@
+---
+layout: default
+title: Maintainer Guide
+nav_order: 8
+---
 
-## how to change flux-commands.md
+# Maintainer Guide
 
-The entries in flux-commands.md describe the usage of commands used by flux.
+## how to change [docs/flux/flux-commands.md](https://github.com/metafacture/metafacture-documentation/blob/28-use-jekyll-theme/docs/flux/flux-commands.md)
+
+The entries in [docs/flux/flux-commands.md](https://github.com/metafacture/metafacture-documentation/blob/28-use-jekyll-theme/docs/flux/flux-commands.md) describe the usage of commands used by flux.
 flux-commands.md is fully automatically generated. To make this happen one has to
 fill in the proper annotations in the correponding java classes. E.g.
 
@@ -30,7 +37,7 @@ The option's name is produced by cutting away the "set" from the methods name, l
 "BatchSize" which is then lowercased. The parameter of this option is generated from the
 parameter type of the method - here an "int"eger.
 
-## how to publish flux-commands.md
+## how to publish [docs/flux/flux-commands.md](https://github.com/metafacture/metafacture-documentation/blob/28-use-jekyll-theme/docs/flux/flux-commands.md)
 
 If you have updated some of these annotations, say "description", and these changes are
 merged into the master branch, generate a new flux-commands.md like this:
@@ -43,6 +50,7 @@ $ flux.sh > flux-commands.md
 ```
 
 Open the generated flux-commands.md and remove some boilerplate at the beginning of the
-file manually. Save it, copy it here, commit and push.
+file manually. Add the naviagtion part of the page, save it, copy it [here](https://github.com/metafacture/metafacture-documentation/blob/28-use-jekyll-theme/docs/flux/flux-commands.md), commit and push.
+
 
 The [publishing process will be automated with an github action](https://github.com/metafacture/metafacture-core/issues/368).
diff --git a/Getting-Started.md → docs/Getting-Started.md b/Getting-Started.md → docs/Getting-Started.md
@@ -1,17 +1,20 @@
-![logo](https://github.com/culturegraph/metafacture-core/wiki/img/metafacture_small.png)
-
+---
+layout: default
+title: Getting Started
+nav_order: 2
+---
 
 # Getting started!
 
 ## Playground
 
 The easiest way to get started with Metafacture is the Playground. Take a look at the [first example](https://metafacture.org/playground/?example=encode-xml) and run it by pressing the !["Process"](https://metafacture.org/img/process.png) button. Check out the other examples (first button, !["Load Examples"](https://metafacture.org/img/load-exmples.png)) for different input sources, transformations, and output formats.
 
-For commands available in the Flux, see [the Flux commands documentation](/flux-commands.md).
+For commands available in the Flux, see [the Flux commands documentation](/docs/flux/flux-commands.html).
 
-For functions and usage of the Fix, see [the Fix functions and cookbook](/Fix-functions-and-cookbook).
+For functions and usage of the Fix, see [the Fix functions and cookbook](/docs/fix/Fix-functions-and-cookbook.html).
 
-For next steps get familar with [FLUX](/Flux-User-Guide.md) and [FIX](/Fix-User-Guide.md). And try out some Metafacture workflows.
+For next steps get familar with [FLUX](/docs/flux/Flux-User-Guide.html) and [FIX](/docs/fix/Fix-User-Guide.html). And try out some Metafacture workflows.
 
 ## Command line
 
@@ -24,7 +27,7 @@ To get started, you can export a workflow from the Playground (last button, !["E
 
 To set up IDE support for editing your Flux and Fix files, see [the IDE extensions page](https://metafacture.org/ide-extensions/index.html).
 
-For next steps get familar with [FLUX](/Flux-User-Guide.md) and [FIX](/Fix-User-Guide.md). And try out some Metafacture workflows.
+For next steps get familar with [FLUX](/docs/flux/Flux-User-Guide.html) and [FIX](/docs/fix/Fix-User-Guide.html). And try out some Metafacture workflows.
 
 ## Using Metafacture as a Java library
 
@@ -55,4 +58,4 @@ To use Fix you would declare `metafix` instead of `metafacture-io` as in the exa
 Occasionally, we publish snapshot builds on [Sonatype OSS Repository](https://oss.sonatype.org/index.html#nexus-search;gav~org.metafacture~~~~~kw,versionexpand). The version number is derived from the branch name. Snapshot builds from the master branch always have the version `master-SNAPSHOT`. We also provide sometimes pre releases as github packages.
 
 
-If you plan to use Metafacture as a Java library or if you wish to add commands to Flux you should get familar with the [Framework](/Framework-User-Guide.md).
+If you plan to use Metafacture as a Java library or if you wish to add commands to Flux you should get familar with the [Framework](/docs/java-integration/Framework-User-Guide.html).
diff --git a/LICENSE → docs/LICENSE b/LICENSE → docs/LICENSE
diff --git a/docs/LICENSE.md b/docs/LICENSE.md
@@ -0,0 +1,27 @@
+---
+layout: default
+title: LICENSE
+nav_order: 9
+---
+
+MIT License
+
+Copyright (c) 2022 just-the-docs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/MF-in-5-min.md → docs/MF-in-5-min.md b/MF-in-5-min.md → docs/MF-in-5-min.md
@@ -1,3 +1,9 @@
+---
+layout: default
+title: 5 min Intro into MF
+nav_order: 3
+---
+
 # Introduction - A quick 5 minute introduction to Metafacture
 
 ## HELLO WORLD
@@ -87,7 +93,7 @@ $ cat yaml2json.flux
 
 ## FIX LANGUAGE
 
-Many data conversions need a mapping from one field to another field plus optional conversions of the data inside these fields. Metafacture provides the transformation module `fix` that uses the Catmandu-inspired Fix language to assist in these mappings. A full list Fix functions is available at https://github.com/metafacture/metafacture-documentation/blob/master/Fix-function-and-Cookbook.md#functions.
+Many data conversions need a mapping from one field to another field plus optional conversions of the data inside these fields. Metafacture provides the transformation module `fix` that uses the Catmandu-inspired Fix language to assist in these mappings. See the [full list of Fix functions](/docs/fix/Fix-functions-and-Cookbook.html#functions).
 
 Fixes can be provided inline as text argument of the fix module in the Flux script, or as a pointer to a Fix script. A Fix script groups one or more fixes in a file.
 
@@ -173,6 +179,6 @@ The 245 field with its subfields of each MARC record is mapped to the title fiel
 The `retain` Fix function keeps only the title field in the output. (In contrast to Catmandu there are no special marc or pica fixes since the internal handling of records and elements is more generic. Also the internal serialization of MARC is not as complex as in Catmandu.)
 
 
-Now you should be ready to [get started](./Getting-Started.md).
+Now you should be ready to [get started](/docs/Getting-Started.html).
 
 (Note: This mini introduction to Metafacture is inspired by the mini introduction to Catmandu here: https://metacpan.org/dist/Catmandu/view/lib/Catmandu/Introduction.pod)
diff --git a/Fix-User-Guide.md → docs/fix/Fix-User-Guide.md b/Fix-User-Guide.md → docs/fix/Fix-User-Guide.md
@@ -1,11 +1,16 @@
-![logo](https://github.com/culturegraph/metafacture-core/wiki/img/metafacture_small.png)
+---
+layout: default
+title: Fix User Guide
+parent: Fix
+nav_order: 1
+---
 
 # Fix User Guide
 
 This document provides an introduction to the Metafacture Fix language (short: Metafix or Fix). The Fix language for Metafacture is introduced as an alternative to configuring data transformations with Metamorph. Inspired by Catmandu Fix, Metafix processes metadata not as a continuous data stream but as discrete records.
 
 ## Part of a metafacture worflow
-Metafacture Fix is a transformation module that can be used in a [Flux Workflow](/Flux-User-Guide.md), for this you have to use this in your pipeline:
+Metafacture Fix is a transformation module that can be used in a [Flux Workflow](/docs/flux/Flux-User-Guide.html), for this you have to use this in your pipeline:
 
 Flux-Example:
 ```PERL
@@ -85,7 +90,7 @@ do Bind(params,…)
 end
 ```
 
-Find here a [list of all functions, selectors, binds and conditionals](/Fix-function-and-Cookbook.md).
+Find here a [list of all functions, selectors, binds and conditionals](//docs/fix/s-and-Cookbook.html).
 
 
 ## Addressing Pieces of Data: FIX-Path and the record structure in FIX

diff --git a/Fix-function-and-Cookbook.md → docs/fix/Fix-functions-and-Cookbook.md b/Fix-function-and-Cookbook.md → docs/fix/Fix-functions-and-Cookbook.md
@@ -1,4 +1,11 @@
-This page is a replication of the passage of the Fix Readme.md. Status: [Fix Release 1.0.0](https://github.com/metafacture/metafacture-fix/releases/tag/1.0.0)
+---
+layout: default
+title: Fix Functions and Cookbook
+parent: Fix
+nav_order: 2
+---
+
+This page is a replication of the passage [Fix Functions and Cookbook](https://github.com/metafacture/metafacture-fix?tab=readme-ov-file#functions-and-cookbook) of the Fix Readme.md. Status: [Fix Release 1.0.0](https://github.com/metafacture/metafacture-fix/releases/tag/1.0.0)
 
 ## Functions and cookbook
 
@@ -935,7 +942,3 @@ Executes the functions if/unless the field value does not match the regular expr
 ##### `str_match`
 
 Executes the functions if/unless the string matches the regular expression pattern.
-
-## Xtext
-
-This repo has been originally set up with [Xtext](https://www.eclipse.org/Xtext/) 2.17.0 and Eclipse for Java 2019-03, following [https://www.eclipse.org/Xtext/documentation/104_jvmdomainmodel.html](https://www.eclipse.org/Xtext/documentation/104_jvmdomainmodel.html).
diff --git a/docs/fix/fix.md b/docs/fix/fix.md
@@ -0,0 +1,19 @@
+---
+layout: default
+title: Fix
+nav_order: 6
+has_children: true
+---
+
+Metafix is a domain specific language for metadata transformation based on Catmandu FIX. The FIX object performing the transformation is used as part of a processing pipeline.
+
+If you are using **Metafacture with CLI or Playground** and therefore the Flux scripting language to build and run pipelines, use the `fix` command in your FLUX-Pipeline. 
+
+If you are using **Metafacture as a Java library**, just create a Metafix object and add it to your pipeline (see also the [Framework User Guide](#framework)).
+
+The transformation itself is declared in a fix-object which can be a file. For more information on how to declare transformations see [Metafix User Guide](/Fix-User-Guide.md).
+
+See [here a list for all available FIX functions and a cookbook for using fix](//docs/fix/Fix-functions-and-Cookbook.html).
+
+{: .note }
+PS: There is also the transformation modul MORPH. Have a look at[ the old documentation](https://github.com/metafacture/metafacture-core/wiki/Metamorph-User-Guide) and the german cookbook by [Swissbib](https://swissbib.gitlab.io/metamorph-doku/).