Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/mkamarin/Hugo-2-Gopher-and-Gemini

A Hugo theme to convert a Hugo site to Gopher and or Gemini with the purpose of maintaining a three between one and three sites (one in html, gopher, and or gemini). Each site can have different content. The main html site is expected to use one of the many Hugo themes.
https://github.com/mkamarin/Hugo-2-Gopher-and-Gemini

Last synced: 3 months ago
JSON representation

Host: GitHub
URL: https://github.com/mkamarin/Hugo-2-Gopher-and-Gemini
Owner: mkamarin
License: gpl-3.0
Created: 2021-03-07T21:29:40.000Z (over 3 years ago)
Default Branch: main
Last Pushed: 2023-02-13T23:41:06.000Z (over 1 year ago)
Last Synced: 2024-05-20T22:12:31.981Z (6 months ago)
Language: Python
Size: 81.1 KB
Stars: 22
Watchers: 3
Forks: 1
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

awesome-gemini - Hugo-2-Gopher-and-Gemini - A Hugo theme to convert a Hugo site to Gemini or Gopher. (Tools / Gemtext converters)

README

# Hugo-2-Gopher-and-Gemini
A [Hugo](https://gohugo.io/) theme to convert a Hugo site to [Gopher](https://en.wikipedia.org/wiki/Gopher_%28protocol%29) and/or [Gemini](https://en.wikipedia.org/wiki/Gemini_%28protocol%29) with the purpose of maintaining between one and three sites (a static web site, a Gopher hole, and a Gemini capsule). Each site may have different content.

This theme is expected to be used as an additional theme. While, by default, your main theme will generate the site in the `public` folder, this additional theme will generate in `public-gg`. This requires two distinct executions of `hugo`, namely one for your regular theme, and one for this theme. There are no changes or side effects to your original Hugo site or files.

There are few use cases for this theme:
* A person with a current Hugo generated site that want to have presence in Gopher space or/and in Gemini space, while maintaining the original web site using Hugo. In this situation the person can use Hugo to maintain all the sites (the web site, the Gopher hole and the Gemini capsule). Most content will be common between them, but other content may be specific to one or two of the sites.
* A person that wants to use Hugo to generate and maintain a Gemini capsule or Gopher hole.
* A person that wants to migrate a current Hugo web site to a Gemini capsule or a Gopher hole.

You may find my [basic step by step on how to use this tool](https://www.mkamarin.com/posts/xhugo2ggx/) useful to understand this page.
In addition you may find the [Gopher-and-Gemini-Walker](https://github.com/mkamarin/Gopher-and-Gemini-Walker) tool useful to verify the generated Gopher hole and/or the Gemini capsule before deploying them.

## Features
- Menu
- Social media links
- Do not generate HTML or RSS
- Automatic conversion of a Hugo site to a Gopher hole
- Automatic conversion of a Hugo site to a Gemini capsule

## Installation & Update
In most cases, you will already have Hugo installed and have already a theme for your web site. You will install this theme as an additional complementary theme (while maintaining your current theme). However, if you have not installed hugo follow the instructions at [quick start](https://gohugo.io/getting-started/quick-start/).

To add this theme to your current hugo site, just do:

```sh
~$ git clone https://github.com/mkamarin/Hugo-2-Gopher-and-Gemini.git
```

For more information, see [Hugo docs](https://gohugo.io/themes/installing/). For upgrades, just do:

```sh
~$ git submodule update --remote --merge
```

## Short set of Steps

1. You need to copy the `config-gg.toml` file to the main folder of your hugo site and edit it to adjust it to your situation. Now you have two distinct config files, namely one for your main theme (`config.toml`) and one for this theme (`config-gg.toml`).
2.
You may want some pages to be treated different when generating them for Gopher or Gemini. In those cases, you can add to the page front matter some of the flags described in `Hugo-2-Gopher-and-Gemini/archetypes/default.md`.

2. If you plan to have content that is specific to Gopher and/or Gemini, you may want to use a naming convention for those posts. For example, you may name those posts `-gg.md` and write them in a way that will look nice in Gopher and/or Gemini. In that case, you want to add the following line to your main `config.toml` file:

```toml
ignoreFiles = ["-gg.md$"]
```

Then, when you want to create content that should only be in Gopher and/or Gemini, you will create the markdown file as follows:

```bash
~$ hugo new posts/name-gg.md
```

3. You need to create an empty folder called `layouts-gg`. This is done to avoid hugo from using the content in your main `layouts` folder.

```sh
~$ mkdir layouts-gg
```

4. The `public-gg` folder will have two sub-folders, one for the Gopher hole named `public-gg/gopher` and one for the Gemini capsule named `public-gg/gemini`. There are two ways you can generate the `public-gg` folder:

* Execute `hugo2gg.py` located in this theme folder under `src`. In most cases, the default options will work fine. You can see all the options by executing `hugo2gg.py --help`. Based on the options, `hugo2gg.py` will execute hugo as the first step of the conversion. So, in most cases, you just want to execute it from the main folder of your hugo site as:

```sh
~$ themes/Hugo-2-Gopher-and-Gemini/src/hugo2gg.py
```

* If you want to execute hugo manually before executing `hugo2gg.py`, you can do as follows:

```sh
~$ hugo --config config-gg.toml --destination public-gg --layoutDir layouts-gg --disableKinds sitemap

~$ themes/Hugo-2-Gopher-and-Gemini/src/hugo2gg.py --no-hugo
```

5. Now you can check the generated files. By default, the Gopher hole will be in `public-gg/gopher` and the Gemini capsule in `public-gg/gemini`. You may want to browse those directories using the [Gopher-and-Gemini-Walker](https://github.com/mkamarin/Gopher-and-Gemini-Walker) tool before deploying them to your hosting environment.

## Usage

```bash
Usage:
hugo2gg.py [flags]

Flags:
-p, --path Path of the site to be converted (default to public-gg)
-g, --gopher Gopher output folder (default to public-gg/gopher)
-G, --gemini Gemini output folder (default to public-gg/gemini)
-e, --empty Path of empty folder (default to layouts-gg)
-l, --last Path for last build folder (default to public-gg-sav)
-b, --base Rebase all Gopher absolute links to
-B, --Base Rebase all Gemini absolute links to
-c, --config Name of the hugo config file (default to config-gg.toml)
-M, --map File with mapping of labels to links (default to hugo2gg.map)
-t, --type type of output to be generated (default to none)
can be:
all Generate both gopher and gemini sites
gopher Generate only the gopher hole
gemini Generate only the gemini capsule
-k, --keep Keep processed temporary files for debugging purposes
-m, --max-line Max lenght of gophermap lines (default 70 but some prefer 67)
-f, --full-line Forces each line in the gophermap to be fully compliant
(overrides fullLine and textChar in config-gg.toml)
-n, --no-hugo Do not run hugo. Remember to run hugo before
-w, --white-lines Indicate the max number of empty lines (default 1)
-h, --help Prints this help
-v, --verbose Produces verbose stdout output

```

## Fixup script
The script `src/fixup.sh` is useful to post-process the generated Gopher hole or Gemini capsule before deployment. Although, `src/hugo2gg.py` implements the same functionality, in my workflow I have found it easier to use `src/fixup.sh`.

This script is useful to re-base a Gemini capsule or Gopher hole. Meaning, changing all the absolute links (links that start with "/") to add a base directory.

In addition, this script can add the correct host and port to a gophermap. Therefore, making each line in the gophermap comply with the four tabs expected by some Gopher servers.

## License
GPLv3