-
Notifications
You must be signed in to change notification settings - Fork 327
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
Landing pages flow & content #564
Comments
I like the split screen idea, looks different than usual landing page and keeps user engaged. 👍 Some Ideas for left pane
Unsure where to put
Some ideas for content for the right pane
|
The ideas for the left pane sound pretty good. I think the animation from ipfs.io is far too soft, I bet it gets unnoticed by most of the people. I think if the IPFS logo gets the heartbeat animation it will be sufficient, I'll probably add that and see how it goes. The right pane looks good too, I'll try find a way to make that look clean but attention drawing. As you said in another thread, less is more, we want to keep this page uncluttered but draw the user to learn more and follow some links. Thanks for the feedback @lidel! |
Released to beta channel v2.5.0.11550 🎊 🚀 |
Hey @ipfs-shipyard/gui!
As we talked in the GUI & In Web Browsers Sync, we need to define the flow and content of the landing pages for Companion.
Welcome Page
After the extension is installed, the user would be presented with a page that showed something like a thank you message for installing Companion, and also checked if a node is already running, giving simple instructions how to run one if not. We could have some links about the dweb and some IPFS resources.
I think a split screen layout would work great for this:

In the left side we would have the Companion related thank you message and node checks, in the right side we would have the links to resources or other apps.
The content is key and it will help with the design, so I'm asking you for some feedback about what should be present here.
References
The text was updated successfully, but these errors were encountered: