Overview

Relevant source files

• .github/workflows/static.yml
• README.md
• Wikinder.html

Purpose and Scope

This document provides a high-level introduction to the Wikinder project, a GitHub-based wiki system that converts content from a GitHub Wiki repository into static HTML pages and deploys them to multiple hosting platforms simultaneously. Wikinder focuses primarily on mathematical and educational content, implementing comprehensive metadata standards, MathJax-based mathematical rendering, and a multi-platform redundancy strategy for high availability.

For detailed information about specific subsystems, see:

• System architecture details: System Architecture
• Content organization patterns: Content Organization
• Deployment pipeline specifics: Deployment System
• Individual content types: Content Pages
• Client-side functionality: Client-Side Systems
• Asset management: Assets & Configuration
• Legal framework: Licensing & Collaboration

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

System Architecture Overview

Wikinder operates as a static site generator with automated deployment and multi-platform hosting. Content originates in a GitHub Wiki repository, is converted to static HTML files stored in the wikinder/wikinder.github.io repository, and is automatically deployed to four independent hosting platforms through GitHub Actions.

Complete System Flow

Sources: .github/workflows/static.yml1-44 README.md7-18

Core Components

Source Repository: wikinder.github.io

The wikinder.github.io repository serves as the canonical source for all deployed content. It contains:

Component	Location	Purpose
HTML articles	Root directory	Individual content pages (e.g., Wikinder.html, Math.html)
Deployment workflow	.github/workflows/static.yml	Automated deployment configuration
CSS stylesheet	/assets/css/style.css	Global typography and layout rules
JavaScript configuration	/assets/js/mathjax-config.js	MathJax rendering setup
Site icon	/assets/images/icon.jpg	Branding and Open Graph image
License	LICENSE	CC BY-SA 4.0 legal text
Documentation	README.md	Hosting URLs and archive links

Sources: README.md1-19 Wikinder.html9-11

Deployment Workflow: static.yml

The deployment process is managed by a GitHub Actions workflow named "Deploy static content to Pages":

The workflow configuration includes:

• Triggers: Push to main branch or manual dispatch (static.yml4-10)
• Permissions: Read contents, write pages, write id-token (static.yml13-16)
• Concurrency control: Single deployment group, no cancellation of in-progress runs (static.yml20-22)
• Artifact upload: Entire repository (.) is packaged (static.yml39-40)

Sources: .github/workflows/static.yml1-44

Hosting Infrastructure

Wikinder implements a four-platform hosting strategy:

Platform	URL	Primary Role
Cloudflare Pages	wikindergarten.pages.dev	Primary (domain points here)
GitHub Pages	wikinder.github.io	Secondary
GitLab Pages	wikinder.gitlab.io	Tertiary (read-only)
Vercel	wikinder.vercel.app	Quaternary

All platforms serve identical content and are capable of responding to the wikinder.org domain, providing redundancy against platform-specific outages.

Sources: README.md7-12

Archival System

Three independent web archiving services maintain historical snapshots:

1. Archive.today - archive.today/wikinder.org
2. Internet Archive - web.archive.org/web/*/wikinder.org*
3. Megalodon - gyo.tc/https

This multi-service approach ensures long-term content preservation even if individual services become unavailable.

Sources: README.md14-18

Content Structure

HTML Article Template

Every article follows a consistent HTML5 structure with comprehensive metadata:

Example from Wikinder.html:

• Meta tags: Wikinder.html4-24
• Structured data: Wikinder.html26-51
• Body structure: Wikinder.html54-146

Sources: Wikinder.html1-147

Navigation and Linking

The site implements wiki-style internal navigation:

• Header navigation: Links to homepage at / (Wikinder.html57-62)
• Internal article links: Class internal present for existing pages (Wikinder.html78)
• Edit links: Footer links to GitHub Wiki source (Wikinder.html142)

Sources: Wikinder.html57-142

Technical Characteristics

Static Site Generation

Wikinder operates entirely as static HTML with no server-side processing:

Characteristic	Implementation
Content format	Pre-rendered HTML files
Dynamic features	Client-side JavaScript only (MathJax)
Data storage	None (all content in HTML)
Build process	Manual conversion from GitHub Wiki
Deployment	Static file upload via GitHub Actions

Mathematical Content Support

Mathematical expressions are rendered client-side using MathJax:

1. Local configuration file: /assets/js/mathjax-config.js sets up Euler font and inline delimiters
2. External library: MathJax 4.0.0 loaded from cdn.jsdelivr.net
3. LaTeX syntax: Mathematical notation written in LaTeX format within HTML

Sources: README.md5 Wikinder.html9

Metadata and SEO

Each article implements four parallel metadata systems:

1. Basic HTML meta tags - Browser compatibility and viewport configuration
2. Open Graph Protocol - Social media preview cards (Facebook, LinkedIn)
3. X/Twitter Cards - Twitter-specific preview format
4. Schema.org JSON-LD - Structured data for search engines

This redundant approach ensures optimal presentation across all platforms and search contexts.

Sources: Wikinder.html4-51

Licensing Framework

All content operates under CC BY-SA 4.0:

Sources: Wikinder.html11-140

Project Metadata

Property	Value
Founder	bear (Wikinder.html84)
Founding date	September 1, 2005 (Wikinder.html88)
Primary wiki host	GitHub (Wikinder.html96)
Secondary wiki host	GitLab (read-only) (Wikinder.html98)
License	CC BY-SA 4.0
Primary author	yuuki (Wikinder.html12)

Sources: Wikinder.html80-99