Hello, I'm afraid we were a bit late getting the p...
# design-datahub-documentationp
prehistoric-dawn-23569
11/04/2022, 2:06 PMHello, I'm afraid we were a bit late getting the poll in front of our DataHub users, so we missed the deadline.
However, I've shared it with them now and there are a couple of concerns about dropping markdown support. Would it be OK to share here?
prehistoric-dawn-23569
11/04/2022, 2:10 PMThe main question that people had was: "What format(s) would be available for access via the API?"
One of the potential benefits for us of retrieving markdown would be that it can easily be converted to Wikitext, whereas plain text would be limiting and custom HTML might present more challenges.
g
gorgeous-optician-32034
11/04/2022, 6:41 PMSome kind of structure is very important for us in field descriptions. Added apologies for being late to the survey, but we do have some fields that are tricky to understand. We would have to move those explanations into tags, column-level lineage when that's possible, and (hopefully not) external links.
l
little-megabyte-1074
11/05/2022, 12:15 AM
Hi @prehistoric-dawn-23569 & @gorgeous-optician-32034! Thanks for sharing the feedback 🙂
Based on the survey results, we found there’s a large demand within the Community (and a wide variety of use cases!) to keep documentation stored in Markdown, so we will not be removing that support.
Any changes we make to the UI-based documentation editing experience will not require migrating away from Markdown storage.
CC: @brave-insurance-80044 @boundless-student-48844 @bulky-soccer-26729 please jump in if I’ve misspoken!