You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
A couple of us are looking to enhance Docs to Markdown (in addition to addressing some outstanding bugs and feature requests).
Before we get started, wanted to ask you followers if you have any ideas that you haven't already noted in bug reports or feature requests. Can't guarantee that we'll implement all of them, but we'll certainly consider them.
A few ideas that we've been playing with and have implemented prototypes of:
variable: single line or multi-line text blocks that can be replaced throughout the document by referencing the variable name (in conversion output, of course).
definitions of important terms: Users can hover over marked terms and see the definition as a tool tip.
acronym expansion: When acronym/abbreviation expansions are provided, we replace (in the conversion output) the first instance of the acronym with the expansion followed by the acronym. For example: Community Learning Center (CLC).
comments: Allow comments in the Google Doc. These are not visible in the rendered output (either ignored or written as HTML commments.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
A couple of us are looking to enhance Docs to Markdown (in addition to addressing some outstanding bugs and feature requests).
Before we get started, wanted to ask you followers if you have any ideas that you haven't already noted in bug reports or feature requests. Can't guarantee that we'll implement all of them, but we'll certainly consider them.
A few ideas that we've been playing with and have implemented prototypes of:
Thanks,
evbacher
Beta Was this translation helpful? Give feedback.
All reactions