New Article Template

From BloomWiki
Jump to navigation Jump to search

ARTICLE TITLE[edit]

Remembering (Knowledge / Recall)[edit]

🧠 List the foundational vocabulary and factual knowledge an expert should be able to recall.

  • Core terminology & definitions
    • Term 1 – Replace this link with the topic's actual Wikipedia article later.
    • Term 2 – Short, precise definition.
    • Term 3 – Key acronym, role, object, protocol, etc.


  • Where this topic commonly appears
    • Industries, fields, workflows, real-world environments.
  • Typical recall-level facts
    • Year introduced, creator/vendor, category, major versions.

Understanding (Comprehension)[edit]

📖 Explain what the topic means, how it works conceptually, and how it relates to similar ideas.

  • Conceptual relationships & contrasts
    • Topic vs. alternative approach — key differences.
    • Topic inside a broader system or ecosystem.
  • Core principles & paradigms
    • Foundational theory, learning model, architectural mindset.
  • How it works (high-level)
    • Inputs → processes → outputs.
  • Roles & perspectives
    • Builder, operator, stakeholder, end user.

Applying (Use / Application)[edit]

🛠️ Show what someone can *do* with the topic.

  • "Hello, World" example
    • Minimal, canonical starter use case.
  • Core task loops
    • Regular workflows, processes, or procedures.
  • Frequently used commands / functions / actions
    • Short reference list.
  • Real-world use cases
    • Common applications, industries, or problems solved.

Analyzing (Break Down / Analysis)[edit]

🔬 Demonstrate expert-level structural understanding and diagnostic reasoning.

  • Comparative analysis
    • Topic vs. competing tools, methods, or systems.
  • Failure modes & root causes
    • What commonly goes wrong and why.
  • Troubleshooting & observability techniques
    • Logs, metrics, debugging steps.
  • Structural insights
    • Dependencies, internal architecture, system boundaries.

Creating (Synthesis / Create)[edit]

🏗️ Demonstrate designing or building with the topic.

  • Design patterns & best practices
    • Proven solutions or recommended structures.
  • Security, governance, or ethical considerations
  • Lifecycle management strategies
    • Versioning, migrations, backward compatibility.
  • Scalability & optimization patterns

Evaluating (Judgment / Evaluation)[edit]

⚖️ Assessing suitability, trade-offs, risks, or long-term value.

  • Evaluation frameworks & tools
    • How to measure effectiveness, reliability, quality.
  • Maturity & adoption models
    • Ecosystem stability, documentation, community size.
  • Key performance indicators
    • Quantitative or qualitative success measures.
  • Strategic decision criteria
    • When to use this topic — and when not to.
  • Holistic impact analysis
    • Cost, maintainability, learning curve, governance, risks.

Linking Guidelines

  • Replace all placeholder external links with Wikipedia links when available.
  • Use the format: `Descriptive link text`
  • Internal wiki pages use double brackets: `Article Name`