The Wiki

From CreatorSpace Wiki Demo
Jump to navigation Jump to search

The Wiki
Status Review
Lead Wiki Steward
Rooms All rooms
Skills Documentation; governance; safety review; training
Proof of concept. This page is sample content for the CreatorSpace Wiki POC. It does not represent approved CreatorSpace policy, verified equipment instructions, or real member data.

The Wiki

The live public wiki is at wiki.creatorspace.org. This POC keeps that spirit but adds structure: pages should be discoverable, owned, categorized, editable with forms, and clear about review status.

Direction

The wiki should become the public operating memory of CreatorSpace: what spaces exist, what each room contains, who stewards it, what training is needed, what supplies are available, what policies apply, and where members can find or share finished work.

The long-term direction is:

  • Keep public, durable knowledge in the wiki.
  • Keep private member records, access codes, finances, incidents, and credentials out of public pages.
  • Use forms and templates so pages can be queried instead of only browsed.
  • Use Slack identity for login and role mapping when SSO is ready.
  • Give every safety or equipment page a named steward or role owner.

Standards

  • Every person with a login should have a wiki user id that matches their Slack id or the agreed Slack-derived account name.
  • Roles, not individual one-off exceptions, should manage permissions wherever possible.
  • Every page except the home page and special pages should belong to at least one category.
  • Every normal content page should use a template that has a Page Forms form, or should be marked as a migration exception until the right template exists.
  • Every room, equipment, training, policy, and how-to page should make the responsible person or steward role clear.
  • Safety instructions, machine settings, access rules, and policies stay in "Review" until a steward approves them.
  • The wiki should link to source systems instead of copying secrets, private files, accounting data, or member-only records.
  • Page titles should be stable enough for QR codes, signage, and printed labels.

Other Makerspace Wikis To Reference

Wiki Strong suite What CreatorSpace can borrow
CreatorSpace live wiki Current public navigation, disciplines, stewards, and official starting point. Treat it as the source to reorganize, not something to replace blindly.
London Hackspace Wiki Deep equipment directory across many workshop areas. Equipment pages, area indexes, and long-lived tool records.
Makespace Wiki Clear split between equipment, training, and room operations. Training-required equipment model and member-facing safety notes.
Bristol Hackspace Wiki Tool and room inventories organized by workshop area. Simple area pages that link directly to tools and orientation content.
Nottinghack Wiki Practical tool lists, policies, and member operations. Everyday operational documentation and governance examples.
Noisebridge Wiki Culture, norms, meetings, and community process. Lightweight governance and community memory patterns.
Hackerspaces.org Wiki Cross-space directory and hackerspace patterns. Reference examples for space setup, governance, and comparative research.

Extensions Currently In This POC

Extension Benefit
PageForms Form-based editing for room, equipment, people, project, training, and task pages.
Cargo Queryable tables for directories, dashboards, review queues, and cross-links.
TemplateStyles Page-local CSS for clean cards, dashboards, and room layouts.
TemplateData Template metadata for better editing and future documentation.
ParserFunctions Conditional and utility logic in templates.
VisualEditor WYSIWYG editing for regular pages.
WikiEditor Better source editor for users who prefer wikitext.
ApprovedRevs Review boundary for policy and safety-sensitive pages.
Cite Citations and references for source-backed documentation.
CodeEditor and SyntaxHighlight Better editing and rendering for code, configuration, and snippets.
Linter Finds broken markup before it becomes maintenance debt.
DiscussionTools and Echo Better on-wiki discussions and notifications.
CategoryTree Easier browsing of category structure.
ImageMap, MultimediaViewer, PdfHandler Better handling of images, maps, media, and PDFs.
Interwiki, Scribunto, MobileFrontend, Nuke Link management, Lua module support, mobile skin support, and admin cleanup tools.

Form Editing Status

The Page Forms free-text areas are configured with editor=visualeditor, class=toolbarOnTop, and a taller editor height so room, people, and equipment pages can use a WYSIWYG editor for narrative notes. Page Forms supports this setup when VisualEditor is installed and VEForAll is present on the server.

Extensions To Consider

Extension or feature Why consider it
VEForAll Required for VisualEditor/WYSIWYG editing inside Page Forms textarea and free-text inputs.
PluggableAuth plus OpenID Connect Slack or identity-provider login with account linking.
LDAPProvider or another directory bridge Future member-directory integration if CreatorSpace centralizes identity outside Slack.
CirrusSearch and Elastica Much better search once the wiki has hundreds of equipment, policy, and how-to pages.
Maps Room maps, area diagrams, and location-aware pages if floor-plan work grows.
Mermaid or GraphViz support Process diagrams for onboarding, maintenance, approvals, and project workflows.
MsUpload or UploadWizard Easier photo upload for stewards documenting rooms and equipment.
Lockdown or Namespace-specific access control Only if private wiki areas are added; public pages should stay public by default.
ReplaceText Batch renames and cleanup during migration.

What Belongs Here

Put it in the wiki Put it somewhere else
Public room guides, equipment pages, training routes, approved policies, how-to guides, public steward roles, public showcase pages, public project notes, supply lists, and documentation tasks. Slack discussions, quick coordination, private messages, unfinished arguments, access codes, member billing, donation receipts, private contact details, incident reports, sensitive photos, and credentials.
Stable links for QR codes, labels, signs, and onboarding packets. Source code, scripts, and deployable applications belong in GitLab, with wiki pages linking to them.
Public summaries of board-approved policy. Draft board deliberation, financial records, legal documents, and HR-like records belong in the approved private systems.

Organization Plan

  • Front page: clean navigation and current priority paths.
  • Room pages: access, steward, equipment, training, supplies, map/photo references, and review status.
  • Equipment pages: stable ID, model, room, training, steward, status, manuals, videos, maintenance, approved materials, and safe-use boundaries.
  • Training pages: prerequisites, outcomes, signoff owner, equipment covered, and review cadence.
  • Policy pages: owner, approved status, source decision, effective date, and review date.
  • People pages: opt-in public information only, with skills, projects, and how-to links.
  • Tasks: review queue items with owner, blocker, next action, and done-means checklist.

Migration Plan

  1. Mirror high-value live wiki pages into structured pages.
  2. Add real photos and exact equipment IDs.
  3. Replace "Review" placeholders with steward-approved facts.
  4. Connect Slack login to wiki accounts and roles.
  5. Create a short steward workflow for approving page changes.
  6. Add QR codes to rooms and equipment once page titles are stable.