change: updates readme for fork
6 files changed, 21 insertions(+), 217 deletions(-)

A => .build.yml
R CONTRIBUTING.md => 
M README.md
R code_of_conduct.md => 
R go.mod => 
R netlify.toml => 
A => .build.yml +12 -0
@@ 0,0 1,12 @@ 
+image: alpine/edge
+packages:
+  - hugo
+sources:
+  - hg+https://hg.sr.ht/~ser/hugo-tufte
+secrets:
+    - 45926939-38b0-4e7f-bfa5-1a5b5786a773
+    - d7d86c19-5b94-4c65-bf07-b8b30f55bd63
+tasks:
+    - build: |
+        cd ${PROJ}/exampleSite
+        hugo --gc --minify

          
R CONTRIBUTING.md =>  +0 -66
@@ 1,66 0,0 @@ 
-# Introduction
-
-> First off, thank you for considering contributing to Hugo-Tufte!
-
-
-# Ground Rules
-
-- Respect the [Code of conduct]()
-- ***If you just have a question use this [Discussion](https://github.com/slashformotion/hugo-tufte/discussions).***
-
-
-# How to report a bug
-
-### Tell your contributors how to file a bug report.
-You can even include a template so people can just copy-paste (again, less work for you).
-
-When filing an issue, make sure to answer these five questions:
-
-1. What version of Go are you using (`$ hugo version`)?
-2. What operating system and processor architecture are you using?
-3. What did you do?
-4. What did you expect to see?
-5. What did you see instead?
-
-
-# How to suggest a feature or enhancement
-
-If you find yourself wishing for a feature that doesn't exist in hugo-tufte, you are probably not alone. There are bound to be others out there with similar needs. Open an issue on our issues list on GitHub which describes the feature you would like to see, why you need it, and how it should work.
-
-# Your First Contribution
-
-<center>
-
-![](https://media.giphy.com/media/3oEduFYRfaeS6KViN2/giphy.gif)
-
-</center>
-
-Learn how pull request works here: 
-- https://makeapullrequest.com
-- http://www.firsttimersonly.com/
-
-> Working on your first Pull Request? You can learn how from this *free* series, [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
-
-
-
->At this point, you're ready to make your changes! Feel free to ask for help [here](https://github.com/slashformotion/hugo-tufte/discussions); everyone is a beginner at first :smile_cat:
->
->If a maintainer **(me)** asks you to "rebase" your PR, they're saying that a lot of code has changed, and that you need to update your branch so it's easier to merge.
-
-# Getting started to contribute with code
-
-1. Create your own fork of the code
-2. Do the changes in your fork
-3. If you like the change and think the project could use it:
-    * Be sure that you didn't break anything. 
-
-<center>
-
-![](https://media.giphy.com/media/3o7btNa0RUYa5E7iiQ/giphy-downsized.gif)
-
-</center>
-
-
-# Community
-
-You can chat with me [here](https://github.com/slashformotion/hugo-tufte/discussions).

          
M README.md +9 -8
@@ 1,6 1,6 @@ 
 # Tufte Hugo Theme
 
-[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.0-4baaaa.svg)](code_of_conduct.md) [![Test Build](https://github.com/loikein/hugo-tufte/actions/workflows/test-build.yml/badge.svg)](https://github.com/loikein/hugo-tufte/actions/workflows/test-build.yml) [![Netlify Status](https://api.netlify.com/api/v1/badges/0a3e11e2-0209-40bb-8570-c3eb9b8471dc/deploy-status)](https://app.netlify.com/sites/huto-tufte/deploys)
+[![Test Build](https://builds.sr.ht/~ser/hugo-tufte/.build.yml.svg)](https://builds.sr.ht/~ser/hugo-tufte/.build.yml?) ★ [License (MIT)](https://hg.sr.ht/~ser/hugo-tufte/browse/LICENSE.md?rev=tip)
 
 ## History of this project
 

          
@@ 11,7 11,8 @@ attempts to be a faithful implementation
 
 - The original repo: [shawnohare/hugo-tufte](https://github.com/shawnohare/hugo-tufte)
 - Second repo: [slashformotion/hugo-tufte](https://github.com/slashformotion/hugo-tufte)
-- This ([loikein/hugo-tufte](https://github.com/loikein/hugo-tufte)) is now the _de facto_ third repo although my original intension was only to make a few tweaks.
+- Third repo: ([loikein/hugo-tufte](https://github.com/loikein/hugo-tufte)) is now the _de facto_ third repo although my original intension was only to make a few tweaks.
+- This repo: ([~ser/hugo-tufte](https://hg.sr.ht/~ser/hugo-tufte)). Moved from github to Sourcehut, and from git to Mercurial. The motivation was because Hugo keeps changing its API (by refusing to release a 1.x.x release, even on an 11 year-old project, they cleverly avoid committing to backwards compatability and keep their theme developers in instability hell! Genius!), and the theme needed updating in advance of breaking changes. The hosting move was because monocultures suck, and the VCS change was because Mercurial is objectively superior to to Git.
 
 ## Quickstart
 

          
@@ 33,7 34,7 @@ You'll need to install Hugo Extended for
 ### Check out the example site
 
 ```shell
-git clone https://github.com/loikein/hugo-tufte.git
+hg clone https://hg.sr.ht/~ser/hugo-tufte
 cd hugo-tufte/exampleSite
 hugo server --buildDrafts --disableFastRender
 ```

          
@@ 50,7 51,7 @@ The showcase posts are:
 ```shell
 hugo new site <your-site-name>
 cd <your-site-name>/themes/
-git clone https://github.com/loikein/hugo-tufte.git
+hg clone https://hg.sr.ht/~ser/hugo-tufte
 ```
 
 Add `theme: 'hugo-tufte'` to your `config.yaml` to let your site know to actually use _this_ theme, specifically.

          
@@ 63,7 64,7 @@ Then run `hugo server --buildDrafts --di
 
 In this version, I use [Yihui Xie's method](https://yihui.org/en/2018/07/latex-math-markdown/) to support (almost) seamless LaTeX rendering with [KaTeX](https://katex.org/).
 
-For usage and examples, refer to [./exampleSite/content/posts/tufte-features.md ](https://github.com/loikein/hugo-tufte/blob/main/exampleSite/content/posts/tufte-features.md).
+For usage and examples, refer to [./exampleSite/content/posts/tufte-features.md ](https://hg.sr.ht/~ser/hugo-tufte/blob/main/exampleSite/content/posts/tufte-features.md).
 
 Downside: LaTeX in post title is no longer supported.
 

          
@@ 101,7 102,7 @@ You can add links to your social media p
 - `orcid`: string
 - `google_scholar`: string
 
-Please see [`exampleSite/config.yaml`](https://github.com/loikein/hugo-tufte/blob/main/exampleSite/config.yaml#L47) to see the full implementation with exemples.
+Please see [`exampleSite/config.yaml`](https://hg.sr.ht/~ser/hugo-tufte/blob/main/exampleSite/config.yaml#L47) to see the full implementation with exemples.
 
 ### Page Parameters
 

          
@@ 113,7 114,7 @@ Please see [`exampleSite/config.yaml`](h
 - `toc` boolean: if true, display the table of contents for the page.
 - Layout parameters: (NEW)
   + For more information, see [Hugo's Lookup Order | Hugo](https://gohugo.io/templates/lookup-order/).
-  + `type` string: If set to `book`, layout files in [./layouts/book/](https://github.com/loikein/hugo-tufte/tree/main/layouts/book) will be prioritised.
+  + `type` string: If set to `book`, layout files in [./layouts/book/](https://hg.sr.ht/~ser/hugo-tufte/tree/main/layouts/book) will be prioritised.
   + `layout` string: If set, layout files with the name of this field's value will be prioritised.
 
 ### Shortcodes

          
@@ 121,7 122,7 @@ Please see [`exampleSite/config.yaml`](h
 This theme provides the following shortcodes in an attempt to completely
 support all the features present in the [Tufte-css](https://github.com/edwardtufte/tufte-css) project.
 
-For usage and examples, refer to [./exampleSite/content/posts/tufte-features.md ](https://github.com/loikein/hugo-tufte/blob/main/exampleSite/content/posts/tufte-features.md).
+For usage and examples, refer to [./exampleSite/content/posts/tufte-features.md ](https://hg.sr.ht/~ser/hugo-tufte/blob/main/exampleSite/content/posts/tufte-features.md).
 
 - `blockquote`
 - `div`

          
R code_of_conduct.md =>  +0 -134
@@ 1,134 0,0 @@ 
-
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-slashformotion[at]protonmail[dot].com.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
-
-Community Impact Guidelines were inspired by 
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
-at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
-

          
R go.mod =>  +0 -3
@@ 1,3 0,0 @@ 
-module github.com/loikein/hugo-tufte
-
-go 1.17

          
R netlify.toml =>  +0 -6
@@ 1,6 0,0 @@ 
-[build]
-command = "cd exampleSite && hugo --buildDrafts --minify --gc --themesDir .. --theme ."
-publish = "exampleSite/public"
-
-[build.environment]
-HUGO_THEME = "hugo-tufte"