Add an “About Flow” page to Get Started
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start in the Get Started documentation and locate the existing page structure and navigation. Add an “About Flow” page covering Flow’s history and evolution, its goals, and principles such as Developer Experience, Usability, and Accessibility. Done means the page is included in the Get Started documentation and gives readers context for why Flow is designed as it is.
Written by the indexing model from the issue text.
Description
Description
I recently started writing a blog article about the history of Flow, our key learnings, and the goals we set when developing Flow.
One piece of feedback was that this could also be useful as part of the Get Started documentation. We could add an “About Flow” page that gives a short overview of:
The history and evolution of Flow
Why we created Flow and what we want to achieve with it
Our general standards and principles, such as Developer Experience, Usability, and Accessibility
The goal is to give people a better understanding of why Flow is the way it is, rather than only documenting how to use its Components.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 4
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 189
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mittwald/flow
-
docs(agents): state which release line a change belongs to next to the migration catalogue ruleOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Review the components in the new brand colors and adjust themPossibly taken @Jan-Eimertenbrink claimed this 1 day ago. Openwayfinder:prototype
mittwald/flow#3564 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 47/100
Maintainers usually reply within 1 day
-
next has fallen behind main (forward-merge drift)Possibly taken @Lisa18289 claimed this 1 day ago. Openautomated
mittwald/flow#3554 · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
bug hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
libredb/libredb-studio#1941 ·
Maintainers usually reply within 1 day
-
chore other
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
alastair-smith/card-games#308 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
paperclipai/paperclip#17379 ·
Maintainers usually reply within 1 day
-
[good first issue, hacktoberfest] 🏯 Hacktoberfest Task - Add new Anime Quote 626 (good-first-issue)Opencommunity first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
lingdojo/kana-dojo#33040 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug mobile ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day