October newsletter

[meenaxc]

No description provided.

[louwers]

This Markdown link is broken.

See Markdown syntax here: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax

[louwers]

Broken Markdown link.

[louwers]

Broken Markdown link.

[louwers]

I have formatted the Markdown files with

npm run format

I also deleted some files that I think were committed by accident.

I left some comments.

[meenaxc]

Have made edits, please check!

[louwers]

Missing dot at the end of the sentence.

[louwers]

There are still some issues.

When copying Markdown from a GitHub comment, make sure to press 'Edit' first.

A few mistakes were likely introduced by just copying the text from the rendered HTML.

[meenaxc]

Pushed changes, please check

[louwers]

OK let me check and run the formatting.

[louwers]

Some of the Markdown links are broken again.

Markdown is also sensitive to formatting. For example, this:

- Kaushal Kumar Singh rewrote the Android build config from Groovy to the more modern Kotlin in [#2902](https://github.com/maplibre/maplibre-native/pull/2902).
-Support for..

Results in (note the missing space after -):

Instead of there being a separate bullet point.

The link to text-variable-anchor-offset in the MapLibre Style Spec that was in my submission is also still not there.

I'll push a commit to fix these, but please take a look at the syntax of Markdown: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax