Overview

Relevant source files

This document provides a technical introduction to the Wikinder platform, explaining its architecture, purpose, and key characteristics. Wikinder is a static wiki site that converts content from GitHub Wiki into deployable HTML pages. For detailed information about specific subsystems, see System Architecture, Deployment Infrastructure, and Content Management Workflow.

What is Wikinder

Wikinder is an open-source educational content platform that publishes static HTML pages generated from a GitHub Wiki repository. The platform serves mathematical formulas, music notation, language analysis, and general educational articles under a Creative Commons license.

The primary domain wikinder.org points to a multi-platform hosting infrastructure with redundant deployments across Cloudflare Pages, GitHub Pages, GitLab Pages, and Vercel.

Sources: README.md1-19 Wikinder.html1-147 index.html1-96

Core Identity

Property	Value
Organization	Wikinder
Founder	bear
Founding Date	September 1, 2005
Primary Domain	`wikinder.org`
License	CC BY-SA 4.0
Content Source	GitHub Wiki (`github.com/wikinder/wikinder/wiki`)
Site Type	Static HTML

Sources: Wikinder.html83-89 README.md5

System Architecture Overview

The following diagram illustrates how Wikinder's components interact from content creation to user access:

Content-to-Delivery Pipeline

Sources: README.md5-12 .github/workflows/static.yml1-52

Repository Structure Mapping

This diagram maps the repository's file structure to functional components:

Sources: index.html9-12 Wikinder.html9 assets/css/style.css1 assets/js/mathjax-config.js1 .github/workflows/static.yml1

Key Characteristics

Static Site Architecture

Wikinder generates pure static HTML with no server-side processing. Each page is a self-contained HTML5 document that includes:

Embedded metadata (Open Graph, Twitter Cards, JSON-LD)
Inline navigation elements
Client-side JavaScript for math rendering (MathJax)
Shared CSS styling

All pages follow a consistent template structure with <header>, <main>, <article>, and <footer> semantic elements.

Sources: index.html1-96 Wikinder.html1-147

Content Source Strategy

Content originates from a GitHub Wiki repository located at github.com/wikinder/wikinder/wiki. This approach provides:

Benefit	Implementation
Collaborative Editing	GitHub Wiki's web interface
Version Control	Git commit history
Attribution	Commit-based authorship tracking
Accessibility	No build tools required for editing

Each HTML page links back to its source wiki page via the footer edit link.

Sources: README.md5 index.html91 Wikinder.html142

Open Licensing Framework

All content is licensed under CC BY-SA 4.0 (Creative Commons Attribution-ShareAlike 4.0 International). This license is declared in three locations on every page:

HTML <head> link element: <link rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/">
JSON-LD structured data: "license": "https://creativecommons.org/licenses/by-sa/4.0/"
Footer text: "Content is available under CC BY-SA 4.0 unless otherwise noted."

Attribution is implemented through JSON-LD author objects that reference specific Git commit hashes.

Sources: index.html15-89 Wikinder.html11-140

Multi-Platform Deployment

Wikinder deploys to four independent hosting platforms simultaneously:

Platform	URL	Role
Cloudflare Pages	`wikindergarten.pages.dev`	Primary (DNS points here)
GitHub Pages	`wikinder.github.io`	Redundant hosting
GitLab Pages	`wikinder.gitlab.io`	Redundant hosting
Vercel	`wikinder.vercel.app`	Redundant hosting

This redundancy ensures availability even if one platform experiences downtime.

Sources: README.md7-12

Archival Strategy

The platform maintains archival copies through three independent services:

Archive.today - https://archive.today/wikinder.org
Internet Archive - https://web.archive.org/web/*/wikinder.org*
Megalodon - https://gyo.tc/https://wikinder.org

These archives preserve historical versions and protect against data loss.

Sources: README.md14-18 Wikinder.html118-132

Content Categories

Wikinder publishes content across several thematic areas:

Content Type Distribution

Sources: index.html57 Math.html1 Wikinder.html78

Category	Page Count	Key Files
Mathematics	5	`Math.html`, `Math-formulas.html`, `Math-formulas-proofs.html`
Music	1	`LilyPond-sheet-music.html`
Language	1	`Chinese-characters.html`
Meta/About	4	`Wikinder.html`, `Wikinder-Japan.html`, `yuuki.html`, `bear.html`
Homepage	1	`index.html`

Sources: index.html57

Technology Stack

Core Technologies

Component	Technology	Implementation
Markup	HTML5	Semantic elements (`<article>`, `<header>`, `<main>`)
Styling	CSS3	Single global stylesheet (`/assets/css/style.css`)
Math Rendering	MathJax 4.1.0	CDN-loaded with local config
Build System	GitHub Actions	Workflow: `.github/workflows/static.yml`
Version Control	Git	GitHub repository + Wiki

Sources: index.html1-12 .github/workflows/static.yml1

Client-Side Dependencies

Wikinder minimizes external dependencies. The only runtime dependency is MathJax for mathematical formula rendering:

<!-- From index.html -->
<script defer src="/assets/js/mathjax-config.js"></script>
<script defer src="https://cdn.jsdelivr.net/npm/mathjax@4.1.0/startup.js" 
        integrity="sha512-..." crossorigin="anonymous"></script>

Both scripts use defer attribute to avoid blocking page rendering.

Sources: index.html11-12

Metadata Implementation

Every content page implements a four-layer metadata strategy:

