39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
# Markdown Authoring
|
|
|
|
You must update the site to support Markdown content in blog posts and microblog statuses.
|
|
|
|
- Use the [mdex](https://hex.pm/packages/mdex) to convert markdown into HTML
|
|
- [MDEx documentation](https://hexdocs.pm/mdex/MDEx.html)
|
|
- Keep all content markdown -> HTML in a new module in the `Web` boundary so that any later customizations to markdown to HTML conversion are applied throughout the site
|
|
|
|
- Use the existing `body` field of the `Schema.Post`. assume this content is already markdown
|
|
|
|
- Ensure that syntax highlighting is supported in codefences
|
|
- Use the catppuccin latte colorscheme
|
|
- Make sure support for the following languges is available:
|
|
- Elixir
|
|
- Erlang
|
|
- JavaScript (including React / JSX)
|
|
- TypeScript
|
|
- Bash
|
|
- HTML
|
|
- Markdown
|
|
- Lua
|
|
- JSON
|
|
- TOML
|
|
- SQL
|
|
- YAML
|
|
|
|
- Enable these extensions:
|
|
- strikethrough
|
|
- table
|
|
- autolink
|
|
- tasklist
|
|
- footnotes
|
|
|
|
|
|
You will need to update the blog show page, the status show page, the status index page, and the home page where recent statuses are shown.
|
|
|
|
Use components to reduced code duplication when possible.
|
|
|
|
If components are shared between multiple views create a new module in `lib/web/components/` for the components pertaining to a specific thing.
|