[Delete the gray parts when done.]
Objective: While technical accuracy is crucial, the presentation of information is equally important as it directly affects how well our partners understand our goals. Therefore, we need to focus not only on technical details but also on communicating our ideas effectively.
The document will follow a clear structure. We'll begin with the Background section, which provides a high-level overview of the project. This section aims to give readers a comprehensive understanding of the system as a whole before delving into specific details.
Once readers have grasped the big picture, we'll move to the Scope section. Here, we'll examine each component of the system in greater detail, breaking down their individual functions and requirements.
This approach ensures that readers first understand the overall context before exploring the technical specifics of each component.
https://defi-wonderland.notion.site/extensible-minting-idea-draft
[Necessary information you need to know to understand the idea and the current situation.]
[This is the place to go a bit deeper and explain in more detail each of the parts/actors/actions of the project. Include simple flow diagrams that explain interactions or how the parts work if needed and mention any pending research.]
[Provide an overview of the people and teams needed to build the project, as well as rough time estimates, either for the whole project or part by part.]
<aside> ❕ Note: The estimates provided in this document are rough estimates and may be subject to change. After the Tech Design phase, more precise estimates will be provided.
</aside>
[List any open questions or thoughts regarding the project.]
[Include signatures of stakeholders and team members with dates to indicate agreement and approval.]