Information and Links

Introduction Information and Links (IAL) is a set of scripts and an XHTML page template that allows locally downloading API documentation. This documentation and other URLs can then be linked from a single home page.

This can be a more structured approach than having tons of bookmarks or searching documentation online all of the time. Since IAL consists of files external to the web browser, its contents can be synchronized across devices and browsers. It is also possible to host it on a web server in order to locally provide commonly needed API documentation and links.

IAL consists of two main components:

  1. XHTML Template: A page template is provided that can be used as a “homepage” for all the collected documentation. The page consists of multiple search boxes (for Internet and local searches respectively) and “boxes” into which links can be placed. These links can point to local documentation or websites.
  2. Scripts: Scrips are provided for downloading API documentations from the respective vendors as HTML files that can be stored locally. Additionally, the scripts contain code to extract relevant keywords from the downloaded HTML. These keywords are then stored in a JSON file (script.js) along with links to the respective matching pages. Including these script.js files from the IAL home page enables a keyword-based search to search the documentation.

The idea is that these components provide a framework that users can take as an example that can be customized to fit their own uses.


As documentation is often available online, there is less and less need for the functionality provided by Information and Links. A software that also focuses on offlince documentation searching can be found at

Getting Started with the Example Content

If you want to try out what IAL can look and feel like, this section describes a quick way to set it up to “display something”. If you want to take the most out of it, consider reading the remainder of the documentation here to find out what the different parts are supposed to mean.

Additionally, note that all the scripts are unlikely to work on Windows OSes natively. Consider running them in WSL, Docker or a Linux VM if you are using Windows.

  1. Clone the co-artifact repository and the bo-ial repository.
git clone
git clone
cd bo-ial
  1. Download some documentation
./      # requires a Debian-based OS, skip if not available
./     # requires a Debian-based OS, skip if not available
  1. Instantiate the template
xmlstarlet tr --xinclude remove_containers.xsl index.xhtml > index_with_includes_resolved.xhtml
  1. Open page index_with_includes_resolved.xhtml in a web browser to show the example IAL page.

Result of performing the steps as described – a minimal working IAL 1.6 instance

As you can see in the screenshot, the icons are not automatically provided by the scripts. If you want them to display correctly, you need to download them from external sources like e. g. Wikipedia or the sources’ homepages.

The XHTML Template for IAL 1.6

The XHTML page template can be found in file index.xhtml in the repository. It consists of a page structure, stylesheet and script. The template contains XInclude links to files primary.xml, boxes.xml and scripts.xml.

The idea behind these separate files is to separate presentation and contents, The index.xhtml template can be left unmodified for a consistent presentation and all the contents can be supplied through the three external XML files. Web browsers and servers do not normally resolve the XInclude directives. Hence in order to make use of the template, the XInclude links need to be resolved explicitly. To do this, a dedicated XML tool like e.g. xmlstarlet can be used e. g. as shown under Instantiate the template above.

Users are of course free to modify the template directly and need not make use of the XInclude structure proposed here. It is possible to directly include the contents in the respective sections of the index.xhtml by replacing the XInclude with the content of interest. Staying with the XInclude scheme simplifies pulling a new index.xhtml from the repository later, though.

This file is intended to collect links to “primary” (by choice of the user) pieces of documentation. The template expects there to be a list of links with icons, but users are of course free to deviate.

If one were to link Ant, Erlang, Java, PHP and POSIX pages from this file, the associated primary.xml could e. g. look as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!-- primary.xml -->
<div id="primary_links" xmlns="">
    <a href="ant/cnt/index.html"><img src="icons/ant.gif"/></a>
    <a href="erlang/doc/index.html"><img src="icons/erlang.svg"/></a>
    <a href="java/api/index.html"><img src="icons/java.svg"/></a>
    <a href="php/php-chunked-xhtml/index.html"><img src="icons/php.svg"/></a>
    <a href="posix/susv4-2018/index.html"><img src="icons/posix.svg"/></a>

To be a useful homepage, IAL tries to crunch as many links into the space as reasonable. To achieve some structure, it allows categorizing the links into boxes. The structuring of the boxes is entirely left to the user. By default, IAL expects the boxes to contain a title as <h2> tag and links in unsorted lists which are then rendered as two columns by the CSS.

Here is an example which adds two boxes containing some links and useful webtools respectively:

<?xml version="1.0" encoding="UTF-8"?>
<!-- boxes.xml -->
<masysma:boxes xmlns:masysma=""
<div class="box">
    <h2> Links</h2>
        <li><a href=""></a></li>
        <li><a href=""></a></li>
        <li><a href=""></a></li>
        <li><a href=""></a></li>
        <li><a href="">hn</a></li>
        <li><a href="">reddit</a></li>
        <li><a href="">Yellowlab Pagespeed</a></li>

