Turning my Markdown notes into a Word document
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…
I observed that the table in my exported document appeared uneven, with the Deliverable column taking up more space than the Owner and Review requirement columns. This discrepancy was evident despite the varying content within each cell. Despite the text being easily readable, I decided to allocate more width to the descriptions while reducing the space dedicated to the names.
The project handoff notes I was working with were relatively simple, comprising a table, a few review steps, and a compact JavaScript function. To proceed with the conversion, I employed the Markdown to Word tool, preserving the default Classic style and downloading the DOCX file. Initially, I opted to maintain the existing styling so that I could evaluate the default output before making any adjustments.
The review steps following the table were straightforward, featuring three bullet points beneath a numbered second step. These bullet points remained indented, allowing for seamless reading without the need to discern which points were interconnected. The continuity of the instructions, such as "3," facilitated a smooth reading experience.
I also paid close attention to the code block, which, although brief, retained its indentation and the blank line preceding the "return" statement, aiding in the separation of function components. Both the code and text remained editable, devoid of syntax highlighting—a feature I found acceptable given the short length of the code.
The heading styles were accurately transferred, encompassing the title, main sections, and subsections, thereby eliminating the necessity to reconfigure the document's hierarchy. The reference at the end remained intact as a blue, underlined link, preserving its label and destination—attributes I deemed unnecessary to recreate manually after each export.
Upon examination in LibreOffice, the notes accommodated comfortably on two pages, with no elements being truncated or overlapping. The code section was positioned on the second page, accompanied by its heading and explanation, rendering the page break a logical and intuitive pause point. For this specific document, I concluded that most of the formatting remained satisfactory as-is.
However, I recognized the need to allocate an additional minute to the table, increasing the space allocated to the descriptions to enhance readability upon sharing the file.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
