Skip to content
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

Create Help Page #51

Closed
dignifiedquire opened this issue Oct 6, 2015 · 11 comments
Closed

Create Help Page #51

dignifiedquire opened this issue Oct 6, 2015 · 11 comments

Comments

@dignifiedquire
Copy link
Member

There should be some form of help/documentation page inside the app, so people can understand what the app is doing and how to use it.

@RichardLitt
Copy link
Member

@dignifiedquire: @RichardLitt: yes it would be great to get some help on that, my idea was to do the setup once the PR is merged, as it has been long running enough for now, but if you want to start writing content in markdown format that would be great

Sweet!

@daviddias daviddias modified the milestone: 1.0.0 Oct 12, 2015
@dignifiedquire
Copy link
Member Author

  • Sync from ipns when available
  • Ship initial version so it's always available

@dignifiedquire
Copy link
Member Author

  1. Create a directory called docs
  2. Create a window that renders those docs using a markdown renderer inside a nice help window
  3. Add ipfs sync capabilities to allow auto updates of those docs

@daviddias daviddias removed this from the 1.0.0 milestone Nov 22, 2017
@hacdias
Copy link
Member

hacdias commented Dec 30, 2017

@diasdavid is this supposed to be done? If so, what should this Help page contain?

@daviddias
Copy link
Member

daviddias commented Dec 30, 2017

This is a really old proposal (Oct 2015). Yes, docs are great but even greater is making sure that the IPFS GUI is cohesive so that part of the documentation is just UX.

Think about what can be done to improve, but avoid spending dozens of hours, if you feel like you need dozens of hours to make docs great, then think about UX of station+companion+webui first.

@RichardLitt
Copy link
Member

so that part of the documentation is just UX.

A 30 sentence document will help developers understand what this is enough to be able to contribute and will go further towards collaboration and scaffolding this out faster than depending on the UX of the GUI. I'd say take a stab at it, @hacdias.

@hacdias
Copy link
Member

hacdias commented Dec 30, 2017

Oh, I thought this was more about a end-user help page. For devs, we already started writing some stuff: https://github.com/ipfs-shipyard/ipfs-station#file-structure

@RichardLitt
Copy link
Member

Ah, word. Yeah. In that case, David is probably right. Some basic text may help, though. The most use might be gotten out of drawing up some wireframes or user flows, and then implementing them in the GUI.

@daviddias
Copy link
Member

In any case, @hacdias already did some valuable work to fulfil the need you described, @RichardLitt , check it out here https://github.com/ipfs-shipyard/ipfs-station#file-structure

@hacdias
Copy link
Member

hacdias commented Dec 30, 2017

Should we close this?

@hacdias
Copy link
Member

hacdias commented Feb 16, 2019

After more than I year, let's close this. The README contains information about how the app works. Now, IPFS Desktop is a relatively simple app and doesn't seem to need 'help'/how-to-use info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants