It is possible to find a way into the open-air maze with the OSM route planner x)

It is funny that someone mapped the maze completely.

Transition a CSS grid row from 0 to 1fr to get an accordion working :D
An Advantage is the text is already rendered for screen readers.

Wow I didn't think about it. It seems practical!

With a list with data-index attributes such as <li class="searchable" data-index="newtoncronintorphy.dorothea@gmail.com(121)644-5577">
and the snippet:

<script type="text/javascript">
var searchStyle = document.getElementById('search_style');
document.getElementById('search').addEventListener('input', function() {
  if (!this.value) {
    searchStyle.innerHTML = "";
    return;
  }
  // look ma, no indexOf!
  searchStyle.innerHTML = ".searchable:not([data-index*=\"" + this.value.toLowerCase() + "\"]) { display: none; }";
  // beware of css injections!
});
</script>

A simple CSS code to check bot messages on social media (mastodon).

La méthode est artisanale mais efficace : une bouteille percée à remplir avec un appât à base de bière, de sirop et surtout de vin blanc. Car l'abeille déteste, le frelon lui adore. Le piège est redoutable.

"C'est un gros trou de 10 mm pour faire rentrer le frelon asiatique. Il ne ressortira pas, il va être dedans , il va s'épuiser, il va boire ou se noyer", explique Frédéric Provost, chargé de mission environnement à la mairie.

Est-ce que cela cible uniquement le frelon?

1. use product instead of nested python for-loops
2. use the walrus operator for assignment expressions
3. use ternary conditional operator if the assignment is simple
4. use lambda function to define simple functions
5. use list comprehensions
6. leverage the Higher Order functions of python such as map and other iterable functions.
7. use union operators to merge dictionaries
8. use f-strings to format strings
9. use asteriks for unpacking iterables and destructuring assignment

It can be useful in some cases: to declare variables in the <template> directly.

If you are logged in or not, use the /home to display the landing page or the default page of a website.

Also, the logo should have the alt="home" as this is what the users of screen readers expect. See the second point of https://jessbudd.com/blog/screen-reader-usability-testing-observations

About design:

1. Less is more: the content will be more important
2. 5x5 rule: Maximum 5 lines of texte for a slide, and maximum 5 words per line.
3. Show, don't tell: group together, use size, color, font, bold, etc...
4. Fonts: Outfit, Montserrat, Lato, Fira, Roboto, Opan Sans, Poxima, Circular
5. Illustrations: Pixabay (https://pixabay.com/fr/), Unsplash (https://unsplash.com), stocksnap (https://stocksnap.io), Undraw (https://undraw.co)
6. Icons: Flaticon, TheNounProject (https://thenounproject.com/)
7. Figma or Adoe XD can help to create the slides

Clean code is not only concise code, but more importantly, it is readable. A rule of thumb when writing code, is to write code as if comments didn’t exist. The code should be self-explanatory.

• booleans should always have a prefix like "is", "has", or "was"

and other JS tips

Great tips indeed

Use classes on svg inner elements and animate them

const { length, 0: first, [length - 1]: last } = arr;

I was also struggling with it:
const multilineStrings = 'This is a\n' + 'multiline\n' + 'strings';
or
const multilineStrings = ['This is a', 'multiline', 'strings'].join('\n');
or
``const multilineStrings =This is a
multiline
strings`;

git config --global --add --bool push.autoSetupRemote true

So the branch will be set if it is not the case 👍
It needs git version 2.37.0 or superior.

1. Partir d'une base légère
2. Éliminer les FROM, RUN et COPY
3. Placer les fichiers modifiés souvent à la fin du build de l'image si possible
4. Utiliser le .dockerignore
5. "tout ce qui n’est pas essentiel au fonctionnement de mon programme n’a pas sa place dans mon image."

• Repo release: https://github.com/:owner/:repo/releases.atom
• Repo commits: https://github.com/:owner/:repo/commits.atom
• Repo tag: https://github.com/:user/:repo/tags.atom
• User activity: https://github.com/:user.atom

• aspect-ratio
• padding-bottom depending of the aspect-ratio
• css variables, but one dimension needs to be known:

  --aspect-ratio: calc(4/3);
  --height: 30vmin;
  --width: calc(var(--height) * var(--aspect-ratio));
  height: var(--height);
  width: var(---width);

1. Be consistent
2. Use ISO 8601 UTC dates
3. Make an exception for public endpoints instead of
4. Provide a health check endpoint: GET /health
5. Version the API
6. Accept API key authentication
7. Use reasonable HTTP status codes
8. Use reasonable HTTP methods
9. Use self-explanatory, simple names: Most endpoints are resource-oriented and should be named that way.
10. Use standardized error responses (the same error structure)
11. Return created resources upon POST
12. Prefer PATH over PUT: full update of a resource is rare
13. Be as specific as possible
14. Use pagination
15. Allow expanding resources

background-clip: padding-box to avoid overflow of the background if border-radius is set.