UI is a priority for our first version.
For the transliterations / translations, quran.com offers a good example of juxtaposing word-by-word definitions. We might draw inspiration from these sources so that the user doesn't have to manually match transliteration meanings to the actual source.
Helping words...
Where we collectively investigate and interrogate the problem space and iteratively scope our approach.
Breakdown to landmarks that communicate shared context we are working towards through 2-tiered task list, CRUD list elements as development unfolds.
Strike the scope of code that reveals the most about the problem/solution FIRST not necessarily the easiest or hardest parts
```
- [ ] Parent Task
- [ ] Child Task
- [ ] Child Task
- [ ] Parent Task
- [ ] Child Task
- [ ] Child Task
```
---
Groundwork
Helping words...
Introduce us to the problem space. Write out what you already know about the terrain you are the recce commander enriching us with details beyond the fog of war.
Where have you tried applying and encountered difficulties?
How have others attempted to scale or explore these challenges?
(Embed internal & external links to related or possible paths of exploration, stackoverflow, documentation, github etc)
Who should be notified?
Emphasis on previous or current practice to discover what is ugly, missing, or unnecessary.
```
INPUT UR ANSWER HERE
```
---
Reflection
Helping words...
Where the eternal wheel returns back to practice and what we finally implemented is to be outlined. You are the historian or archivist bringing clarity to future-yous and us about your foray.
Emphasis on approaching timeless solutions for well-defined problem space through distillation by decanting that which is un-needed and abstracting that which is essential to approaching the problem space.
Add any reflections and internal links to future potential and blindsides.
```
INPUT UR ANSWER HERE
```
Present Context
UI is a priority for our first version. For the transliterations / translations, quran.com offers a good example of juxtaposing word-by-word definitions. We might draw inspiration from these sources so that the user doesn't have to manually match transliteration meanings to the actual source.
Helping words...
Where we collectively investigate and interrogate the problem space and iteratively scope our approach. Breakdown to landmarks that communicate shared context we are working towards through 2-tiered task list, CRUD list elements as development unfolds. Strike the scope of code that reveals the most about the problem/solution FIRST not necessarily the easiest or hardest parts ``` - [ ] Parent Task - [ ] Child Task - [ ] Child Task - [ ] Parent Task - [ ] Child Task - [ ] Child Task ``` ---Groundwork
Helping words...
Introduce us to the problem space. Write out what you already know about the terrain you are the recce commander enriching us with details beyond the fog of war. Where have you tried applying and encountered difficulties? How have others attempted to scale or explore these challenges? (Embed internal & external links to related or possible paths of exploration, stackoverflow, documentation, github etc) Who should be notified? Emphasis on previous or current practice to discover what is ugly, missing, or unnecessary. ``` INPUT UR ANSWER HERE ``` ---Reflection
Helping words...
Where the eternal wheel returns back to practice and what we finally implemented is to be outlined. You are the historian or archivist bringing clarity to future-yous and us about your foray. Emphasis on approaching timeless solutions for well-defined problem space through distillation by decanting that which is un-needed and abstracting that which is essential to approaching the problem space. Add any reflections and internal links to future potential and blindsides. ``` INPUT UR ANSWER HERE ```