A lot of you are noticing the preexisting automatic detection feature from 2022 [1], which I also worked on. That's NOT what this newly announced feature is. The new feature supports full import/export, but it's still rolling out so you're likely not seeing it yet!
Hope you like it once it reaches you :)
[1] https://workspaceupdates.googleblog.com/2022/03/compose-with...
1. There's a service I use sporadically or used to use
2. They announce a new feature that might potentially mean I'll start using it again/more
3. I read the post, log in and realise I don't have access yet
4. I completely forget this ever happened.
Surely all the effort that goes into announcing these things is a bit wasted ?
What happened to the a nice "Labs" switch to opt into stuff that's new and a bit raw?
Labs is more for experimental features that needs more beta testing before rolling out to everyone, rather than being the "first stage" of slow rollout.
I work at Google in open source so I am constantly converting Google Docs to Markdown to put them on GitHub and vice versa. This will save me a lot of effort.
I often need to prepare technical slides with code in it, and being able to just backtick away into a <code> tag or a <pre> block would be a godsend.
This source code: http://hub.scroll.pub/slideshowdemo/index.scroll
Produces this HTML: http://hub.scroll.pub/slideshowdemo/
I won't support directly importing Markdown as DOCX. For that you could convert from Markdown to Docs to DOCX though.
I would say there wasn't much disagreement there. I typically started out by writing tests for the simple cases, then I would identify edge cases through actual usage of the feature locally, and write tests for those as well. Also, whenever bugs were found, I would write "regression test cases" for those when fixing.
Export outputs base64 encoded image URLs. We use Markdown reference links to place the large URLs out of the way of reading at the bottom of the file
Any hint on why you have used square brackets?
See https://daringfireball.net/projects/markdown/syntax#link
Google Colab also supports Markdown input cells as "Text" with a preview.
Does this work with Google Sites?
How to create a Google Sites page from a Markdown doc, with MyST Markdown YAML front matter
NotebookLM can generate Python, LaTeX, and Markdown.
How to Markdown and Git diff on a Chromebook without containers or Inspect Element because [...]
How to auto-grade Jupyter Notebooks with Markdown prose, with OtterGrader
How to build a jupyter-book from .rst, MyST Markdown .md, and .ipynb jupyter/nbformat notebooks containing MyST Markdown
This isn't to say I prefer CM -- because Markdown came into being from Gruber's script. In a literal sense, "Markdown" is defined as whatever `markdown.pl` is, warts and all -- however, contact with the outside world forced things to move in a direction that is (so to speak) more organized that what John originally wrote.
The existence of comments about how certain elements were rendered on export made me think that something was missing when compared with CM.
Just curious: Google docs supports a lot more than what Markdown has syntaxes for - how do you deal with this when exporting to markdown?
Well, you solved it. Thanks!
This will make a huge difference to a lot of my work.