Currently the hypha.app main page has a “Documentation” link that links to hypha-docs on github.
I know the plan is to eventually have Gitbook as the main place where the documentation lives–should we change the link now, or wait (and if wait, until what conditions have been met)?
@frjo, thoughts?
As soon as there is something else to link to I think it should be changed.
You should now also have access to GitHub - HyphaApp/hypha-site: The Hypha site.. The front page source is at hypha-site/_index.md at b53d90c73dd2df1f87592c064b4107782e1c7511 · HyphaApp/hypha-site · GitHub.
Any changes to that file will trigger an automatic deploy of the site. New content should be visible at https://www.hypha.app/ within a few minuts.
When needed we can add Forestry.io to get a nicer editing environment.
The site is as bare bones as it gets so any ideas to make it nice is more than welcomed.
The site https://www.hypha.app/ uses the exact same setup, tools and base theme as https://www.appg.tech/.
The later has had the help of a designer as can be easily seen.
Do we want the hypha site index page to be the same as the hypha docs index page?
There is a lot of overlap, but the site index page has more info.
Maybe the documentation index page should have even less of the “general” info it has now, and be more documentation-oriented.
Thoughts? (@blah, @maxpearl, @bernard). What makes the most sense for users navigating to the documentation for the first time?
Please create a new topic for this, it’s a separate and important discussion.
We also have the repo README that should be part of the discussion.
No they should be different, they serve different purposes.
The user of the docs.hypha site will primarily be an adopter, therefore it needs to meet their needs first.
The hypha.app site could be used by anyone, therefore it needs to be a higher-level introduction to what Hypha is, what it does, etc.
Right now the hypha.app site is a 1 page static site, very simple.
I’ve created a site-map to map the information architecture of both sites.
@emlini if you create a miro account I can give you edit access.
Maybe the documentation index page should have even less of the “general” info it has now, and be more documentation-oriented.
Agreed.
What makes the most sense for users navigating to the documentation for the first time?
The documentation site should focus on Hypha documentation, with a short introduction para to give context to people who might find themselves there - “this is the documentation site for Hypha, the submission management platform for open funding calls…etc” - with a link to the hypha.app site.
In terms of the documentation structure, I’m not 100% but I’m sure you’ve got ideas! 
We already have a Github issue to for the hypha.app website: [Meta] Create Hypha product website · Issue #2164 · HyphaApp/hypha · GitHub
@emlini I’ve added a section called “Getting started with Hypha” and specifically linked to docs.hypha.app