There's already a mechanism to mark a source as active or inactive. When importing, ignore inactive sources. Print something to the log to indicate they are being ignored.

If you put in a bad login it doesn't do anything. It should say you failed the login.

So you don't have to worry about getting the settings right.

http://serials.orbit.al/#/books/4cfc1580-cf98-445f-9e5e-d20224c62d51

https://twistedcogs.wordpress.com/table-of-contents/

Been trying out the app, pretty neat.

One thing occured to me (correct me if I am wrong), the current flow for bookmark/tracking progress is:

1. click a chapter
2. read
3. go back to webfiction app
4. click next chapter through UI

Many fictions have next/prev chapter links built in (wordpress ones for example), readers are much more likely to click on those instead of clicking back button - and the progress happened this way is lost.

Two ways I can think of to address this:

1. through link's :visited style, however, in all browsers, js have no access to the data, only css does, so cannot do it automatically, still requires user to manually mark all visited chapters as read
2. also bundle a chrome extension with the app, might work like this:

• have a background page/script running to coordinate events across tabs
• when user visit webfiction app, somehow share authentication token with the background script, so it can communicate with app server on its own
• when user click open a chapter from app, inform the background script, indicating a new reading session has started, and keep tracking the opened fiction tab
• run a content-script on page load in fiction/chapter tab, renders prev/next tab button, the content script should know the current chapter link and webfiction id, so are its previous and next chapters' link and id
• clicking these buttons will refresh page navigate to next chapter's link (can be just a <a> tag), also communicating to background page the current chapter is done
• upon receiving the message from content script, background page make a ajax request to webfiction server, with the chapter id provided in the message passed in

tl;dr: use browser extension to render prev/next button on actual fiction chapter's page and communicate to server about reading progress upon clicking them

Users should be able to choose books to place in their library / queue.

Send the user an email when they sign up to confirm their email address. Prereq for #23

Users should be able to sign up and choose books to place in their library / queue.

Only admins or the corresponding user should be able to see user subscriptions and edit user information.

It's not minified right now and it's pushing 2MB. Let's get a production version as part of the deploy process. going so it's not too slow.

See here:
http://serials.orbit.al/#/admin/import-log/500

I think it seems a little weird that the content is floated to the left, it would probably be better if it would be centered.

Are you new to Zurb Foundation?

I'm guessing that in main.js, instead of:

    <div className="row columns small-12" style={background}>
      {this.props.children}
    </div>

you meant something like:

<div className="row">
    <div className="small-12 large-12 columns" style={background}>
      {this.props.children}
    </div>
</div>

I don't know react.js, but I think it supposed to look like that. You can read more here.

We need a way to collect emails if people are interested in knowing when this thing comes out. Not a login, just save their emails so we can keep them in the loop.

We need a static landing page (doesn't load any of the app for speed) that lets people sign up for the site.

• describe what we're doing
• collect emails (or real signups?)
• have pretty pictures
• be awesome

Then we can spam the world saying they can sign up for beta invites, and start releasing them.

Direct them to landing page here? Or on unbounce?

Then get them to sign up.

The admin interface is great, but the end-user experience sucks. Draw out what we're making and do it.

A form to have people suggest a book they don't see.

Our system should scan all sources automatically every 5 minutes.

• Need to improve saving time (right now we're saving everything one at a time)
• Monitors

[email protected] doesn't work as a log in, even though [email protected] is my account email.

Make it responsive, just clean it up a little. Meant to be much easier than #11

I'm getting 401 unauthorized. I created an account: ed72f5c2-66df-4c35-a709-4aa3ff00314f. Admin is set to true.

Also when I click "admin" it goes back to saying Login instead of Hello, Sean. I'm not sure if that's related.

Currently it's pretty confusing, because you can access the admin, and the import-log page, just not the actual import log.

We have too many header items. we need a clean design for our different areas / tabs / login, etc. On small screens things disappear and push content down.

Wildbow gives names to his "Arcs", which consist of about 10 numbered chapters. Right now we only get the chapter numbers, but it would be nice to scan in the names of the arcs as a part of the chapter, or as headings between chapters.

https://parahumans.wordpress.com/table-of-contents/

If subscribed (#19), users should get email notifications when new chapters are added.

Extra: manage notification settings in your profile

Ability to add tags to a source. Search by tags. Or some way to divide the books into useful categories.

It's not running. See the import log. I'm not sure what changed but it seemed to stop working around the time I changed the deploy to work with circle-ci.

Once logged in. System should keep track of which chapter a user is on. Depends on #19

Ability to update email address. Also is a prereq for #23.