Tonight I started working on the UI improvements requested by the users, primarily around scrolling and instructions text. Originally, I wanted the text field to be plain HTML, but now I want to have semantic meaning to the different parts; summary, details on rules, and flavor text. In the process, I learned some interesting things:
- CDATA in XML is helpful for rendering HTML out of XML
- details semantic HTML5 tag, which auto collapses. Found this on accident because my xml tag is named details
- window.scrollTo(0,0) is a javascript function to scroll to top.
I'm actually proud of my solution to scrolling. People didn't want to scroll up to check results, then back down. Also, one player mentioned it was hard to tell when the room changed. I didn't want to get rid of the cool pictures, so I used them to my advantage. When the page scrolls to the top automatically on room reload, it will show most of the picture, visually signalling a new room has arrived.
I added a few things to my previous todo list for the show HN, namely bots. I also might want to revisit powers again sometime soon, but not for now.
In June I'm going to do a game jam and take a break from this, so July will be when I will do the show hn.
For playtest this weekend:
- Room writing instructions.
For the show hn:
- polish website?
- bots. this will be helpful to get people to try the game before convincing their friends to join.
- create a real docker build. I've been putting this off for a while and using my quick and dirty image, but I'll need an image with deterministic builds from a svn revision/branch with a database in a volume. This will probably also include some minor tools fixes to support the new build.
- db backups, dr. For the short term, this is just being able to grab it somewhere on the filesystem and copy somewhere else on the filesystem. For a production server I'd store the db backup offsite but that's not necessary for the staging build
- monitoring, metrics, alerting. I need to be able to see how well the app is performing. I doubt the show hn will blow up (most shows have like 2 upvotes) but if it does I'll want to know whats wrong. The UI is pretty inefficient, and I know the DB code does WAY too many queries for simple operations.
- lock down dev and tools dir. cannot forget to do this, but it should be covered in the new docker build.
- https. pretty simple, just adding a letsencrypt cert to the server and connecting to pound
2 hours
Last edit: dungeonsoffear 2021-05-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tonight I started working on the UI improvements requested by the users, primarily around scrolling and instructions text. Originally, I wanted the text field to be plain HTML, but now I want to have semantic meaning to the different parts; summary, details on rules, and flavor text. In the process, I learned some interesting things:
- CDATA in XML is helpful for rendering HTML out of XML
- details semantic HTML5 tag, which auto collapses. Found this on accident because my xml tag is named details
- window.scrollTo(0,0) is a javascript function to scroll to top.
I'm actually proud of my solution to scrolling. People didn't want to scroll up to check results, then back down. Also, one player mentioned it was hard to tell when the room changed. I didn't want to get rid of the cool pictures, so I used them to my advantage. When the page scrolls to the top automatically on room reload, it will show most of the picture, visually signalling a new room has arrived.
I added a few things to my previous todo list for the show HN, namely bots. I also might want to revisit powers again sometime soon, but not for now.
In June I'm going to do a game jam and take a break from this, so July will be when I will do the show hn.
For playtest this weekend:
- Room writing instructions.
For the show hn:
- polish website?
- bots. this will be helpful to get people to try the game before convincing their friends to join.
- create a real docker build. I've been putting this off for a while and using my quick and dirty image, but I'll need an image with deterministic builds from a svn revision/branch with a database in a volume. This will probably also include some minor tools fixes to support the new build.
- db backups, dr. For the short term, this is just being able to grab it somewhere on the filesystem and copy somewhere else on the filesystem. For a production server I'd store the db backup offsite but that's not necessary for the staging build
- monitoring, metrics, alerting. I need to be able to see how well the app is performing. I doubt the show hn will blow up (most shows have like 2 upvotes) but if it does I'll want to know whats wrong. The UI is pretty inefficient, and I know the DB code does WAY too many queries for simple operations.
- lock down dev and tools dir. cannot forget to do this, but it should be covered in the new docker build.
- https. pretty simple, just adding a letsencrypt cert to the server and connecting to pound
2 hours
Last edit: dungeonsoffear 2021-05-27