<div class="box">
        <li><a href="">MGRS</a></li>
        <li><a href=",10.000000?karte=OpenStreetMap&amp;zoom=8">Koordinaten-Umrechner GUI</a></li>
        <li><a href=""></a></li>
        <li><a href="">MD5 Red</a></li>
        <li><a href="">Detexify LaTeX Symbol</a></li>
        <li><a href="">GLS Tracking</a></li>
        <li><a href=";m1=09&amp;y1=2018&amp;d2=12&amp;m2=10&amp;y2=2018&amp;ti=on&amp;ach=3">Arbeitstagezähler</a></li>
        <li><a href="">EAN Search</a></li>
        <li><a href="">Printable Graph Paper</a></li>
        <li><a href="">Free Online Graph Paper</a></li>
        <li><a href="">TOSHIBA Check Warranty</a></li>
        <li><a href="">Integer Encoder</a></li>
        <li><a href="">Screensavers</a></li>
        <li><a href="">GCC Godbolt</a></li>
        <li><a href="">This to That (Glue Advice)</a></li>

Note the enclosing masysma:boxes element which is required as XML does not support multiple root elements per document. This tag is not used in the output XHTML as it is removed by the remove_containers.xsl stylesheet as provided in the repository.

scripts.xml – Providing Database Contents for Keyword Searches

IAL’s search feature works by keeping a map of all keys and associated URLs in memory (in the web browser). JavaScript functions in the template homepage are provided to process this data in the form of JavaScript Objects (similar to JSON). The scripts generate script.js files which are ready for being included into the home page by suitable <script> tags. For example, scripts.xml can look as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!-- scripts.xml -->
<masysma:scripts xmlns:masysma=""
    <script type="text/javascript" src="ant/script.js"></script>
    <script type="text/javascript" src="erlang/script.js"></script>
    <script type="text/javascript" src="java/script.js"></script>
    <script type="text/javascript" src="php/script.js"></script>
    <script type="text/javascript" src="posix/script.js"></script>

User Interface and Navigation

The IAL UI concept is a hybrid of VIM-like keybindings and a standard „clickable” GUI. Links can be clicked just like one expects from any (X)HTML page.

Additionally, the search input fields can be activated by mouse and a search text can be entered. In order to open the results, just press [ENTER].

The categories next to the search bars in the boxes can be clicked to toggle results from this category appearing. By default, all categories are enabled.

The keybindings are as follows:

