wires/hypnagaga_old
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

formatting

Browse source
This commit is contained in:
madrilene 2024-02-08 10:40:47 +01:00
parent 7fc159319f
commit bb12da7ef2
2 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
src/docs/open-graph.md
View file

@ -26,14 +26,15 @@ The implementation is based on [Bernard Nijenhuis article.](https://bnijenhuis.n
If you want to be inspired, have a look at [what Lea is doing here.](https://lea.codes/posts/2023-04-25-pseudorandom-numbers-in-eleventy/)
Previously the images were created at build time, but this leads to not rendering the font - if the system executing the build has not installed it, it will not be generated.
Previously, the images were created at build time, but this leads to not rendering the font -- if the system executing the build has not installed the font, it will not be used.
A solution would be to always build the page yourself and then place it on the server directly. Or, as [Sophie Koonin does](https://github.com/sophiekoonin/localghost/blob/main/eleventy.config.js#L45-L47), explicitly specify the system to be used for the build and select a font that this system has installed by default.
A solution would be to always build the page yourself and then place it on the server directly.
Or, as [Sophie Koonin does](https://github.com/sophiekoonin/localghost/blob/main/eleventy.config.js#L45-L47), explicitly specify the system to be used for the build, and select a font that this system has installed by default.
At the moment I have relocated the creation of the images in the development process, so that the font only needs to be installed on your own system. The images are located in `src/assets/og-images` and are comitted.
This is fine as long as you only work with markdown and the font is always installed on your system, how this works with a CMS workflow remains to be seen.
This is fine as long as you only work with markdown and the font is always installed on your system. How this works if a CMS is involved remains to be seen :sweat_smile:.
Consider that the domain is a hard coded value in `src/common/og-images.njk`.
Consider that the domain is a hard coded value in the front matter in `src/common/og-images.njk`.
Let me know if you encounter any problems.

4
src/posts/2022-11-02-markdown.md
View file

@ -8,7 +8,7 @@ tags: ['markdown', 'feature']
A lot of markdown packages are installed to help you write your posts.
You can configure them in `config/plugins/markdown.js`.
As of my personal preference, there are some presets. For example the conversion of web pages to links (www.lenesaile.com) and the addition of `rel: 'noopener'` for external links (all links with the pattern `/^https?:/`).
As of my personal preference, there are some presets. For example the conversion of web pages to links (www.lenesaile.com) and the addition of `rel="noopener"` for external links (all links with the pattern `/^https?:/`).
**This is a tiny pitfall!**
Take care to not prefix your internal links with your domain, or else they will be treated ad external as well. To link internally use this pattern:
@ -113,7 +113,7 @@ Autoconverted link https://every-layout.dev/ (enabled via linkify)
([A reference for emoji markup](https://gist.github.com/rxaviers/7360908))
**Shortcuts (emoticons)**:
:-) :-( 8-) ;)
:-) :-( 8-) ;) :-P
## mark