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 »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Best practices for posting tabular data

Parent

Best practices for posting tabular data

+4
−0

I am trying to find how tabular data is presented in Software Development. So far, I have found one question, How to pivot text?. The question presents tabular data using code blocks, dash to indicate a new row, pipe to indicate column separation and underscore to indicate an empty cell. I took the data from the referred question and set none as the programming language to prevent the text from being highlighted:

- PERSON 1 | PERSON 2 | YES
- PERSON 1 | PERSON 3 | YES
- PERSON 2 | PERSON 1 | YES
- PERSON 2 | PERSON 3 | YES
- PERSON 3 | PERSON 1 | NO
- PERSON 3 | PERSON 2 | NO

and

- _________| PERSON 1 | PERSON 2 | PERSON 3 |
- PERSON 1 |   X      |   YES    |    YES   |
- PERSON 2 |   YES    |   X      |    YES   |
- PERSON 3 |   NO     |   NO     |    X     |

Sometimes, including the column and row headers on spreadsheet-formula questions might be relevant. Below I'm using dashes (-) and a plus (+) character between columns to separate the column headers from the data below:

  |    A     |    B     |  C
--+----------+----------+-----
1 | PERSON 1 | PERSON 2 | YES
2 | PERSON 1 | PERSON 3 | YES
3 | PERSON 2 | PERSON 1 | YES
4 | PERSON 2 | PERSON 3 | YES
5 | PERSON 3 | PERSON 1 | NO
6 | PERSON 3 | PERSON 2 | NO

It bugs me a bit that the space between lines looks to be too big.

  • Is there a better way to present tabular data?
  • Is there a way to reduce the space between lines?
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Thanks for posting what you learned in an answer. I've filed an issue to add tables to the formattin... (1 comment)
Auto suggest (1 comment)
Post
+3
−0

I just found a post in Codidact Meta using showing a rendered table. Looking at the post content, it is using markdown.

Playing a bit, I found that the following "plain text" (intended to show markdown features, not to make it readable, maintainable, etc.)

| | | |
-|-|-  
PERSON 1 | PERSON 2 | YES|
PERSON 1 | PERSON 3 | YES|
PERSON 2 | PERSON 1 | YES|
PERSON 2 | PERSON 3 | YES|
PERSON 3 | PERSON 1 | NO|
PERSON 3 | PERSON 2 | NO|

is rendered as follows:

simple table

Live demo:

PERSON 1 PERSON 2 YES
PERSON 1 PERSON 3 YES
PERSON 2 PERSON 1 YES
PERSON 2 PERSON 3 YES
PERSON 3 PERSON 1 NO
PERSON 3 PERSON 2 NO

Recently found related posts

Blog

Feature requests

Markdown

HTML

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Extra options (2 comments)
Extra options
trichoplax‭ wrote over 1 year ago · edited over 1 year ago

Might be worth editing to mention the extra options that this example is not using:

  • above the dividing line of hyphens, you can include column headers between the vertical bars
  • you can add more hyphens in the dividing line to make the vertical bars line up with the vertical bars in the other rows in the raw text
  • you can add spaces to make the vertical bars in all the rows line up, so it looks like a nicely aligned table even in the raw text - this makes it much clearer for future editors
Wicket‭ wrote over 1 year ago

Thanks for the suggestion. As the above answer is not intended to be used as a reference, I just mentioned that the "plain text" is intended to show markdown features.

P.S. I also added a section of recently found related posts that might be helpful when writing / updating a post / help article about using tables.