Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

34
  • 94
    Is there a plan to add a table button (wizard, csv converter, something?) to the editor for those... less fluent in md?
    – Nick is tired
    Commented Nov 23, 2020 at 17:22
  • 13
    Timely advice to readers, the easiest way is writing your tables in a spreadsheet and exporting in one of the markdown supported formats.
    – bad_coder
    Commented Nov 23, 2020 at 18:03
  • 5
    @Ollie Clearly, we're so excited about them, we don't want to let you hide them! :P (My guess, they're both not CommonMark, so they don't play well together) Feel free to post as an answer
    – Catija
    Commented Nov 23, 2020 at 18:11
  • 4
    There are a few table posts now in the Formatting Sandbox, e.g. this one highlighting a few differences between preview and finished post — and of course the usual sandbox weirdness.
    – Sebastian Simon
    Commented Nov 23, 2020 at 18:23
  • 34
    @Nick yes, we're going to include buttons for inserting and editing tables in the new editor that we're going to present soon. Tables are complicated so we'll likely need a few iterations to get this right but I think this will be a step in the right direction.
    – Ham Vocke StaffMod
    Commented Nov 23, 2020 at 19:07
  • 1
    @Ollie It was added to meta.stackexchange.com/editing-help. We'll update the help center once we're ready to roll support out network-wide.
    – Adam Lear StaffMod
    Commented Nov 23, 2020 at 22:33
  • 2
    Glad to finally have table formatting, instead of having to rely on complicated MathJax to make "arrays". Hope the rollout goes well! (...Also, it bothers me that that last header about migrated posts is missing a question mark at the end. >.>)
    – V2Blast
    Commented Nov 24, 2020 at 0:48
  • 4
    Thanks for implementing this. It might be quite handy in some situations. "Teams customers asking for this ..." That made me realize that this community here should have stronger ties to the Teams user community. That way whenever we want something we should tell Teams users how wonderful that would be for Teams first. :)
    – NoDataDumpNoContribution
    Commented Nov 24, 2020 at 14:58
  • 2
    @SonictheK-DayHedgehog I'm still around, just had a busy day yesterday and didn't manage to triage the feedback. I'll catch up on things and will do my best to support the responses in this question throughout the week.
    – Ham Vocke StaffMod
    Commented Nov 25, 2020 at 7:57
  • 2
    This syntax seems fairly similar to Markdown Extended Syntax's tables.
    – Robotnik
    Commented Nov 26, 2020 at 0:28
  • 1
    Can you address forcing of header content to uppercase? E.g., in section "Limitations".
    – This_is_NOT_a_forum
    Commented Nov 27, 2020 at 8:10
  • 2
    @P.Mort.-forgotClayShirky_q I'm still trying to figure out the right course of action for uppercasing headers. I want to run this by our designers once they're back from holiday next week to see if this is something we want to keep or not.
    – Ham Vocke StaffMod
    Commented Nov 27, 2020 at 8:13
  • 8
    @AndrewGrimm what kind of disability are we talking about? The HTML tables we're generating are using proper semantics and should work reasonably well for users who are using screen readers. A lot of care goes into our Stacks design system to make sure the colors and fonts we use work for visually impaired users. Accessibility is hard and we don't always get it right, but we're trying. If you notice something specific that's not accessible, please let us know.
    – Ham Vocke StaffMod
    Commented Dec 4, 2020 at 11:11
  • 5
    @DavidConrad I get why this is confusing. Let me try to clarify: CommonMark is a popular markdown specification. Switching to CommonMark allowed us to replace our old, hand-rolled Markdown renderers with something off the shelve. CommonMark does not define tables (yet?). The open source renderers we introduced, however, support more than just CommonMark (GFM tables for example). That's the causality. Switching to CommonMark brought us open source renderers and they brought table support.
    – Ham Vocke StaffMod
    Commented Dec 11, 2020 at 7:50
  • 6
    @TheTechExpertGuy That's not really how Community Wikis work. A CW is a signal that the post is open to editing and contributions from all people who wish to participate. It's not a way to shelter from rep gains. Additionally, this is an important release that Ham led and getting some reputation for that and taking the time to announce and support the release is... totally fair. We do not use CW for announcements. That would be a huge departure from our standards. This is also a big change, which is why it's been featured for a while, but "a pretty long time" is just a week, not so long.
    – Catija
    Commented Dec 11, 2020 at 14:24