# \[✔️\] Markdown export **URL:** \ **Category:** Ideas & Features\ **Tags:** export\ **Created:** [March 5, 2021, 9:49am UTC](https://community.fibery.io/t/markdown-export/1424 "2021-03-05T09:49:04Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![freele](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/freele/32/1568_2.png) [@freele](https://community.fibery.io/u/freele)\ **Post date:** [March 5, 2021, 9:49am UTC](https://community.fibery.io/t/markdown-export/1424/1 "2021-03-05T09:49:04Z")
**Use cases** Export documents (or excerpts from the documents) in fibery. **Current workflow** Now I can do it either via the API or using some third-party services integrations (e.g. github issues are exported preserving markdown format). **Suggestions** - a button to export document as markdown ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 5, 2021, 1:19pm UTC](https://community.fibery.io/t/markdown-export/1424/2 "2021-08-05T13:19:19Z")
Export is implemented in latest release > [@CHANGELOG: August 5 / Export Document or Entity to Markdown, Notify People Action](https://community.fibery.io/t/changelog-august-5-export-document-or-entity-to-markdown-notify-people-action/1884): > > rolled_up_newspaper Export Document or Entity to Markdown Now you can export documents and entities into markdown. Find Export to Markdown in the right top corner. [CleanShot 2021-08-05 at 15.37.12@2x] What is exported? You will get an archive with a markdown file and all images. If an entity has several rich edit fields, all the fields will be added into a single markdown file. Cases: Now you can write an article in Fibery, export it into markdown, and quickly publish it on any platform,… ---
**Author:** ![seaotternerd](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@seaotternerd](https://community.fibery.io/u/seaotternerd)\ **Post date:** [August 5, 2021, 6:40pm UTC](https://community.fibery.io/t/markdown-export/1424/3 "2021-08-05T18:40:42Z")
Yay! Thanks for implementing this! The lack of markdown export was my last remaining major reservation about Finery. Is there a plan in the future to be able to export an entire workspace to markdown (so that you could export all entities without having to manually click on each one)? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 5, 2021, 6:48pm UTC](https://community.fibery.io/t/markdown-export/1424/4 "2021-08-05T18:48:01Z")
Sure, this was just a necessary first step. Next are: 1. Select entities in table view and export in batch 2. Export entire workspace (it will take longer to implement) ---
**Author:** ![seaotternerd](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@seaotternerd](https://community.fibery.io/u/seaotternerd)\ **Post date:** [August 6, 2021, 2:59am UTC](https://community.fibery.io/t/markdown-export/1424/5 "2021-08-06T02:59:53Z")
Fantastic! That’s great to hear! ---
**Author:** ![Holger\_Winkelmann](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/holger_winkelmann/32/1524_2.png) [@Holger\_Winkelmann](https://community.fibery.io/u/Holger_Winkelmann)\ **Post date:** [September 7, 2021, 3:54pm UTC](https://community.fibery.io/t/markdown-export/1424/6 "2021-09-07T15:54:51Z")
Please make it possible to import and export MD automatically to given backend machen, preferable as part of a git workflow. I.e. if a entity changed push a PR towards GitHub, or push a branch in plain git. May also the other way around to react on GH actions? ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [September 8, 2021, 12:49pm UTC](https://community.fibery.io/t/markdown-export/1424/7 "2021-09-08T12:49:17Z")
Thanks for sharing Holger, but I’m not sure that I understand the problem… If you could share more details, that would be super cool 🐸 ---
**Author:** ![Holger\_Winkelmann](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/holger_winkelmann/32/1524_2.png) [@Holger\_Winkelmann](https://community.fibery.io/u/Holger_Winkelmann)\ **Post date:** [September 8, 2021, 5:58pm UTC](https://community.fibery.io/t/markdown-export/1424/8 "2021-09-08T17:58:47Z")
@Polina_Zenevich sure no problem, tough this was clear enough… But in more details the Use case: As a user I want to eliminate manual and local data as much i can (may expect a full export as backup to run away from fibery, which is understandable as part of “fear management” but should not the main driver IMHO) In this context I would not like to have local zip download, which i need to manually un pack and copy and paste in another system, manually. I rather would prefer to configure a action which triggers at a change condition (or any other) and sends the object markdown “serialisation” towards a given “target” which might be: - a git repo - a S3 Endpoint - a API PR request API Call at Github / Gitlab This gives us the opportunity to start a action to build i.e. static pages via a trigger and a build publish pipeline. Hope this makes sense? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 19, 2021, 6:32am UTC](https://community.fibery.io/t/markdown-export/1424/9 "2021-12-19T06:32:43Z")