Yeah. Bootstrap was my first thought.
Buffistas Building a Better Board ++
Do you have problems, concerns, or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Point of order: I generally view b.org in w3m, a console web browser with no Javascript. It works beautifully. I would really, really like for that to remain the case.
Bootstrap is a CSS thing, not a Javascript thing. The idea would be to have things look the same, but in a way that scales to mobile better.
Thanks to Jon, the b.org source is now in a private repository in gitlab :).
I've added some issues, investigating the logging out issue, fixing a concerning security flaw, and coming up with a plan for a better mobile experience.
It you want to participate in board development, let me know, and I can hook you up to get access to the repository.
My first task will be organization and cleanup to make local deployment easier.
In general, I think it should be policy to work on a branch rather than master.
Oh, oh, make a scrum team! Have sprints! And daily stand-ups!
(Please do not do these things.)
Oh, we're doing it all, including planning poker. I've got a whiteboard and a stack of sticky notes waiting. I'm going to agile the sh*t out of this.
(No, no I'm not.)
Agile is a verb now? I had no idea.
Another big issue is that after the PHP upgrade in January, all new database records that are created are encoded as UTF-8, whereas all previous database records were Latin-1. So if you go back and read any old posts, you will see a lot of ⬧s.
I was thinking of writing a script to go through and update all the old records and reencoding any that aren't just plain ascii to utf-8. (I did this manually already for a few things like the quotes, and § ita §'s username. The main problem being that it would take a long time to complete (weeks or even months), and there is the possibility I could fuck up the board's database.
Buffista product tenets:
All planning poker must be done with kittens.
After planning, post-its must be copied on to the sprint board using a system of different colored pens.
Anyone who suggests building an experience map will be staked.
I've added some issues, investigating the logging out issue, fixing a concerning security flaw, and coming up with a plan for a better mobile experience.
Gud: Do you have the keys to ftp/ssh? i.e. Can you pull updates to the main site?