The only, and I mean only change that affects the forums is the iPhone viewport tag ( which only changes the width). The header is the only thing affected by the media queries. So no overspecialising has occurred, if anything all the forum affecting changes can be attributed to this tag:
<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0;">
The mark up and styling of the PHPBB forum itself has not changed, what you are seeing is the existing layout being squashed into the real iPhone screen width.
Now I'm aware that this isn't ideal when looking at the forum index. So you have two choices:
- Wait until I start making changes to streamline the forums (e.g. smaller icons, less padding in some places to save horizontal width etc)
- Fork the springsite repo on github, change 5 or 6 characters so the iPhone viewport tag is say... 600px on the forums, rather than device screen width, then commit and issue a pull request ( all doable from the github web frontend, no push/pull/desktop client required. )
My time at work is booked at the moment and I've had freelance work of an evening for the last few days so I've not had a chance to work further on these things, else I would have made progress.
The width at which the forum no longer shrinks and requires panning or zooming is ~552px on a desktop for most pages. On an iPhone, the forum retains this width and panning to the right is needed, or zooming out ( which gives what we had to begin with but with more legible text than before my changes were made ).
Changes I plan to make to the forum:
- Add classes and IDs to various elements
- Hide the upload attachment part when on an iPhone
- <600px Remove the unread and read icons on the forums and replace them with highlighting ( subject to testing, it may turn out to be better than sliced bread, or it may be so garish I claw my eyes out )
- <600px Reduce widths on author columns
- <600px Linearize the top menus
- Make the preview post table the same width as what gets actually posted ( it doesnt account for the author column )