Menu

Overview

Relevant source files

Purpose and Scope

The wikinder.github.io repository is a static HTML website that serves as the deployment artifact for wikinder.org. The repository contains pre-generated HTML pages converted from a separate GitHub Wiki which serves as the content authoring environment. This page provides a high-level introduction to the repository's architecture, hosting strategy, and technical characteristics.

For detailed information about specific subsystems:

Scope: This document covers the structure and purpose of the static site repository only. The GitHub Wiki conversion process is external to this repository.

Out of Scope: Wiki-to-HTML conversion mechanisms, GitHub Wiki editing workflows, and content authoring guidelines.

Sources: README.md1-19


Repository Structure and Purpose

The repository follows a zero-build static site architecture, where all HTML files are committed directly to the repository and deployed as-is without server-side processing or build steps. This design choice prioritizes simplicity, portability, and hosting platform independence.

Repository File Organization

Key Characteristics:

AspectImplementation
Build ProcessNone - pre-generated HTML committed directly
Content FormatStatic HTML5 with embedded metadata
Mathematical ContentLaTeX notation rendered client-side via MathJax
InternationalizationURL-encoded filenames for non-ASCII characters
NavigationLink-based, no JavaScript routing
DeploymentDirect file serving from repository root

Sources: index.html1-96 sitemap.xml1-75


Multi-Platform Hosting Strategy

The repository implements a redundant multi-platform hosting architecture where the same static files are deployed to four independent hosting providers simultaneously, plus three archival services for long-term preservation.

Hosting Platform Distribution

Hosting Configuration

PlatformURLPurposeConfiguration
Cloudflare Pageswikinder.orgPrimary domainDNS points to wikindergarten.pages.dev
GitHub Pageswikinder.github.ioMirror + automatic deploymentDeployed via .github/workflows/static.yml
GitLab Pageswikinder.gitlab.ioMirrorManual sync from GitHub
Vercelwikinder.vercel.appMirror + edge optimizationConfigured via vercel.json
Archive.todayarchive.today/wikinder.orgSnapshot preservationManual archiving
Internet Archiveweb.archive.orgHistorical snapshotsAutomatic crawling
Megalodongyo.tcJapanese archivalManual archiving

Redundancy Benefits:

  • High Availability: Site remains accessible if any single platform experiences downtime
  • Geographic Distribution: Different CDN networks optimize for different regions
  • Platform Independence: No vendor lock-in to a single hosting provider
  • Historical Preservation: Archival services ensure content survives even if live site becomes unavailable

Sources: README.md7-18


Content Management Model

The repository follows a bidirectional authoring model where content creation happens in a separate GitHub Wiki, but all pages include edit links back to the source.

Authoring-to-Publication Flow

Key Edit Link Implementation: Every page footer includes this structure:

<footer>
  <p>🧸 Content is available under <a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</a> unless otherwise noted.</p>
  <p>
    <a href="https://github.com/wikinder/wikinder/wiki">Edit this page</a>
  </p>
</footer>

This creates a closed-loop editing workflow where readers can navigate directly to the source for corrections or contributions.

Sources: index.html87-93


Key Technical Characteristics

1. Triple-Redundant Metadata System

Every content page implements three parallel metadata systems for maximum discoverability:

SystemPurposeExample Elements
Open Graph ProtocolSocial media sharing (Facebook, LinkedIn, WhatsApp)og:type, og:title, og:url, og:image, og:site_name
Twitter CardX/Twitter optimizationtwitter:card
Schema.org JSON-LDSearch engine structured data@type: Article, author, datePublished, license
<!-- Example from index.html -->
<meta property="og:type" content="website">
<meta property="og:title" content="Wikinder">
<meta property="og:url" content="https://wikinder.org">
<meta property="og:image" content="https://wikinder.org/assets/images/icon.jpg">
<meta property="og:site_name" content="Wikinder">

<meta name="twitter:card" content="summary">

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Wikinder",
  "url": "https://wikinder.org",
  "license": "https://creativecommons.org/licenses/by-sa/4.0/"
}
</script>

Sources: index.html17-50

2. Bilingual Content Support with URL Encoding

Japanese-language pages use URL-encoded filenames to support non-ASCII characters while maintaining filesystem compatibility:

