Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the "town hall" (meta-discussion site) for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Enhancing mobile readability for long numerical data tables

+3
−0

Hi everyone,

I’m a new member and I've been exploring how we present technical information here. I noticed that when we use standard Markdown tables for comparative data—such as long lists of regional codes or telecommunication prefixes—the mobile experience can be a bit challenging.

On smaller screens, these tables often require significant horizontal scrolling, which makes it hard to compare data points across rows.

I’m curious if the community has any recommended best practices or Markdown "tricks" to make these tables more responsive? For example:

Is it better to use nested bullet points instead of tables for long lists?

Are there specific ways to format headers to keep the columns narrow?

I want to ensure that any technical data I contribute in the future is as accessible and "mobile-friendly" as possible for everyone.

Looking forward to your thoughts and suggestions!

History

1 comment thread

Thanks for raising this. I was not previously aware of the problem (not having done much with Markdo... (1 comment)

Sign up to answer this question »