-
Notifications
You must be signed in to change notification settings - Fork 1
add markdown file #101
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
base: master
Are you sure you want to change the base?
add markdown file #101
Conversation
Deploying with
|
| Latest commit: |
b41f393
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4782a3fb.platform-nan-dev-8sl.pages.dev |
component/markdown.jsx
Outdated
| import { Span, Color, P, Div } from './elements.jsx' | ||
| import { css } from '../lib/dom.js' | ||
| import { NavLink } from '../component/header.jsx' | ||
| import { NavLink } from './header.jsx' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
import { NavLink } from '../component/header.jsx'
import { NavLink } from './header.jsx'?? ce code compile ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
faut eviter autan que possible de lier les components entre eux, le headers doit pas creer des components generique reutiliser par markdown.jsx
| .warn{ | ||
| outline:1px dashed red; | ||
| padding:0.8rem; | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
je pense qu'il faut eviter les noms de class css trop generique si elle ne sont pas scoper dans une classe parente plus specifique.
| children, | ||
| ), | ||
| ]), | ||
| ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tu peu pre-compute une partie du code:
export const MTitle = Object.fromEntries(
['h1', 'h2', 'h3', 'h4', 'h5', 'h6'].map((el) => {
const decoration = <Span fg="red">{'#'.repeat(Number(el.slice(1)))}</Span>
return [el, ({ children, ...props }) => h(el, props, decoration, children)]
}),
)Mais je pense que c'est encore mieu de le generer en css directement, comme c'est fait ici: https://github.com/egoist/hack/blob/master/src/css/markdown.css#L91-L105
| ) | ||
|
|
||
| export const MItalicWord = ({ children, color, type }) => { | ||
| return ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
useless return, I do think a lot of this could be achieve with a class and :before :after elements too
| </Span> | ||
| </NavLink> | ||
| ) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
je suis pas convaincu de ce MLi, tu devrais le decouper en 3 components:
- Les LI
- Les Liens
- Le text
et eviter un truc aussi specifique
| .warn{ | ||
| outline:1px dashed red; | ||
| padding:0.8rem; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
padding en rem ca va pas gerer que l'allignement reste sur la grille de characters monospace (mode text quoi)
component/header.jsx
Outdated
|
|
||
| // prettier-ignore | ||
| const NavLink = (props) => <li> - <Link {...props} /></li> | ||
| export const NavLink = (props) => <li> - <Link {...props} /></li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pas sur que je trouve ca specialement intressant d'exporter ca plutot que de le copier / coller dans ce cas
create a markdown utility file for hep in design