-
-
Notifications
You must be signed in to change notification settings - Fork 736
Pybee.org 3.0 redesign
Philip James edited this page Oct 29, 2017
·
2 revisions
In discussions with various people, it's become clear that one of the biggest impediments to progress for BeeWare (especially on the funding front) is our project homepage. It's complex, and doesn't clearly explain the project's purpose. Here's a grab-bag of things we need to capture for a "PyBee.org 3.0" redesign.
- Better articulate the aim of the project
- Revisit the "IDEs of Python" tagline
- Provide a better "roadmap" to show how all the pieces fit together
- "What will BeeWare enable me to do?"
- "Who else is using BeeWare, and for what?"
- right now, the answer pretty much nobody, because it's early alpha - but we need to communicate this
- Provide a better out-of-box experience
- "I want to try BeeWare - what should I do?"
- Toga tutorial? Briefcase tutorial? What is the "Beeware tutorial"?
- "I want to try BeeWare - what should I do?"
- Clarify the call to action of the home page
- Subscribe to mailing list
- Join as a member
- Contribute code
- Experienced developer, just show me the code and what you want me to do
- Complete first timer (doesn't know git, ...)
- Better articulate why people should donate financially
- Possibly different landing pages for different user types:
- Python developer
- Technical, but non-developer with app needs
- Manager with control of funds
- Potential investors?
- Possibly different landing pages for different user types:
- Use this relaunch as an opportunity to formally rename as BeeWare (beeware.org, etc)
- Look at how we could use adwords and other promotion mechanisms to spend a little cash to drive people outside the "friends and followers" demographic to sign up, learn about BeeWare, etc.
Comments from @phildini:
- right now navigation is super tricky. Even if the content itself doesn't change, the organization should.