Reading Options page

[JohannesSeikowsky]

Kicking off important work on Issue #223.
We really should make it MUCH easier for new users to figure out how to start reading Gutenberg books.

This is a new page that clearly lays out the different options people have for reading. Focus is on clarity, practicality and also brevity (as far as brevity is possible) given peoples' limited attention and patience online.

Essentially trying to make it as straightforward as possible for new users to understand what exactly they can do to start reading our books.

Bibrec also needs work to incorporate something like this. Next stop.

[JohannesSeikowsky]

[JohannesSeikowsky]

[JohannesSeikowsky]

etc

[eshellman]

should we do something with mobile.html?

[eshellman]

could you update your branch from master? thanks

[JohannesSeikowsky]

should we do something with mobile.html?

to be honest, I don't really think so. That page would require a serious amount of editing (it's significantly too wordy) and it may even be a bit confusing to have two pages that cover similar grounds and have essentially the same purpose. As of now mobile.html is still being linked to from "/help/". I'd suggest to either leave it like that or just take the page out.

could you update your branch from master? thanks

I guess you mean to write "from dev"? sure.

[Rowan-McKereghan]

I think this is a good start. I know from experience that even though these instructions seem simple, people (especially older people who tend to use PG) will still get turned around – if there's a way to embed a video walkthrough for kindle, libby, etc. at some point that would be ideal imo

[JohannesSeikowsky]

making it simple/straightforward is really the main thing I tried to do (not very easy to do btw).

I think video walkthroughs are a very good idea!

[eshellman]

This will be a big improvement!!

[eshellman]

When I tried updating the branch to view it with current css, there were merge conflicts.

[JohannesSeikowsky]

hm not sure why that is. Technically this PR is pretty straightforward. Can you resolve the conflicts?

[JohannesSeikowsky]

@eshellman I can't recreate your merge conflicts.

[JohannesSeikowsky]

In fact Github tells me "No conflicts with base branch"
lmk if something needs to be done here, but looks fine to me.

[eshellman]

The problem was that you re-used a branch name. I was unable to test the current, same-named branch until I explicitly deleted the previous branch

[JohannesSeikowsky]

oh I see. sorry - didn't notice.

[JohannesSeikowsky]

all good now?