MRC iteration - News Bits and Scaling

I have always thought that the "Photoshoots" slideshow in the front page would be better bigger in some other place, because it is fun to watch.
Thank you for the entire effort.

Wow, thank you for working on this behind the scenes!! This website offers a huge service to the community, and it's often easy to forget that there are people behind it offering their time to make it work, paying the hosting bills, etc. A huge thank you for all the work!

I got used to it, I frequently visit on my phone, but it could definitely be better. I basically always start with a double-tap to zoom in. And since I recently started using the Firefox app, its biggest downside is that the double-tap doesn’t work anymore so I gotta use both hands to zoom in now.

It’s true that it does have its moments, where it reminds me of something that happened years ago, and I go “hah, on yeah that happened” or ”it’s been that many years ago already”. So it’s a fun category, although I might not miss it severely.

Very nice!

I noticed some variance in the width of the blocks on the frontpage, and I could scroll right a little bit in a number of places. In the desktop browser I made a user style in Stylus which cleaned it up in the places that I could find, hopefully that’s useful to tweak the CSS a bit more!

@media only screen and (max-width:988px) {
    /* frontpage: clear a bunch of float: lefts and width: 100%s */
    #main .block-contentblock,
    #main #block-contentblock-6,
    div.front-one,
    div.front-two,
    div.front-three,
    div.front-four,
    div.front-five,
    div#spotlight-items {
        width: auto !important;
        float: none !important;
    }
    
    /* frontpage: tweak some white space in the spotlight */
    div#spotlight-items div.slp {
        width: auto !important;
        margin-left: 4px;
        left: 0;
        right: 0;
    }

    /* newspost/forum: negative margin caused horizontal scroll */
    div.comment-options {
        margin: 0 -4px -2px -4px;
    }

    /* newspost/forum: let post contents span full width */
    /* To cancel out the max-width: 90% (can’t remove with userstyle) */
    div.txt {
        max-width: 100% !important;
    }

    /* forum/photoshoots: negative margin caused horizontal scroll */
    /* It was just to cancel out the padding, so we remove the padding instead. */
    body.node-forum-view #content,
    body.page-image #content {
        margin: 0;
        padding: 0;
    }
}

It's better to put the wiki above "News bits".

Any way to turn the scaling off? Even with "desktop site" enabled I get the scaled site.

Or use landscape on ye phone. I always hated that I needed to zoom on my phone. And even onㅣlandscape... We are old msx users, out sight gets less with age. I need glasses to read on my phone since last year. This scaling helps a lot ????

screen resolution is 1080 x 2400 pixels, chrome browser
on phone obviously.

doesnt seem to be possible to get the full site regardless of what i do, portrait mode /landscape

I browse MRC from my phone quite often, and there's only one thing I can say:

THANK YOU!!

What you've done makes a hell of a difference!

Yes, what is used less must be lower. The wiki is more used that the News bits section.

That is a great idea, basically reverse the chronological order of comments in a thread so newer comments are on top.

That is not what mcolom said.

Because fun:

/**
 * MRC layout tweaker -  arrange msx.org frontpage to your liking
 * v0.1
 * 
 * .front-
 *     one             spotlight (6)             (2 blocks wide)
 *     two        news headlines (2)  &  latest forum posts (12)
 *   three    lastest reactions (10)  &            news bits (9)
 *    four  trading & collecting (4)  &         wiki updates (3)
 *    five      today's history (11)  &         photoshoots (22)
 *
 */

Say you want latest forum posts first, then latest reactions, then wiki updates, and then whatever, pass [12,10,3] to the function:

(function(n,t=[]){const e=document,o=e.createElement("style");o.innerText="\n#main {\n\tdisplay: grid;\n\tgrid-template-columns: 1fr 1fr;\n\trow-gap: 8px;\n\tgrid-auto-flow: dense;\n}\n#main > div[class|=front] { display: contents; }\n#main > div[class|=front] > .block {\n\tmargin: 0!important;\n\tpadding: 5px;\n}\n\n#right > .sidebar {\n\tpadding-top: 6px;\n}\n#right > .sidebar > .block {\n\tmargin: 0 6px 6px 6px;\n}\n\n@media (min-width: 989px) {\n\t#main > .front-one > .block { grid-column: 1/3 }\n\t#main > .help { grid-column: 1/3 }\n\t#main > .share { grid-column: 1/3 }\n}\n\n@media only screen and (max-width:988px) {\n\t#main {\n\t\tgrid-template-columns: 100%;\n\t}\n}\n",document.head.append(o);e.getElementById("main");let i=0;const a=n.length;for(const d of n){i++;e.getElementById(`block-contentblock-${d}`).style.order=-1*(a-i+1)}for(const d of t){e.getElementById(`block-contentblock-${d}`).style.display="none"}})([12,10,3])

You can use this as bookmarklet, or try it in your console. If there's any interest I could write this as user-style, or user-script (JS isn't actually needed). Note: a subsequent invocation (with other values passed) won't work properly ATM.

There's something that can be improved for the photo part... it has a wrong scaling option, chopping off important parts of the image:

Hai, I fixed the link in Ascend, it was padded with a space. That's buggy indeed.
The Nijmegen reactions are correct, those point to different images with the same title. Yup, confusing.

thanx gdx, for keeping an eye on things