The link to the schedule in the website header redirects to https://ep2023.europython.eu/schedule/2023-07-19 which returns a 404 ;( It was working for me yesterday (I think).

It would be helpful to list speaker names inside letter groups on the SpeakersPage:
app/(pages)/speakers/page.tsx

On the speaker list (https://ep2023.europython.eu/speakers), Kuldeep Pisda appears twice. They appear to be the presenter of two sessions, so that might have been the issue.

I would suggest to enhance conference schedule by:

1. add option to download iCal (or common calendar format) calendar files which can be stored in attendees mobile devices
2. add option for registered users to personalise schedule and select tracks into your personal list... to ease up planning of attendance.

This would actually help organisers to see potential interest on topics (how crowded rooms might be) and attendees would see if they have selected all tracks they are interested.
In addition there is no reason to have schedule on paper - save money on printing and save nature by not generating additional waste.

I think it would be tremendously beneficial if session pages (e.g., talk/tutorial/poster session pages) included the date, time, and the room in which the session is taking place.

EP 2022 has a dedicated branch @ archive/2022, the website on vercel now points to that branch.

We should document this properly once we add a new website for 2023 :)

use field Custom Room on pretalx to list the room place in each individual poster listing, so it doesn't show the column name on the schedule.

I just saw that community voting closed on 14th April:

https://fosstodon.org/@europython/110190566061335730

And https://ep2023.europython.eu/voting confirms it has closed.

But https://voting.europython.eu bookmarked is still accepting votes. I was still voting on a few every day for the last three weeks despite it being officially "closed" 🙃

Please could you actually close https://voting.europython.eu and add text at the top?

Each tutorial looks like two separate talks instead of one event:

One design idea to improve this visually is this:

Since we are using resources on pretalx, where speakers can upload their slides (super useful stuff!), we should list them on the website.

For the homepage, it shows correct Prague information.
For content pages, it shows Dublin dates & location.

