Right now RPNow always sends the entire RP to a user when they load the page. This is fine for short to medium-length RP's. But as they get large, there should probably be different behavior.

We might be able to reduce Callback Hell inside of the API code by using a module like co*. It's worth a look.

The rp-view is by far the most complicated monolithic piece of the frontend right now, and could benefit from being split up into different components.

If a user loses connection to the server, it should indicate this somewhere on the page.

I think we could be making more effective use of the Angular-Material themes, so that we don't have to flip between md-hue-2 and md-hue-3 whenever switching between light and dark mode.

We look up an RP by its RPCode pretty often, so it will be a good idea to index these. Right now I'm not sure if it is or not.

What keybindings would be helpful for the RPNow UI?

One possibility: using TAB to open and close the character side-drawer.

Using $scope in AngularJS seems to be discouraged in some circles. Should I refactor it to use the "controller as" syntax?

If the "press enter to send" option is enabled, it should probably also imply "press enter to submit changes."

Especially on mobile, it might be helpful to allow the user to have a larger/smaller font size.

Possibly. But this might have an undesirable effect on mobile. Try it out.

Currently, the server struggles if it receives a very large socket.io message (100MB+). See if Nginx can protect Node from things like that.

We need to make sure no user can brute-force their way into other people's roleplays by guessing URL's.

On medium-sized screens, the title of the RP is not quite centered.

Allow a user to change the name or color of a previously created character. This should affect all messages previously sent with said character.

The old site had a way to read all of the previous RP content online in a paginated format. This new beta site no longer has that functionality; it needs to be added back.

RPNow can't realistically support all browsers; however, we should at least show the user a message instead of a blank page.

We're using a third-party mongodb driver and it might be better to use the official one. Not sure.

Let users add icons for their characters, to give character messages more personality. Probably support multiple icons per character so they can have different expressions, etc.

What if users could share a read-only link to their RP? That way people could share an RP in all its beautiful formatting detail, without having to let those people post to said RP.

Instead of showing a vast, blank space on a newly-created RP page, we should see a helpful message that lets the user know what to do next.

Consider: something as simple as an arrow pointing to the message box on the bottom of the page, saying "Type your first message here!"

The current one requires some hacks to store arrays; let's see if a more advanced one exists.

To incorporate an element of chance into an RP, roll a die! We'll probably want a d20 and a d6, and possibly a coin flip too.

When the browser loads an RP page, it should automatically scroll to view the last-posted RP messages. However, if an image loads, sometimes the page scrolls back up a bit. This is probably because angular's digest cycle doesn't listen for when an image loads, changing the height of the feed.

Right now the new site doesn't have any manual for the user that tells them how to format text.

Right now the RP description is displayed as a tooltip of the header, as well as in the downloaded document. However, neither of these are immediately obvious. We should put it somewhere else too.

The vendor script/style bundles are pretty big; currently, 400kb even after minification and compression. We should make sure that the user sees some kind of "loading" message before these show up.

Right now, RPNow 2 doesn't give a good idea of what the site is for and what it does. Here's some ideas:

• Add an informative video
• ... or a demo gif, like digitalocean does
• What else?

If you've scrolled up above the most recently posted messages, but then you make a post, should the UI automatically scroll down to the bottom? I think the answer is probably yes.

Right now logs are only visible in the output of docker-compose. They should be written to somewhere on the filesystem.

From Tumblr user hiding-from-senpai:

When my keyboard pops up, I can't see or scroll up to view the space where I type the name of the character. (Chrome on Android)

Enforcing a standard on the coding style might be advisable. JS Standard Style is one possible avenue for that.

The message typing box could be improved significantly. Right now, it seems to span the width of the browser, but the actual area where you can type text is smaller. Also, it's strange to have a long, colorful bar go across the whole page. This needs to be improved at some point.

Frontend files should have linting be part of the build process.

Not sure what Nginx is currently doing in terms of caching static assets. Investigate this.

If you open the character side-drawer on a desktop-sized screen, it'll stick open, even after refreshing the page. That's good.

However, the problem is that it appears before the page finishes loading the RP. This shouldn't happen.

• Dockerize RPNow 1
• Merge servers
• Merge frontends
• Create opt-in migration system from the old site
• Fix inevitable bugs
• Migrate the remaining RP's
• Take RPNow 1 offline

How does RPNow handle RP's that are extremely long? I know for a fact that there's a 16MB size limit on a MongoDB document. Add testing to see how it's handled.

The sound and titlebar flashing is cool, but most modern browsers support notifications that show up on the desktop computer's UI. Use this functionality.

HTTPS is expected on the modern web. This should be added, probably with Let's Encrypt.

If a user has disabled JavaScript, we should tell them to enable it.