How davidcarcamo94/liga-herues works
Project Overview
• The repository is focused on handling the plans and lore surrounding the Justice League.
• The resources include various markdown files covering topics such as heroes, villains, cities (ciudades), missions (misiones), completed missions (misiones-completadas), and historical documents (with a dedicated “historia” folder and, for example, a file dedicated to superman).
Defining Main Components
• Following primary category components:
• Heroes (from heroes.md)
• Villains (from villanos.md)
• Cities (from ciudades.md)
• Missions (from misiones.md and misiones-completadas.md)
• History or Background (from the historia directory, including historia/superman.md)
• Optionally, you could include “Additional Documents” or “General Notes” (based on ciudade, ciudades or any other files that seem to capture extra information).
Relationships and Interactions
• “Heroes” and “Villains” to “Missions”: Indicate that both groups are involved in mission planning and execution.
• Link “Cities” to “Missions”: Cities provide the geographical context for where missions occur.
• “History” to “Heroes” (and optionally to the overall plan management): The historical narratives give context to the strategies, character backgrounds, and evolution of the Justice League.
Architectural Patterns/Design Principles
• Although the project is documentation-driven, organizing it into distinct “modules” (i.e., heroes, villains, cities, missions, history) resembles a modular architecture.
• The design emphasis is on clarity and separation of concerns so that each aspect of the Justice League’s planning is clearly delineated.
• That even in a documentation repository the clarity of component interrelations is critical—following a separation between categories helps in understanding the overall plan structure.