The last column in my table could use a little more room.
That was my first thought looking at the exported document. The table had three columns: Deliverable, Owner, and Review requirement. They appeared equally wide, even though the content wasn’t. “Product” sat in a mostly empty cell, while the review instructions beside it wrapped across several lines.
Everything was readable. I’d just give the descriptions more space and the names a little less.
I was working with a short set of project handoff notes written in Markdown. There wasn’t much to it: a table, a few review steps, and a small JavaScript function.
For the conversion, I used Markdown to Word. I pasted in the text, kept the default Classic style, and downloaded the DOCX. I left the styling alone at this point; I wanted to see what the default output gave me before changing anything.
Below the table, the review steps were easy to follow. The second numbered step had three bullet points underneath it. Those stayed indented, and the next main step continued with “3.”
I could read straight through the instructions without having to stop and work out which points belonged together. For a handoff document, that’s something I’d want to keep.
The code block was the next thing that caught my attention. It was short, but the indentation and the blank line before return helped separate the pieces of the function.
Both were still there, along with the line breaks and monospaced text. The code also remained editable text.
It didn’t have syntax highlighting. For these few lines, I didn’t miss the colors much. I’d take another look with a longer example, especially one with lines wide enough to wrap.
The heading styles carried over, too. The title, main sections, and subsection kept their hierarchy, so I wouldn’t need to set those up again if I wanted to reorganize the document.
The reference at the end was still a blue, underlined link, with the same label and destination.
I wouldn’t want to rebuild either of those by hand after every export.
In LibreOffice, the notes fit on two pages without anything getting cut off or overlapping. The code section started on the second page, with its heading and explanation together, so the page break felt like a natural place to pause.
For this particular document, I’d leave most of the formatting as it is. The table is where I’d spend another minute.
A little more room for the descriptions would make the page easier to scan. That’s a small edit, but it’s the one I’d make before sharing the file.
Top comments (0)