Key Meaning
ENTER Open search result (if in a search box) or selected link otherwise
DOWN Move cursor to the next link (INSERT/navigate in search results)
UP Move cursor to the previous link (INSERT/navigate in search results)
ESC Switch to NORMAL mode (i.e. keys get the meaning as per the rows below:
i Focus the “Online”/“Google” search box
a Focus the “Docs” search box
o Focus the “Archive” search box
h Move cursor to the previous box
j Move cursor to the next link
k Move cursor to the previous link
l Move cursor to the next box

If you are using an extension like Vimium, VimFX or such to provide VIM-style keybindings for the web browser, it may be sensible to disable them for the IAL page since it implements its own (likely conflicting) keyboard navigation.


The scripts are used to download pieces of information and generate script.js files containing the relevant metadata in a format that IAL can use. The typical structure of each script is as follows:

  1. Download an archive with the documentation data.
  2. Extract this archive.
  3. From the extracted files, rename and keep only the relevant subdirectories.
  4. Generate a list of entries in script.js format from the files.

The first two steps are usually handled by an invocation of maartifact(11) which downloads from various sources and keeps local copies of the original data.

The following scripts are provided in the repository:

Script Downloads From Target Directory
pages_ada.php Debian ada-reference-manual-2012 ada Debian ant-doc ant Debian erlang-doc erlang URL jargon Debian openjdk-11-doc java URL php URL posix

Archivebox Integration

Archivebox is a tool that creates and manages offline copies of (single) websites. To this end it serves a similar function like IAL, albeit with a different focus.

Both of the tools can be integrated because the script pages_archivebox.sql can be used to read ArchiveBox’ database and create a suitable script.js for inclusion into IAL. The script is a polyglot that can be either used as a query against the database or executed from the shell in order to invoke this query in a given archivebox database.

The “Archive” box in IAL can then be used to search within the Archivebox links and [ENTER] leads to the page as captured in Archivebox.

The URL to prepend to Archivebox links is currently hardcoded to but can be changed in pages_archivebox.sql as needed.

Additionally, the integration supports certain tags to be present in the Archivebox archive and assigns different “priorities” to them. This is necessary since IAL only supports a single category per entry whereas Archivebox entries can have any number of tags. The tag with the lowest priority is assigned as category when viewed in IAL (other tags are discarded).

The following shows this as an excerpt from the script. Smaller numbers mean higher priorities.

-- pages_archivebox.sql lines 26-29
INSERT INTO masysma_tag_priorities (name, prio) VALUES
    ('alpha',       10), ('primary',     20), ('fun',         40),
    ('swrec',       40), ('gam',         40), ('dcf77',       40),
    ('book',        50);
-- ...

As one can see, the following tags are currently recognized by IAL:

Tag Description
alpha noteworthy primary sources of information
primary less important primary sources of information
fun fun entries
swrec software recommendations
gam entries about games
dcf77 entries about clocks
book entries about books or containing the content of a book

Users can either make use of these tags or define their own priorities in the script in order to declare which of the archivebox results should appear under their on category in IAL.

Data Format of script.js

The script.js-files look as follows:

    { id: "posix", box: "doc", title: "a64l()", link: "posix/susv4-2018/functions/a64l.html", primary: ["a64l()"], secondary: [] },
    { id: "posix", box: "doc", title: "abort()", link: "posix/susv4-2018/functions/abort.html", primary: ["abort()"], secondary: [] },
    /* ... */

I.e.: There is always a call to ial_add_data to add the data to IAL’s memory. This function takes a list of objects with the following properties:

Property Type Description
id String Specifies the category of the entry.
box doc | abx Specifies the box to associate this entry to.
title String Display name of the entry.
link String Link to open on pressing [ENTER] on this entry.
primary List<String> Strings to match for searching (prefixes).
secondary List<String> Alternate strings to match for searching.

The primary list is only matched in terms of prefixes whereas the secondary matches appear in the results if the search box contains a substring of the secondary keyword. In the search results, all primary results appear first, followed by all matches from secondary entries.

Recommended default values: box: "doc", secondary: [].

Example Makefile and Systemd User Service

To automatically keep the generated file in sync with the changes made to the XML files and also to Archivebox databases, a Makefile alongside with Systemd user services is provided in directory example.

Create a directory to store your copy of IAL into (e.g. /data/main/130_archivebox/ial) and place all the customized XML files (boxes.xml, scripts.xml, primary.xml) there alongside a copy of index.xhtml under the name tpl.xml and a copy of the Makefile.

I.e. in terms of shell commands this might look as follows

cp example/ialupdate.*               ~/.config/systemd/user
cp example/Makefile index.xhtml      /data/main/130_archivebox/ial
cp boxes.xml primary.xml scripts.xml /data/main/130_archivebox/ial

The systemd user services can be installed by copying them to ~/.config/systemd/user and then enabling them through systemd, e.g.

systemctl --user daemon-reload
systemctl --user enable ialupdate.service
systemctl --user enable ialupdate.timer

The ialupdate.service file needs to be edited to point to the target directory of the IAL to update:

# ialupdate.service
[Unit] IAL Update

ExecStart=make -C /data/main/130_archivebox/ial


In the Makefile, let ARCHIVEBOX point to the location of your Archivebox installation’s directory containing the file index.sqlite3.

# Makefile
MDVL_CI_PHOENIX_ROOT = /data/main/120_mdvl_rr
IAL_SRC              = $(MDVL_CI_PHOENIX_ROOT)/bo-ial
ARCHIVEBOX           = ../data

all: archivebox/script.js index.xhtml

archivebox/script.js: $(ARCHIVEBOX)/index.sqlite3 $(IAL_SRC)/pages_archivebox.sql
    $(IAL_SRC)/pages_archivebox.sql $(ARCHIVEBOX)/index.sqlite3

index.xhtml: tpl.xhtml $(IAL_SRC)/remove_containers.xsl
    xmlstarlet tr --xinclude $(IAL_SRC)/remove_containers.xsl tpl.xhtml \
                                > index.xhtml

tpl.xhtml: $(IAL_SRC)/index.xhtml
    cp $< $@


Since meaningful IAL deployments are likely to mix proprietary data with the repository contents, IAL is released under a permissive CC0-1.0 license except for the logo and icon. See LICENSE.txt for the CC0-1.0 license information. Website 5 (1.0.2) – no Flash, no JavaScript, no Webfont, no Copy Protection, no Mobile First. No bullshit. No GUI needed. Works with any browser.

Created: 2023/05/07 17:57:36 | Tags: ial, d5man2, information, links, documentation, offline | Version: 1.6.x | SRC (Pandoc MD) | GPL

(c) 2023