Hello Aleksi Thanks for your feedback. I think I need to clarify a couple of things, which I should have made a little more clear in the article. Firstly, the article relates specifically to www.ripe.net, our public website. These changes won’t affect the functionality or design of our other websites such as the RIPE Database, stat.ripe.net, atlas.ripe.net, etc. This means that your workflow shouldn’t be affected if you’re using one of these tools. Secondly, in the article, “fully responsive design” refers to the practice of making a website’s layout change based on the size of the screen on which it is presented. Generally this practice doesn’t change the content on the page itself, instead it moves the content around to best fit the screen size and orientation. For example, a page displayed on a tablet device would use a slightly smaller font size and reduced image sizes compared to how the page would display on the larger screen of a laptop. The page’s HTML and contents would be the same in both cases, and the transition between layouts doesn't require the page to reload. This also shouldn’t affect your workflow, and the changes we’re making in this respect will be limited to the www.ripe.net website. I hope this answers your concerns. If not, please feel free to reach out and I can provide more detail. Best regards Phillip Oldham Manager, Web Services RIPE NCC On 21/11/2023 10:53, ncc-services-wg-request@ripe.net wrote:

Date: Tue, 21 Nov 2023 11:53:39 +0200 From: Aleksi Suhonen <ripe-ml-2023@ssd.axu.tm> To: ncc-services-wg@ripe.net Subject: Re: [ncc-services-wg] New article on RIPE Labs: Redesigning ripe.net Message-ID: <4ea8f573-85e8-4566-b7e2-002e7528e38f@ssd.axu.tm> Content-Type: text/plain; charset=UTF-8; format=flowed

Hello,

...

Following up on plans laid out back in our Activity Plan and Budget 2023, over the past year we've been working towards improving ripe.net. In this new article on RIPE Labs, I give an overview of the changes we have in mind and a sneak preview of the new design: The previous iteration (or two?) have been plagued by things that look

On 10/11/2023 16:37, Phillip Oldham wrote: like links, but are not in fact links, so you can't open them in another tab. I hope this design pattern will be discontinued.

When working with a smallish number of RIPE objects, I like to open them all into separate tabs first. Then I go through the tabs and check each object for the changes required, if any, and then close them as they have been dealt with. Once I run out of tabs, I know I've covered everything, and I can sleep soundly.

The RIPE labs article talks about "fully responsive design" which to me sounds like I would need to responsively make a new search for objects after each object I've handled. This is a nightmare, as I'd inevitably/accidentally end up checking some objects several times, and at the end of the day I still couldn't be sure that I've done everything I set out to do.

My 2 cents,