-
Notifications
You must be signed in to change notification settings - Fork 490
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
Show an intro to Web UI and IPFS when file browser is empty #818
Comments
Are you using it with Companion? If so, that's why. Companion scopes each app to its own directory. We don't have a way yet to tell Companion that we are WebUI and want access to everything |
We should use this as an opportunity to introduce IPFS and Web UI to new users who have just installed IPFS for the first time. When running in companion we can also add an explanation that the files view is limited to files added via the app. It's not ideal, but we should at least explain the current situation. There is also a proposal to pull the Files page up to the top of the list and make it the default / home page for the app. It's likely to be a new users first expectation (i use IPFS for files, right?) and if the empty state does a good job of explaining what to do next, it'd make for a good new user experience. See: #622 |
Yep, that'd be a start! We should add some info about drag-and-drop support for adding files too. |
First pass at #847 (comment). |
Fixed in #847. |
I have no files in my MFS, I get presented with this page:
Needs a call to action, or at the very least some text saying there's "no files here". At the moment it looks broken.
The text was updated successfully, but these errors were encountered: