Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

avoid markdown #45

Closed
r10s opened this issue Dec 16, 2019 · 4 comments
Closed

avoid markdown #45

r10s opened this issue Dec 16, 2019 · 4 comments
Projects

Comments

@r10s
Copy link
Member

@r10s r10s commented Dec 16, 2019

we should avoid markdown whereever possible for now.

the different uis do not support it and start supporting markdown opens a lot of possible issues and cornercases to think about.
also, the idea is to put some infos to device-chat - also here, messages currently do not support markdown.
seeing things badly formatted in the different uis can easily be considered as a bug,

links should be added just as plain text, android and ios already makes them clickable at least in messages. this also has the advantage that the user can "see" the link and type it in on another device.

@Simon-Laux

This comment has been minimized.

Copy link
Member

@Simon-Laux Simon-Laux commented Dec 16, 2019

the question is what parts are website and what parts are website.
IMO we could use plain yaml files without markdown and render the website from them and also parse them for the cargo package.

@missytake missytake added this to To do in Onboarding via automation Jan 7, 2020
@missytake

This comment has been minimized.

Copy link
Contributor

@missytake missytake commented Jan 8, 2020

@pabzm

This comment has been minimized.

Copy link
Contributor

@pabzm pabzm commented Jan 17, 2020

As far as I understood, we want to avoid markdown in the structured data (the front-matter part of each file). The content part can contain markdown as it is rendered by jekyll for the web.

@r10s

This comment has been minimized.

Copy link
Member Author

@r10s r10s commented Jan 17, 2020

The content part can contain markdown as it is rendered by jekyll for the web.

yip, as we have now sorted out which parts are for the apps (the frontmatter) and which for the web (the body), and as markdown in the frontmatter is somewhat unusual, i think we can close this issue.

@r10s r10s closed this Jan 17, 2020
Onboarding automation moved this from To do to Done Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.