Japanese TitleEncoded FilenameURL Path
神様という概念%E7%A5%9E%E6%A7%98%E3%81%A8%E3%81%84%E3%81%86%E6%A6%82%E5%BF%B5.html/%E7%A5%9E%E6%A7%98%E3%81%A8%E3%81%84%E3%81%86%E6%A6%82%E5%BF%B5
堕落天使-4%E5%A0%95%E8%90%BD%E5%A4%A9%E2%80%904.html/%E5%A0%95%E8%90%BD%E5%A4%A9%E2%80%904
青空%E9%9D%92%E7%A9%BA.html/%E9%9D%92%E7%A9%BA

This encoding appears consistently in:

Sources: sitemap.xml7-73 index.html57

3. Client-Side Mathematical Rendering

Mathematical content uses LaTeX notation rendered client-side via MathJax 4.1.0:

<!-- MathJax configuration and loading -->
<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-gbKMhIJ85apknSbI7sgedh1H1jUx3LGfWDlhXtj4cLlpN6fPSa/8uuy2CkWSkc105yg2LlWm8a7nL3bautKgpA==" 
        crossorigin="anonymous"></script>

Rendering Strategy:

  • Scripts use defer attribute to avoid blocking HTML parsing
  • LaTeX expressions embedded inline using $ delimiters: $(a + b)^2 = a^2 + 2ab + b^2$
  • Complex expressions progressively enhance visible text

Sources: index.html10-13 index.html73

4. Creative Commons Licensing

All content is licensed under CC BY-SA 4.0 (Creative Commons Attribution-ShareAlike 4.0 International), declared in three locations per page:

  1. HTML <link rel="license"> tag (index.html15)
  2. Footer visible notice (index.html89)
  3. Schema.org JSON-LD license field (index.html35)

This triple-declaration ensures both human and machine readability of licensing terms.

Sources: index.html15 index.html35 index.html89


Technology Stack

Core Technologies

Technology Details

ComponentTechnologyVersion/SourcePurpose
MarkupHTML5-Semantic structure with <article>, <header>, <main>, <footer>
StylingCSS/assets/css/style.cssGlobal typography (Palatino) and layout
Math RenderingMathJax4.1.0 (jsDelivr CDN)Client-side LaTeX → HTML+CSS conversion
Math ConfigurationJavaScript/assets/js/mathjax-config.jsCustom $ delimiters, AMS package
DeploymentGitHub Actionsactions/checkout@v4, actions/deploy-pages@v4Automated static site deployment
Vercel ConfigJSONvercel.jsoncleanUrls: true, trailingSlash: false
Site IndexXMLsitemap.xml18 URLs with lastmod timestamps
ImagesJPEGicon.jpg, favicon.icoSite branding in metadata and browser

Sources: index.html9-12 README.md1-19


Content Organization

Content Categories and Distribution

The repository contains 18 indexed content pages organized into five thematic categories:

Content Statistics

CategoryPage CountExample Pages
Mathematics6Math.html, Math-formulas.html, Counting-bears.html
Music & Cultural2Music-notation-on-computers.html, Chinese-characters-with-the-most-strokes.html
Organizational4Wikinder.html, Wikinder-Japan.html, bear.html, yuuki.html
Japanese Content5神様という概念.html, 堕落天使-4.html, 青空.html
Other1Anemone.html
Total18(excluding index.html and 404.html)

Navigation Pattern: The landing page (index.html) provides a horizontal navigation bar linking to all major pages, enabling one-click access to any content from the homepage.

Sources: sitemap.xml1-75 index.html57


Summary

The wikinder.github.io repository is a pre-built static HTML website that prioritizes:

  1. Availability: Four hosting platforms + three archival services ensure 24/7 accessibility
  2. Discoverability: Triple-redundant metadata (OG, Twitter Card, Schema.org) optimizes social sharing and search ranking
  3. Editability: Bidirectional workflow with GitHub Wiki via edit links on every page
  4. Internationalization: URL-encoded Japanese content alongside English pages
  5. Performance: Zero-build deployment, deferred JavaScript loading, CDN-hosted libraries
  6. Licensing: Clear CC BY-SA 4.0 licensing in machine and human-readable formats

The architecture separates content authoring (GitHub Wiki) from content publication (this repository), enabling non-technical contributors to edit content while maintaining full control over the deployed HTML structure.

For implementation details of specific subsystems, see the child pages in sections 2 through 10.

Sources: index.html1-96 sitemap.xml1-75 README.md1-19