-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix numbering on Low-income Basic Flow #1912
Comments
@thekaveman I can see how you read the diagram and the basic flow together, but my intent was for each to have a distinct purpose.
Including the step to choose a transit agency, for example, is too granular for the diagram as that's a UI interaction. Step 5 in the flow is brief and covers several backend calls and responses in the diagram. Thus, I see them as complementary and don't believe they have to align verbatim. If we want to make it more clear that they are distinct, I propose adding a header to the diagram that reads something like Technical Architecture and moving the the Basic Flow header above the sequence. |
@indexing I follow you. I think I was tripped up mostly on the numbering on the flow chart, especially since the other flow charts do not have numbering. Should we be consistent here (one way or the other)? |
@thekaveman For me, the numbering in the chart is a helpful affordance to understand the process as a sequence and the numbering makes it a bit easier to step through the phases when scanning. I do note the numbering is new in this diagram; I propose adding it to the others (which I will do). Any objections? Maybe add this as a task in #1812 ? |
Closing as this is being tracked in #1812. |
The chart shows
11
steps:But the list only has
9
steps:Expected behavior
The chart is (correctly) showing all steps in the process, while the list presents a more plain-language (and still correct) version of the process. Suggest removing the numbering from the chart (other flow charts do not have numbering) to avoid confusion.
The text was updated successfully, but these errors were encountered: