-
-
Notifications
You must be signed in to change notification settings - Fork 813
Move Success stories to website #762
Copy link
Copy link
Open
Labels
documentationAn improvement required in the project's documentation.An improvement required in the project's documentation.enhancementNew features, or improvements to existing features.New features, or improvements to existing features.good first issueIs this your first time contributing? This could be a good place to start!Is this your first time contributing? This could be a good place to start!
Metadata
Metadata
Assignees
Labels
documentationAn improvement required in the project's documentation.An improvement required in the project's documentation.enhancementNew features, or improvements to existing features.New features, or improvements to existing features.good first issueIs this your first time contributing? This could be a good place to start!Is this your first time contributing? This could be a good place to start!
What is the problem or limitation you are having?
I started to proofread the success stories, then I thought... Why not reformat this to make it more consistent and informative?
Describe the solution you'd like
I'm envisioning a table, listing the same info for each app:
Also, we currently have one page for Briefcase and one for Toga; they have some apps in common and some unique, and there's no mechanism to sync these. Considering how often people ask about examples, I think it might make more sense to put one combined page on the main site, and potentially link to it from both docs. It would also then make sense, I imagine, to add a column for "BeeWare component(s) used".
Describe alternatives you've considered
We could still maintain separate pages, but I'm not sure if there's a good way to make sure they stay in sync with each other. It's also not clear, currently, from just looking at one, which of the apps also use the other.
If we do keep the individual pages, it seems redundant to mention that each app uses the tech in question.
Additional context
No response