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.

Sign up for GitHub

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

Jump to bottom

Markdown: Parsing and cleansing #12

Open
Illizian opened this issue Aug 9, 2020 · 3 comments
Open

Markdown: Parsing and cleansing #12

Illizian opened this issue Aug 9, 2020 · 3 comments

Comments

@Illizian
Copy link
Contributor

Illizian commented Aug 9, 2020

A few issues encountered within #11 this issue is to highlight the // TODO comment within packages/blog/src/remove-markdown.js to begin the conversation on refactoring to something like https://github.com/remarkjs/remark

This could provide cleansing via the remarkjs/strip-markdown plugin. It could also provide configurable linting and many other features.

Explore?
@shaunchurch
Copy link
Owner

shaunchurch commented Aug 9, 2020 •
edited
Loading

Definitely agree with this. Been looking at unified as a whole, and considering that perhaps we could allow the setup to support not just Markdown, but CSV, HTML, XML, YAML, JSON data sources as well.

@Illizian
Copy link
Contributor Author

Illizian commented Aug 9, 2020

Nice. Whilst I wouldn't condone such activities it certainly sounds sensible. Would unified provide all these, could it be made pluggable? Load static-fns and whichever parser you need? (Over engineering or?)

@shaunchurch
Copy link
Owner

Definitely over engineering. Markdown with the YAML front matter is plenty for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shaunchurch @Illizian