Basic HTML Meta Tags: charset, viewport, color-scheme, author
Open Graph Protocol: og:type, og:title, og:url, og:image, og:site_name
Twitter/X Cards: twitter:card
JSON-LD Structured Data: Schema.org Article or WebSite type

This ensures compatibility with browsers, social media platforms, and search engines.

Sources: index.html4-50 Wikinder.html4-52

Project Structure

Directory Layout

/
├── index.html                    # Homepage
├── Wikinder.html                 # About page
├── Math.html                     # Math hub page
├── [content-pages].html          # ~12 additional content pages
├── 404.html                      # Error page
├── sitemap.xml                   # SEO sitemap
├── LICENSE                       # CC BY-SA 4.0 license text
├── README.md                     # Repository documentation
├── vercel.json                   # Vercel configuration
├── .gitignore                    # Git exclusions
├── .github/
│   └── workflows/
│       └── static.yml            # GitHub Actions CI/CD
└── assets/
    ├── css/
    │   └── style.css             # Global stylesheet
    ├── js/
    │   └── mathjax-config.js     # MathJax configuration
    └── images/
        ├── icon.jpg              # Site icon (Open Graph)
        └── favicon.ico           # Browser favicon

Sources: README.md1 index.html9-12 .github/workflows/static.yml1

Page Template Structure

All content pages share a consistent HTML structure:

<!DOCTYPE html>
<html lang="en">
  <head>
    <!-- Meta tags, Open Graph, Twitter Cards, JSON-LD -->
  </head>
  <body>
    <header>
      <nav><!-- Navigation links --></nav>
    </header>
    <main>
      <article>
        <header><!-- Article title and dates --></header>
        <div><!-- Article content --></div>
      </article>
    </main>
    <footer>
      <!-- License notice and edit link -->
    </footer>
  </body>
</html>

Sources: index.html1-96 Wikinder.html1-147

Wikinder maintains presence across 12+ social media platforms:

Platform	Account	Link
Discord	Main + Japan	`discord.gg/bgEXkwxnQp`, `discord.gg/qPE8DyuVw5`
X/Twitter	`@wikinder` + `@wikinderjp`	Global and Japan accounts
Instagram	`@wikindergarten`	Visual content
YouTube	`@wikinder`	Video content
TikTok	`@wikinder`	Short-form video
Bluesky	`wikinder.bsky.social`	Decentralized social
LinkedIn	`company/wikinder`	Professional network
Mastodon	`@wikinder`	Fediverse presence
Facebook	`facebook.com/wikinder`	Social network
Threads	`@wikindergarten`	Meta platform
Scratch	`users/wikinder`	Educational community

Sources: Wikinder.html104-116 index.html72

The homepage (index.html) provides navigation to featured content through a horizontal navigation bar listing recent/important articles. Individual pages link back to the homepage via the header navigation element.

Sources: index.html57-59

SEO Infrastructure

Wikinder implements search engine optimization through:

Sitemap: sitemap.xml listing all URLs with last modification dates
Canonical URLs: Each page declares its canonical URL via <link rel="canonical">
Structured Data: JSON-LD provides rich search results
Semantic HTML: Proper use of <article>, <header>, <time> elements

Sources: sitemap.xml1 index.html14 Wikinder.html10

Development Workflow

The typical workflow for content updates:

Edit: Contributor edits content via GitHub Wiki interface
Commit: Changes are committed to the wiki repository
Trigger: Commit triggers GitHub Actions workflow
Build: Workflow generates static HTML artifacts
Deploy: Artifacts deploy to all four hosting platforms
Live: Changes appear on wikinder.org and mirrors

For detailed information about this workflow, see Content Management Workflow and GitHub Actions Workflow.

Sources: .github/workflows/static.yml1-52 README.md5

Summary

Wikinder is a static educational wiki that combines:

Open Source: GitHub-hosted repository and wiki
Open License: CC BY-SA 4.0 for all content
Resilient Hosting: Four independent platforms
Long-term Preservation: Three archival services
Standards Compliance: HTML5, Open Graph, Schema.org
Collaborative Editing: GitHub Wiki interface
Automated Deployment: GitHub Actions CI/CD

This architecture prioritizes content accessibility, longevity, and collaborative contribution while maintaining technical simplicity through static HTML generation.

Sources: README.md1-19 index.html1-96 Wikinder.html1-147

Overview

What is Wikinder

Core Identity

System Architecture Overview

Content-to-Delivery Pipeline

Repository Structure Mapping

Key Characteristics

Static Site Architecture

Content Source Strategy

Open Licensing Framework

Multi-Platform Deployment

Archival Strategy

Content Categories

Content Type Distribution

Technology Stack

Core Technologies

Client-Side Dependencies

Metadata Implementation

Project Structure

Directory Layout

Page Template Structure

Navigation and Discoverability

Internal Navigation

SEO Infrastructure

Development Workflow

Summary

On this page

Overview

What is Wikinder

Core Identity

System Architecture Overview

Content-to-Delivery Pipeline

Repository Structure Mapping

Key Characteristics

Static Site Architecture

Content Source Strategy

Open Licensing Framework

Multi-Platform Deployment

Archival Strategy

Content Categories

Content Type Distribution

Technology Stack

Core Technologies

Client-Side Dependencies

Metadata Implementation

Project Structure

Directory Layout

Page Template Structure

Social Media Integration

Navigation and Discoverability

Internal Navigation

SEO Infrastructure

Development Workflow

Summary

On this page