If you add a markdown header to a "pages-content" file, the Next.JS rendering will automatically wrap the header in a link with an anchor for that header (e.g., https://ep2023.europython.eu/mentorship#mentee for the header "Mentee" on the mentorship page). The problem is that the target anchor name isn't added as the id attribute of the header HTML tag.

This means that anchor links don't actually jump to the relevant location on the page.

On the sprints page, the organizers were asked to leave their e-mails, and the generated page then contained email: links without any obfuscation. Such exposed addresses tend to be harvested by bots for spamming, and that happened with my address.

What can be done instead is to obfuscate the address by using HTML entity in place of the @ character, so that it still works correctly in the browser, but is harder to find with a simple bot scan.

In EuroPython Website, Financial Aid Column The Text written on the Button which re-directs to Google Form, is hidden but It is visible on hover, Here is Snapshot to the Issue:

Thanks, Gaurav!

Would be nice to have the session timings and room displayed on the session page upfront when someone opens an individual session page like: https://ep2022.europython.eu/session/django-girls-workshop

Ideally it should be above the abstract just after the title.

• A: Hyperlinks with the anchor element has no underline or primary colour styling.
• B: Lists using MD (- or *) doesn't show bullets; using <li> changes font size. Currently amended main.css here
• C: title's # doesn't get hidden on mobile
• D: <ButtonWithTitle> and <ButtonLink> - need a linebreak after the button. The title currently applies h3, which looks a bit big.
• E: <img> needs a linkebreak after the image.
• F: p.large styling doesn't exist. <p> styling is also different from text without the tag.
• G: I think the sponsor page width needs to be wider to fit the tiers.
• H: with the font size bigger than 2022, I am not sure if it makes sense to increase the overall width for the text.
  Edit: According to Sebastiaan, the general recommendation for text length is between 50-80 characters per line for readability. We might want to consider what an appropriate width is.
• I: the bullet point points to the middle of several lines. This looks very confusing when it is nested. e.g. the following renders as seen in screenshot
  

• Fruit
  • Apple

Right now the default day is the first tutorial day. It is not clear we're looking at tutorials and not at talks and it may be very confusing for users. Adding some mark in the dropdown, like it is present right now for sprints, should improve that.

On pretalx, tutorials and the special workshops all listed with a duration of 90 minutes. But they have either 2 or 4 slots, making the total duration either 90 * 2 (180 min) or 90 * 4 (360 min). But on the specific session, the duration is only listed as 90 mins. See https://ep2023.europython.eu/session/transcode as an example.

Maybe we can add a "back to top" button at the bottom of each schedule page. Or we maybe we can allow the selection of day at the bottom too.

I think it would help users to check different days of schedule easier.

          I briefly looked into sources on the effect of line length on readability for digital screens. Unfortunately, I don't have access to most full-text articles anymore.

There seem to be a couple of different approaches to this question, though. Those approaches include measuring a speed/comprehension trade-off, testing for scanning/visual search in text, and measuring subjective preferences for line lengths. The problem is that there seem to be different answers based on what is measured.

In general, I've read that:

• Longer line lengths are better for quick scanning, as you have to scroll less and make fewer line jumps.
• Medium line lengths (often defined as somewhere between 50 - 80 characters per line) are better for accuracy
• Medium line lengths are preferred by most participants.

Here ar a few sources:

Dyson, M.C., & Kipping, G.J. (1998). The Effects of Line Length and Method of Movement on Patterns of Reading from Screen. Visible Language, 32.

This study comes to two different conclusions:

• People read faster at long line lengths (defined as 100 characters per line) compared to shorter line lengths while reading comprehension stayed pretty much constant over line lengths
• People subjectively preferred reading at medium line lengths (with the most preferred length being 55 characters per line)

In the discussion, they suggest that you should be careful applying principles from printed text to text on screens.

Ling, J., & Van Schaik, P. (2006). The influence of font type and line length on visual search and information retrieval in web pages. International journal of human-computer studies, 64(5), 395-404.

This study comes to the conclusion that longer lines allow for faster scanning of a text for specific terms, but when it comes to processing the information and recalling it later, they found an optimal line length of 70 characters per line. In addition, the subjective preference was for shorter line lengths (55 - 70 characters per line), with a strong effect size in their first experiment and a small-to-medium effect size in their second experiment.

Their main design recommendation relevant to our discussion is:

Given a choice between using long (85–100) and short line lengths (55–70), designers should opt for the latter, because although scanning web pages is also a major activity when finding information on websites (Kitajima et al., 2000), the majority of textual web content is presented to be read rather than skimmed. (page 403)

Baymard Institute

This is a private institute from Denmark, but they do a lot of applied UX research. They have an article on line length that recommends 50-75 characters per line.

Wikipedia

Wikipedia does not provide a clear guideline in terms of line length for electronic text, but also states that shorter line lengths are better for accuracy, while longer line length have benefits for scanning tasks. See https://en.wikipedia.org/wiki/Line_length.

Originally posted by @SebastiaanZ in #224 (comment)

In mobile layout, CoC is the only menu item shown, e.g. in screenshot:

We use mdx with some custom plugins and if there's weird (or unsupported) syntax the pages won't render, but since we render them on demand the build won't fail and we won't notice it in PRs.

Previously, we had so each page's social card automatically rendered, e.g. https://github.com/EuroPython/website/blob/main/public/social-cards/trans_code.png. for Trans*Code page. Currently all page show default. We should probably hide all last year's social cards and when a page has a custom one, they can be shown.

There https://ep2023.europython.eu/wasm page on firefox (v114) has issues and doesn't render the content:

Well, technically it renders it for a fraction of a second and then it dissapears:
https://github.com/EuroPython/website/assets/4189262/0d57bd75-ebba-4217-a131-16fd20f94fd6

On the same machine with Chrome I get a clean console output:

The error messages:

Error: Connection closed.
    NextJS 42
46-e273b211b434aca0.js:1:3406
    NextJS 44

Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    NextJS 40
9766e88b-8e662d1be9194dc0.js:9:113072

Uncaught Error: Connection closed.
    NextJS 42
46-e273b211b434aca0.js:9:4656
    NextJS 42

• Don't show as "announcements", but ideally "Registration" or nothing. Can make a session type on pretalx.
• Room is all wrong - showing Club A for every instance is probably a pretalx bug. But we can just remove the room in the separate listings all together.

If a speaker's homepage URL (on the individual speaker page) does not start with http(s)://, it appends https://ep2022.europython.eu/speaker/ before the URL.

This is how it was supposed to look like:
https://ep2023-git-fork-sebastiaanz-feature-f-ad9fb0-europython-society.vercel.app/finaid#timeline

          On mobile, there's no real indication that you can click on these three cards. With a mouse, you get a pointing hand cursor on hoover, but there's obviously no such indication on mobile.

Originally posted by @SebastiaanZ in #235 (comment)

To be investigated :D

Some extra context already passed on discord, but for example Sebastiaan's talk and Sanskar's tutorial appear twice on the list. There about ten or so duplicates in total.

I find the dev experience of tailwind css much better than using regular css ^^

So we don't forget 😊

Not sure if I am doing the right thing in PR 61. Maybe something about the css, but it doesn't seem to show correctly for me.

Sames #127, but for times on mobile :)

1. I think the dimensions of the card is wrong. It appears cropped on twitter.
2. should not transform keynoters' picture (cropping is better than warping)

On the schedule, on top of each talk, we display the level (which I assume is Python level and not domain level). But when you click into the talk to see more details, you no longer see the level of the talk. I think both the Python and domain level should be listed before the Abstract.

This is raised in PR #75 (comment)

The HTTPS certificate expired on Sunday 27 November 2022 for at least:

• https://blog.europython.eu/
• https://www.europython-society.org/
• https://ep2021.europython.eu/
• https://ep2020.europython.eu/
• https://ep2019.europython.eu/
• https://secure.europython.eu/

Still working, because it has its own instead of using secure.europython.eu:

• https://ep2022.europython.eu/

• 4 tutorial tracks are accessible to tutorial & combined tickets holders. But we have one track for people with a conference tickets, and the other open to public (both requires additional registration on their dedicated event page). It'd be really nice to have a way to mark the differences on the schedule - perhaps putting a thicker grid between the normal tracks and special tracks and add "registration advised/required" to the special tracks.
• We have some reserved slots for the open space, e.g. Mentored Sprints. We'll list the events on the menu /events. But would be good to have these represented on the schedule (could be a tab called Open Space).
• Would be good to list the sprints on the schedule (rooms, coffee break) - perhaps show a dropdown on the schedule but redirect to the sprint page.

“Practical tools for documentation at scale” by Daniele Procida is not listed on /sessions or /tutorials

It would be a nice thing to have a list of all the speaker sessions in the speaker page; i.e., each speaker page could link to all of that speaker's sessions.

Example from the 2021 website: https://ep2021.europython.eu/profiles/rodrigo-girao-serrao/