fix: removed unused files

2025-03-17 19:05:39 +01:00 · 2025-03-17 19:05:39 +01:00 · c1c15120d6
commit c1c15120d6
parent fb20e0ee0c
9 changed files with 0 additions and 1588 deletions
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@ -1,128 +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, 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
 tabi@osc.garden.
 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.
 Community Impact Guidelines were inspired by [Mozilla's code of conduct
 enforcement ladder](https://github.com/mozilla/diversity).
 [homepage]: https://www.contributor-covenant.org
 For answers to common questions about this code of conduct, see the FAQ at
 https://www.contributor-covenant.org/faq. Translations are available at
 https://www.contributor-covenant.org/translations.
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@ -1,122 +0,0 @@
 # Contributing to tabi
 Halló!
 Thanks for contributing to [tabi](https://github.com/welpo/tabi). Before implementing new features and changes, please [submit an issue](https://github.com/welpo/tabi/issues/new) so that we can discuss it.
 We welcome contributions in many forms, including:
 - Bug reports;
 - New translations;
 - Improvements to existing translations;
 - Feature requests;
 - Code patches;
 - Documentation improvements;
 - UI/UX suggestions.
 If you're not sure how to contribute or need help with something, please don't hesitate to reach out via the [issue tracker](https://github.com/welpo/tabi/issues) or [mail](mailto:tabi@osc.garden?subject=[GitHub]%20tabi).
 ## Pull Requests
 Working on your first Pull Request? You can learn how from this free video series:
 [**How to Contribute to an Open Source Project on GitHub**](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github)
 Please make sure the following is done when submitting a pull request:
 1. **Keep your PR small**. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it.
 2. **Use descriptive titles**. It is recommended to follow this [commit message style](#conventional-commit-messages-with-gitmoji).
 3. **Test your changes**. Make sure to test different configurations that might affect your changes.
 4. **Fill the PR template**. The template will guide you through the process of submitting a PR.
 ### Conventional Commit Messages with Gitmoji
 See how a minor change to your commit message style can make you a better programmer.
 Format: `<gitmoji> <type>(<scope>): <description>`
 `<gitmoji>` is an emoji from the [gitmoji](https://gitmoji.dev/) list. It makes it easier to visually scan the commit history and quickly grasp the purpose of changes.
 `<scope>` is optional. If your change affects a specific part of the codebase, consider adding the scope. Scopes should be brief but recognizable, e.g. `config`, `feed`, or `search`.
 The various types of commits:
 - `feat`: a new API or behaviour **for the end user**.
 - `fix`: a bug fix **for the end user**.
 - `style`: changes to the visual appearance of the theme, e.g. CSS, fonts, images…
 - `docs`: a change to the website or other Markdown documents.
 - `refactor`: a change to code that doesn't change behaviour, e.g. splitting files, renaming internal variables, improving code style…
 - `chore`: upgrading dependencies, releasing new versions… Chores that are **regularly done** for maintenance purposes.
 - `misc`: anything else that doesn't change production code, yet is not `chore`. e.g. updating GitHub actions workflow.
 The commits within your PR don't need to follow this convention (we'll [squash them](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)). However, the PR title should be in this format. If you're not sure about the title, don't worry, we'll help you fix it. Your code is more important than conventions!
 Example:
 ```text
 🐛 fix(i18n): localise date in single taxonomy listing
 ^  ^-^^----^  ^--------------------------------------^
 |  |  |       |
 |  |  |       +-> Description in imperative and lowercase.
 |  |  |
 |  |  +-> The scope of the change.
 |  |
 |  +-------> Type: see above for the list we use.
 |
 +----------> A valid gitmoji.
 ```
 ## Coding Style Guidelines
 While we don't enforce a strict coding style, we appreciate it when contributions follow the existing code style of the project (e.g. indenting with 4 spaces). This makes the codebase easier to read and maintain. If you are making significant changes or additions, please try to maintain consistency with the current coding patterns and idioms.
 For JavaScript files, we use [Prettier](https://prettier.io/) to format the code.
 The CSS properties are sorted following [Concentric-CSS](https://github.com/brandon-rhodes/Concentric-CSS). If you use VSCode, the [Sort CSS](https://marketplace.visualstudio.com/items?itemName=piyushsarkar.sort-css-properties) extension makes this super easy.
 ## Pre-commit Githook
 ### Introduction
 We use a pre-commit githook to maintain code and file quality. [This script](https://github.com/welpo/tabi/blob/main/.githooks/pre-commit) performs a series of checks and updates before a commit is made.
 ### Setting Up
 To use the pre-commit githook, run the following command from the root of the repository to configure the git hooks path and make the script executable:
 ```bash
 git config core.hooksPath .githooks
 chmod +x .githooks/pre-commit
 ```
 ### Features
 The pre-commit githook performs the following actions:
 #### Automatic Updates
 - **Front Matter in Markdown Files**: Automatically updates the "updated" field in the front matter of `.md` files.
 - **PNG Compression**: Compresses PNG files using either [`oxipng`](https://github.com/shssoichiro/oxipng) or [`optipng`](https://optipng.sourceforge.net/), whichever is available on your system.
 - **Font Subsetting**: Runs `subset_font` if `config.toml` has been modified.
 #### Commit Checks
 The script prevents you from committing if:
 - The `.md` file is marked as a draft.
 - Any file contains a "TODO".
 - A JavaScript file is being committed without a corresponding minified version.
 - A minified JavaScript file is not as small as it could be. Requires installing [UglifyJS](https://github.com/mishoo/UglifyJS) and/or [terser](https://github.com/terser/terser).
 - `config.toml` and `theme.toml` have different numbers of lines in their `[extra]` sections.
 These checks are in place to ensure code quality and consistency throughout the project.
 ## Code of Conduct
 We expect all contributors to follow our [Code of Conduct](./CODE_OF_CONDUCT.md). Please be respectful and professional when interacting with other contributors.
 ## License
 The code is available under the [MIT license](./LICENSE).
 Thank you for your contributions!
--- a/21
+++ b/21
@ -1,21 +0,0 @@
 MIT License
 Copyright (c) 2023 Óscar Fernández
 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.
--- a/cliff.toml
+++ b/cliff.toml
@ -1,148 +0,0 @@
 # git-cliff ~ default configuration file
 # https://git-cliff.org/docs/configuration
 #
 # Lines starting with "#" are comments.
 # Configuration options are organized into tables and keys.
 # See documentation for more information on available options.
 [remote.github]
 owner = "welpo"
 repo = "tabi"
 [changelog]
 # changelog header
 header = """
 # Changelog
 Welcome to the changelog for tabi. This document aims to provide a comprehensive list of all notable changes made to the project, organised chronologically by release version.
 We use Semantic Versioning (SemVer) for our version numbers, formatted as MAJOR.MINOR.PATCH. Major version changes involve significant (breaking) changes, minor versions introduce features and improvements in a backward compatible manner, and patch versions are for bug fixes and minor tweaks.\n
 """
 # template for the changelog body
 # https://keats.github.io/tera/docs/#introduction
 body = """
 {%- macro remote_url() -%}
  https://github.com/{{ remote.github.owner }}/{{ remote.github.repo }}
 {%- endmacro -%}
 {% if version %}\
    {% if previous.version %}\
        ## [{{ version | trim_start_matches(pat="v") }}]({{ self::remote_url() }}/compare/{{ previous.version }}..{{ version }}) - {{ timestamp | date(format="%Y-%m-%d") }}
    {% else %}\
        ## {{ version | trim_start_matches(pat="v") }} - {{ timestamp | date(format="%Y-%m-%d") }}
    {% endif %}\
 {% else %}\
    ## unreleased
 {% endif %}\
 {% macro commit(commit, in_breaking_section=false) -%}
    - {% if commit.scope %}*({{ commit.scope }})* {% endif %}{% if commit.breaking and not in_breaking_section %}[**‼️BREAKING‼️**] {% endif %}\
        {{ commit.message | upper_first }}\
        {% if not commit.remote.pr_number %} ([{{ commit.id | truncate(length=7, end="") }}]({{ self::remote_url() }}/commit/{{ commit.id }})){%- endif -%}{% if commit.remote.username %} by @{{ commit.remote.username }} \
        {%- set co_authors = commit.footers | filter(attribute="token", value="Co-authored-by") | map(attribute="value") -%}
        {%- set number_of_co_authors = co_authors | length -%}
        {%- for co_author in co_authors -%}
            {%- if not loop.last %}, {% else %} and {% endif %}@{{ co_author | split(pat=" <") | first | trim }}
        {%- endfor -%}
        {%- endif -%}
 {% endmacro -%}
 {%- set breaking_header_shown = false -%}
 {% for commit in commits -%}
    {% if commit.breaking and not breaking_header_shown -%}
        {% raw %}\n### 💥 BREAKING CHANGES 💥\n{% endraw %}
        {%- set_global breaking_header_shown = true -%}
    {%- endif -%}
    {%- if commit.breaking %}
        {{ self::commit(commit=commit, in_breaking_section=true) -}}
    {% endif -%}
 {%- endfor -%}
 {%- if breaking_header_shown == true -%}
    {% raw %}\n{% endraw %}\
 {%- endif -%}
 {% for group, commits in commits | group_by(attribute="group") %}
    ### {{ group | striptags | trim | upper_first }}
    {% for commit in commits
    | filter(attribute="scope")
    | sort(attribute="scope") %}
        {{ self::commit(commit=commit) }}
    {%- endfor -%}
    {% raw %}\n{% endraw %}\
    {%- for commit in commits %}
        {%- if not commit.scope -%}
            {{ self::commit(commit=commit) }}
        {% endif -%}
    {% endfor -%}
 {% endfor %}
 {%- if github.contributors | filter(attribute="is_first_time", value=true) | length != 0 -%}
  {% raw %}\n{% endraw %}### 👥 New contributors
  {% raw -%}\n{% endraw -%}
 {% for contributor in github.contributors | filter(attribute="is_first_time", value=true) %}
  🫶 @{{ contributor.username }} made their first contribution
    {%- if contributor.pr_number %} in \
      [#{{ contributor.pr_number }}]({{ self::remote_url() }}/pull/{{ contributor.pr_number }}) \
    {%- endif %}
 {% endfor %}
 {%- endif %}
 {% raw -%}\n{% endraw -%}
 """
 # remove the leading and trailing whitespace from the template
 trim = true
 # changelog footer
 footer = """
 <!-- generated by git-cliff -->
 """
 # postprocessors
 postprocessors = [
    # { pattern = " @([a-zA-Z0-9](?:[a-zA-Z0-9]+-?)*[a-zA-Z0-9])", replace = " [@$1](https://github.com/$1)"}, # add link to GitHub usernames (done in release script instead)
 ]
 [git]
 # parse the commits based on https://www.conventionalcommits.org
 conventional_commits = true
 # filter out the commits that are not conventional
 filter_unconventional = true
 # process each line of a commit as an individual commit
 split_commits = false
 # regex for preprocessing the commit messages
 commit_preprocessors = [
    # Replace the issue number with the link.
    { pattern = "\\(#([0-9]+)\\)", replace = "([#${1}](https://github.com/welpo/tabi/issues/${1}))" },
    # Remove trailing whitespace.
    { pattern = ' +$', replace = "" },
    # Replace multiple spaces with a single space.
    { pattern = ' +', replace = " " },
    # Remove gitmoji, both actual UTF emoji and :emoji:
    { pattern = ' *(:\w+:|[\p{Emoji_Presentation}\p{Extended_Pictographic}](?:\u{FE0F})?\u{200D}?) *', replace = "" },
 ]
 # regex for parsing and grouping commits
 commit_parsers = [
    { message = "^feat", group = "<!-- 0 -->✨ Features" },
    { message = "^fix", group = "<!-- 1 -->🐛 Bug fixes" },
    { message = "^style", group = "<!-- 2 -->💄 Styling" },
    { message = "^doc", group = "<!-- 3 -->📝 Documentation" },
    { message = "^refactor", group = "<!-- 4 -->♻️ Refactor" },
    { message = "^test", group = "<!-- 5 -->✅ Testing" },
    { message = "^misc", group = "<!-- 6 -->🔧 Miscellaneous tasks" },
    { message = "^deprecate", group = "<!-- 7 -->🗑️️ Deprecations" },
    { message = "^chore", skip = true },
 ]
 # protect breaking changes from being skipped due to matching a skipping commit_parser
 protect_breaking_commits = true
 # filter out the commits that are not matched by commit parsers
 filter_commits = true
 # regex for matching git tags
 tag_pattern = "v[0-9].*"
 # regex for skipping tags
 skip_tags = "v0.1.0-beta.1"
 # regex for ignoring tags
 ignore_tags = ""
 # sort the tags topologically
 topo_order = false
 # sort the commits inside sections by oldest/newest order
 sort_commits = "newest"
 # limit the number of commits included in the changelog.
 # limit_commits = 42
--- a/light_dark_screenshot.png
+++ b/light_dark_screenshot.png
--- a/lighthouse_score.png
+++ b/lighthouse_score.png
--- a/screenshot.png
+++ b/screenshot.png
--- a/sumi.toml
+++ b/sumi.toml
@ -1,57 +0,0 @@
 # git-sumi ~ configuration file
 # Config: https://sumi.rs/docs/configuration
 # Rules: https://sumi.rs/docs/rules
 # Suppresses progress messages.
 quiet = false
 # Displays parsed commit message.
 display = true
 # Sets display format: cli, json, table, toml.
 format = "cli"
 # Processes each non-empty line as an individual commit.
 split_lines = false
 # Rule: Include one valid Gitmoji.
 # See https://gitmoji.dev/.
 gitmoji = true
 # Rule: Description must start with the specified case.
 # Options: 'any', 'lower', 'upper'.
 description_case = "lower"
 # Rule: Use the imperative mood in the description.
 # Example: 'Fix bug' instead of 'Fixed bug'.
 imperative = true
 # Rule: Do not end commit header with a period.
 no_period = true
 # Rule: Header length limit.
 # A value of 0 disables the rule.
 max_header_length = 55
 # Rule: Body line length limit.
 # A value of 0 disables the rule.
 max_body_length = 80
 # Rule: No leading, trailing, or consecutive spaces.
 whitespace = true
 # Rule: Follow Conventional Commits format.
 # See https://www.conventionalcommits.org/.
 conventional = true
 # Rule: List of allowed commit scopes.
 # An empty list allows all scopes. Example: ["docs", "cli"].
 scopes_allowed = []
 # Rule: List of allowed commit types.
 # An empty list allows all types. Example: ["feat", "fix", "docs"].
 types_allowed = ["feat", "fix", "docs", "refactor", "test", "chore", "misc", "style"]
 # Rule: Header must match regex pattern.
 # Example: '^JIRA-\d+:'.
 header_pattern = '^([\p{Emoji_Presentation}\p{Extended_Pictographic}](?:\u{FE0F})?\u{200D}?) \w' # The first character must be an emoji.