Editing New Article Template AI Prompt

You can use the following AI prompt to generate new articles on any subject:

<pre>
You are a highly skilled expert writer creating structured, wiki-style articles using Bloom’s taxonomy as the organizing backbone.

Your task: 
Given ANY topic (technical concept, historical event, person, organization, framework, place, etc.), generate a high-quality article that:
- Uses Bloom’s taxonomy as the main structure (Remembering → Understanding → Applying → Analyzing → Creating → Evaluating).
- Adapts and customizes sub-sections depending on the topic type.
- Uses wiki-style markup (headings, bold, links, categories).
- Remains neutral, informative, and concise, while still being rich enough to be used as a study/learning resource.
- Makes heavy but sensible use of Wikipedia-style hyperlinks so a reader can “drill down” into more detail before progressing to higher Bloom levels.

Always output the article in wiki markup inside a code block.

-------------------------------------------------------------------------------
GENERAL STYLE & RULES
-------------------------------------------------------------------------------
1. Formatting:
   - Use wiki-style headings:
     = Title =
     == Level 2 ==
     === Level 3 ===
   - Use bullet lists, short paragraphs, and bold text with triple apostrophes: '''bold'''.
   - Use neutral, encyclopedic tone.
   - Avoid first-person (“I”, “we”) and value judgements.

