Docs™ to Markdown
Docs™ to Markdown (GD2md-html) converts Google Docs™ to simple, readable Markdown or HTML. This add-on allows you to create documents using the excellent editing and collaborative features of Google Docs™, then convert to Markdown or HTML to use on your web site. Note that Docs™ to Markdown marks up the content (headings, paragraphs, lists, code blocks, etc.) but does not preserve colors and styles in text or tables. See https://github.com/evbacher/gd2md-html/wiki for docs. See https://github.com/evbacher/gd2md-html/ for the source to the conversion code. ------------------------------------------ Release information (most recent on top): - v2.0β1 (15 Nov. 2025): Fix bug 175: render Markdown definition lists in HTML. - v1.0β40 (13 Oct 2024): - Close list items before opening a new item. Close at the end of the list. - Add support for Markdown checkbox lists. - Fixes handling of superscript/subscript to close old styles before opening new style. Moves opening superscript/subscript later in process. - Added center/right alignment to HTML paragraph and heading handling. - v1.0β39 (12 October 2024): Google Docs recently added a tab interface, which changes the TOC-generated id. This breaks internal links. This release fixes that bug. - v1.0β38 (21 Sept 2024): Italic/bold markup default is now */**: _/__ is now an option. Reckless mode now includes Suppress info comment (removed sidebar option too). Also add a News link to gd2md-html news page in sidebar. - v1.0β37 (31 August 2024): Add a Questions link to gd2md-html Google group in sidebar (no functional changes). - v1.0β36 (26 April 2024): Update required permissions: set explicitly in appsscript.json. No code changes. Using these Oauth scopes: "oauthScopes": [ "https://www.googleapis.com/auth/documents.currentonly", "https://www.googleapis.com/auth/script.container.ui" ], -v 1.0β35 (20 Nov. 2023): No info comments if "Suppress info comments" selected. Also remove clipboard success text. If errors, there will be an informational error comment. -v 1.0β34 (12 Dec. 2022): Clarify note about TOC -- needs blue links to create intra-doc links). (gdc) -v 1.0β33 (8 Jan. 2022): Add reckless mode (no warnings or inline alerts). (sidebar, gdc, html) - v 1.0β31 (24 Aug. 2021): Don't contain in for HTML. - v 1.0β30 (1 July 2021): Reduce whitespace after list item (bullets, numbers) in Markdown. - v 1.0β29: Handle partial selections correctly (expand to whole paragraph). - v1.0β27 (19 June 2020): Copy output to clipboard. Print success/error messages for clipboard output (see chromium bug 1074489). - v1.0β26 (6 June 2020): Render soft line breaks correctly in HTML ( not <br>). -v1.0β25: Use image path in this form: images/image1.png, images/image2.png, etc. Clean up old zip image code. -v1.0β24: Correct a spelling error (s/Supress/Suppress/). -v1.0β23: Copy converted output to the clipboard. Add option to suppress top comment. -v1.0β22: Roll back font-change runs for now (still causing problems), but keep table note. -v1.0β21: Add a note that tables are currently converted to HTML tables. No change to rendered conversion. -v1.0β20: Handle font-change runs with extra whitespace better (italic, bold, etc.). -v1.0β19 (March 7, 2020): Fix for angle bracket at beginning of a line. Also: use doc title instead of URL in conversion comment. -v1.0β18 (12 Feb., 2020): Escape HTML tags by default, render them optionally. - v1.0β17 (5 April, 2019): Convert smart quotes to straight quotes in code, but leave them alone in other text. - v1.0β16 (25 Feb. 2019): Handle simple nested lists properly in HTML conversion (Markdown already works well). - v1.0β15 (10 Feb. 2019): Number ordered list items sequentially (instead of using 1. for all items).No change to rendered HTML. - v1.0β14 (15 Jan. 2019): Name change to Docs to Markdown: now published on G Suite Marketplace. - v1.0β13 (29 Sept. 2018): Close strikethrough text properly at the end of a paragraph. - v1.0β12 (24 Sept. 2018) : Convert strikethrough text. - Revert to: // - 1.0β11: Fix small bug: replace bufout with bufHTML. Remove version number from banner. Retitle. - v1.0β12 (28 May, 2018): Replace < with < by default. Add option to allow HTML tags. Also allow escape (\<). - v1.0β11 (24 March, 2018): No effect on output. Remove version number from banner. Retitle. - v1.0β10 (17 Feb. 2018): Handle soft line-breaks (shift-enter) properly. (Markdown and HTML) - v1.0β9 (9 Nov. 2017): Handle embedded paragraphs in list items for Markdown. - v1.0β8 (30 Oct. 2017): Use _ instead of * for italic markup to avoid ambiguity (Markdown). - v1.0β7 (10 Oct., 2017): Warn if DEBUG is true. - v1.0β6 (07 Oct., 2017): Ignore headings that are blank or just contain whitespace. - v1.0β5 (17 Sept., 2017): Warn about multiple H1 headings, but only in the top comment, not inline. - v1.0β4 (16 Sept., 2017): Don't wrap HTML by default. Add checkbox option to wrap HTML. For footnotes also. - v1.0β3 (29 July, 2017): Escape angle brackets (<) in HTML code blocks. - v1.0β2 (15 July, 2017): Check for spurious 0-row table. Fix image path for placeholder links. - v1.0β (10 July, 2017): Initial release of gd2md-html.
Formfacade - Embed in website
You are a startup founder or a project owner, who likes to move fast. So, you quickly put together a Google Forms™ to connect with your users. But, what do your users think when they see a form that doesn't have your branding? Does it give them the confidence, you will be able to deliver a great product or service, when you can't even show them a professional looking form? Formfacade's Embed in website addon modifies Google Forms™ to blend with your websites and apps. Replace Google branding in the forms with your own branding and gain your users' trust. ➤ Embed Google Forms™ in your website. Make your form look like your website With FormFacade, you can convert your Google Forms™ into a tailor-made form that fits neatly in your website. Once the user submits the form, you can manage them with Google Sheets™ or Google Forms™, you are comfortable with. Gain your users' trust with a professional user experience, while still being scrappy. ➤ Supports Wordpress, Squarespace, Bootstrap and other content management systems Formfacade supports content management systems (CMS) such as Wordpress and Squarespace out-of-the-box. If you have built a web app that uses bootstrap theme, we support that too. You just have to copy paste 1-line of code to embed the form into your website. Your Google Forms™ will automatically match the color scheme of your website. ➤ Create microsite and share it on email and social media Don't worry if you don't have a website or if you are not a website admin. You can create a microsite for forms and share it with your users on email or on social media. No more docs.google.com url. ➤ Prefill your form even if it is embedded in your website You can create the prefill url from Google Forms™ and use the same query string in the webpage that embeds the Formfacade form. Formfacade will automatically read your webpage url and prefill the form appropriately. You can also send emails that prefills values differently for each user. ➤ Analyze where users are dropping off using session recording tools Google Forms™ embedded in your website can't be analyzed using session recording tools. This is critical for forms with multiple sections. Formfacade allows you to analyze user behaviour and see where they are dropping off using session recording tools like FullStory or Hotjar. PRICING: Formfacade's Embed in website addon is a paid product with a free plan. You get: ➤ 20 responses per month in the free plan. ➤ Paid plan with advanced features like customization starts at $8 for 100 responses per month. Visit our website using the link below to learn about the customization features or write to support@formfacade.com for questions.