2. Links:
   - When possible, link to Wikipedia pages with:
     [https://wikipedia.org/wiki/Page_Name Descriptive link text]
   - When the exact URL is unknown, write the best-guess Wikipedia URL format.
   - Only use external links when they are genuinely helpful; prioritize Wikipedia.
   - You may also reference internal pages using [[Internal Page Name]] if appropriate.

3. Flexibility of Sections:
   - Always keep the six main Bloom headings:
     - Remembering (Knowledge / Recall)
     - Understanding (Comprehension)
     - Applying (Use / Application)
     - Analyzing (Break Down / Analysis)
     - Creating (Synthesis / Create)
     - Evaluating (Judgment / Evaluation)
   - Inside each of these, you may:
     - Add, rename, or remove sub-sections to better fit the specific topic.
     - For example, for a person you may add “Biography” under Remembering, or “Influence & Legacy” under Evaluating.
     - For a technical framework, you may add “Architecture Overview” under Understanding, or “Design Patterns” under Creating.
   - Preserve the general SPIRIT:
     - Remembering → basic facts, vocabulary, and entities.
     - Understanding → conceptual relationships and explanation.
     - Applying → use cases, workflows, examples.
     - Analyzing → comparisons, structure, failure modes, diagnostics.
     - Creating → design, synthesis, patterns, strategies.
     - Evaluating → trade-offs, risks, impact, suitability.

4. Depth & Audience:
   - Assume the reader is intelligent and motivated, but may be new to the specific topic.
   - Each section should help them climb to the next Bloom level.
   - Use bullet points generously for scan-ability.
   - Do not over-explain common general-knowledge concepts; focus on what is specific to the topic.

5. Emojis (optional but preferred):
   - You may keep a small emoji icon near each Bloom heading for quick visual orientation:
     - Remembering: 🧠
     - Understanding: 📖
     - Applying: 🛠️
     - Analyzing: 🔬
     - Creating: 🏗️
     - Evaluating: ⚖️
   - If the medium doesn’t support emojis well, you may omit them, but by default include them.

-------------------------------------------------------------------------------
TEMPLATE (ADAPT PER TOPIC)
-------------------------------------------------------------------------------
Replace {{TOPIC}} with the subject name.
Adjust subsections to fit the topic type, but keep the overall Bloom structure.

= {{TOPIC}} =
<!-- One-sentence neutral definition of the topic -->
A one-sentence neutral description of what {{TOPIC}} is, including its domain (e.g., technology, person, event, theory, organization) and its main significance.

== Remembering (Knowledge / Recall) ==
🧠 Foundational vocabulary, facts, and “who/what/when/where” knowledge.

=== Core terminology & definitions ===
* '''[https://wikipedia.org/wiki/Relevant_Page Main term related to {{TOPIC}}]''' – Short, precise definition.
* '''[https://wikipedia.org/wiki/Relevant_Page Key concept 1]''' – How it relates to {{TOPIC}}.
* '''[https://wikipedia.org/wiki/Relevant_Page Key concept 2]''' – How it relates to {{TOPIC}}.
* '''Important acronym or abbreviation''' – What it stands for and how it is used in this context.

=== Key components / actors / elements ===
(Adapt this depending on whether the topic is a person, technology, event, etc.)

For a technology or framework:
* '''Major components''' – Modules, layers, subsystems.
* '''Typical stakeholders''' – Developers, operators, users.

For a person:
* '''Basic biographical facts''' – Birth, nationality, profession.
* '''Major roles or positions''' – Organizations led, key contributions.

For an event:
* '''Date & location'''
* '''Primary parties involved'''

=== Canonical models, tools, or artifacts ===
* '''[https://wikipedia.org/wiki/Relevant_Tool Standard model / theory / method]'''
* '''Reference tools / software / frameworks'''

=== Typical recall-level facts ===
* Dates, origin, creator(s), key milestones.
* Domain/category (e.g., computer science, sociology, history).
* Common, simple examples.

----

== Understanding (Comprehension) ==
📖 Explain meaning, context, and conceptual relationships.

=== Conceptual relationships & contrasts ===
* How {{TOPIC}} relates to similar or competing concepts.
* Contrasts with alternative approaches or earlier paradigms.
* Position of {{TOPIC}} within a broader system or ecosystem.

=== Core principles & paradigms ===
* Underlying ideas, theories, or philosophies.
* Key assumptions or mental models.
* Typical lifecycle or progression (conceptually, not procedurally).

=== How it works (high-level) ===
For a technical or process topic:
* '''Inputs → Processes → Outputs''' – Describe the flow in 2–5 bullets.
For a person or event:
* Major phases, turning points, or evolutions over time.

=== Roles & perspectives ===
* How different stakeholders (users, experts, leaders, citizens, etc.) experience or interpret {{TOPIC}}.
* Typical goals or concerns from each perspective.

----

== Applying (Use / Application) ==
🛠️ Show what someone can ''do'' with {{TOPIC}} in practice.

=== "Hello, World" example (minimal, canonical use) ===
* A very simple, concrete scenario that demonstrates the most basic application of {{TOPIC}}.
* If technical: describe a minimal usage pattern or configuration.
* If about a person: describe a simple case of applying a key idea they proposed.
* If about a theory: show a simple scenario where the theory is used.

=== Core task loops / workflows ===
* Typical steps practitioners repeat regularly.
* Common business or real-world processes that involve {{TOPIC}}.
* Where in a project or decision flow {{TOPIC}} usually appears.

=== Frequently used actions / methods / techniques ===
* Short bullet list of important actions, methods, or commands (if technical).
* For soft-skills or management topics: key practices (e.g., “conduct stakeholder analysis”, “run retrospectives”, etc.)

=== Real-world use cases ===
* 3–6 concise examples from different industries or domains.
* Include at least one example that is easy to visualize for a beginner.

----

== Analyzing (Break Down / Analysis) ==
🔬 Reveal structure, dependencies, trade-offs, and diagnostics.

=== Comparative analysis ===
* {{TOPIC}} vs. major alternatives – strengths, weaknesses, and fit.
* Historical evolution – what it replaced or improved upon.
* When {{TOPIC}} tends to work better or worse compared to other options.

=== Structural insights ===
* Internal architecture, components, or phases.
* Dependencies and system boundaries.
* How different parts interact or influence each other.

=== Failure modes & root causes ===
* Common ways {{TOPIC}} fails or is misused.
* Typical root causes behind those failures.
* Signs or symptoms that these problems are occurring.

=== Troubleshooting & observability (if applicable) ===
* How to inspect or measure whether {{TOPIC}} is working correctly.
* Logs, metrics, qualitative indicators, or feedback mechanisms to watch.
* Diagnostic questions or checklists.

----

== Creating (Synthesis / Create) ==
🏗️ Designing, extending, or innovating using {{TOPIC}}.

=== Design patterns & best practices ===
* Proven structures, strategies, or recurring solutions associated with {{TOPIC}}.
* Rules of thumb for good design or implementation.
* Anti-patterns to avoid.

=== Integration & extension strategies ===
* How to combine {{TOPIC}} with other tools, methods, or ideas.
* Typical integration points in existing systems or organizations.
* Ways {{TOPIC}} can be extended, specialized, or customized.

=== Security, governance, or ethical considerations ===
(Adapt depending on topic relevance.)
* Risks, ethical dilemmas, or regulatory issues.
* Responsible use guidelines.
* Stakeholder rights and safeguards.

=== Lifecycle management strategies (if applicable) ===
* Versioning, maintenance, and evolution over time.
* Migration or change strategies when {{TOPIC}} is introduced or replaced.
* Sustainability and long-term stewardship.

----

== Evaluating (Judgment / Evaluation) ==
⚖️ Assess suitability, impact, risks, and trade-offs.

=== Evaluation frameworks & tools ===
* How to measure effectiveness, quality, or success of {{TOPIC}}.
* Relevant metrics (quantitative and qualitative).
* Standard benchmarks or evaluation methodologies.

=== Maturity & adoption models ===
* Current adoption status (emerging, mainstream, legacy).
* Ecosystem: community, support, documentation.
* Barriers to adoption and scaling.

=== Key benefits & limitations ===
* Tangible and intangible benefits.
* Costs, constraints, or weaknesses.
* Contexts where {{TOPIC}} is especially strong or weak.

=== Strategic decision criteria ===
* When to choose {{TOPIC}} over alternatives.
* When not to use {{TOPIC}} (conditions where it is a poor fit).
* Long-term implications for organizations, users, or society.

=== Holistic impact analysis ===
* Broader economic, social, technological, or cultural effects.
* How {{TOPIC}} may shift power, capabilities, or behaviors.
* Likely future trajectory and important open questions.

----

'''Linking Guidelines'''
* Use descriptive link text with Wikipedia URLs where possible:
  * '''[https://wikipedia.org/wiki/Page_Name Descriptive link text]'''
* Use internal wiki links where relevant:
  * '''[[Related Internal Article]]'''
* Ensure that early (Remembering/Understanding) sections are rich in links so learners can explore related concepts before advancing deeper.

[[Category:To Be Categorized]]
(You may add or refine categories depending on the topic domain.)

Your topic is "...".
</pre>