~sircmpwn/harelang.org

24ee2f3c0fdb52337688f54d89006ff7a43caee6 — Amelia Clarke a month ago 064396d
Fix outdated links to documentation

Signed-off-by: Amelia Clarke <selene@perilune.dev>
M content/blog/2021-03-19-stdlib-development.md => content/blog/2021-03-19-stdlib-development.md +3 -3
@@ 71,9 71,9 @@ focus areas we're looking into now are:
</dl>

Take a look through the [stdlib tickets][0] to find work in your area of
interest, and [introduce yourself on IRC](/community), where you can meet the
people you'll work with, ask and answer questions, and get help finding things
to work on.
interest, and [introduce yourself on IRC](/documentation/community/), where you
can meet the people you'll work with, ask and answer questions, and get help
finding things to work on.

[0]: https://todo.sr.ht/~sircmpwn/hare?page=1&search=label%3A%22stdlib%22


M content/blog/2022-04-17-Chronology-in-Hare.md => content/blog/2022-04-17-Chronology-in-Hare.md +3 -3
@@ 519,9 519,9 @@ save the introduction for later.

---

We wish you well in your datetime endeavours. If you'd like to discuss
or contribute to chronology in Hare, [reach us on IRC](/community/), or
write to us at:
We wish you well in your datetime endeavours. If you'd like to discuss or
contribute to chronology in Hare, [reach us on IRC](/documentation/community/),
or write to us at:

- "Byron Torres" <b@torresjrjr.com>
- "Vlad-Stefan Harbuz" <vlad@vladh.net>

M content/blog/2022-04-25-Announcing-Hare.md => content/blog/2022-04-25-Announcing-Hare.md +2 -1
@@ 213,7 213,8 @@ Hare ports.

We hope that you'll like Hare. Our goal is to build a supportive community of
people helping each other build great programs in our language. Consider
[joining our community](/community) on IRC and our mailing lists on SourceHut.
[joining our community](/documentation/community/) on IRC and our mailing lists
on SourceHut.

Again, If you'd like to try Hare, check out the [installation procedure], then
the [tutorial][Hare tutorial]. Have fun!

M content/blog/2022-05-09-hare-ssh.md => content/blog/2022-05-09-hare-ssh.md +2 -2
@@ 930,7 930,7 @@ Himitsu. The next steps for expanding hare-ssh are:
SSH is a relatively small target for a cryptography implementation to aim for.
I'm looking forward to using it as a testbed for our cryptographic suite. If
you're interested in helping with any of these, [please get in
touch](/community)! If you're curious about Hare in general, check out the
[language introduction][intro] to get started. Good luck!
touch](/documentation/community/)! If you're curious about Hare in general,
check out the [language introduction][intro] to get started. Good luck!

[intro]: https://harelang.org/tutorials/introduction/

M content/blog/2022-06-03-Implementing-regular-expressions-in-Hare.md => content/blog/2022-06-03-Implementing-regular-expressions-in-Hare.md +1 -1
@@ 281,4 281,4 @@ programming!
[regex.ha]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/regex/regex.ha
[docs]: https://docs.harelang.org/regex
[swtch]: https://swtch.com/~rsc/regexp/regexp1.html
[community]: https://harelang.org/community/
[community]: /documentation/community/

M content/blog/2022-06-21-Safety-features.md => content/blog/2022-06-21-Safety-features.md +1 -1
@@ 407,7 407,7 @@ simpler than Rust. To add one to Hare will require paring it down to the
essentials and fitting it into our simpler language design. I'm pretty sure that
it can be done.

[a blog post]: https://harelang.org/blog/2021-03-30-future-research-areas/
[a blog post]: /blog/2021-03-30-future-research-areas/
[^2]: As for the fate of the other two features: closures were ruled out, and
  async I/O is done with poll and O\_NONBLOCK, similar to C.


M content/blog/2022-09-06-Cross-builds-with-Hare.md => content/blog/2022-09-06-Cross-builds-with-Hare.md +1 -1
@@ 136,7 136,7 @@ We've [always focused][1] on working hand-in-hand with third-party distributions
as the blessed means of distributing Hare to our users, and with their
cooperation, cross-compiling Hare programs couldn't be easier.

[1]: https://harelang.org/distributions/
[1]: /documentation/install/packaging.html

```
$ hare build -o main -t riscv64 main.ha

M content/blog/2022-11-04-Making-Hare-debuggable.md => content/blog/2022-11-04-Making-Hare-debuggable.md +1 -1
@@ 273,4 273,4 @@ would rely on DWARF to resolve addresses into file names and line numbers.
If you're interested in helping with any of these ideas, [please join us][5].
We would be pleased to have your help.

[5]: https://harelang.org/community/
[5]: /documentation/community/

M content/blog/2023-07-03-All-rabbits-welcome.md => content/blog/2023-07-03-All-rabbits-welcome.md +3 -2
@@ 25,9 25,10 @@ orientations, and all others besides. You are welcome in our community, as
equals, to learn, to participate, and to lead.

For details on our standards of conduct, and the means of enforcing those
standards, consult the [Code of Conduct](/conduct). If you have any questions,
please reach out to the [conduct mailing list][mailing list].
standards, consult the [Code of Conduct][coc]. If you have any questions, please
reach out to the [conduct mailing list][mailing list].

[coc]: /documentation/community/conduct.html
[mailing list]: mailto:~sircmpwn/hare-conduct@lists.sr.ht

The Hare maintainers

M content/blog/2023-08-28-Scaling-the-community.md => content/blog/2023-08-28-Scaling-the-community.md +4 -4
@@ 45,7 45,7 @@ as well as a top-level list of global maintainers: myself, Ember Sawady,
Sebastian, and Bor Grošelj Simić.

[MAINTAINERS]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/MAINTAINERS
[maintainer policy]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/docs/maintainers.md
[maintainer policy]: /documentation/process/maintainers.html

We have also standardized the way that maintainers work on their patch queues so
that we can communicate to each other more effectively the status of ongoing


@@ 128,7 128,7 @@ Changes to be discussed within the RFC framework will follow the process
outlined in the [RFC process document][rfc], wherein proposals are prepared and
submitted to the new hare-rfc mailing list for discussion.

[rfc]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/docs/rfc.md
[rfc]: /documentation/process/rfc.html

## Defining the BDFL role



@@ 146,7 146,7 @@ includes matters such as overseeing fiduciary responsibilities, setting the
long-term vision and planning for the project, and assigning rights and
responsibilities to other participants.

[bdfl]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/docs/bdfl.md
[bdfl]: /documentation/process/bdfl.html

This document also clarifies how best to make use of my resources such that they
can be leveraged efficiently when needed without introducing too many


@@ 168,7 168,7 @@ For these reasons, and to more clearly signal our values and expectations to new
community members, we introduced a [Code of Conduct][coc] and a committee of
three trusted community members to oversee conflict resolution:

[coc]: https://harelang.org/conduct/
[coc]: /documentation/community/conduct.html

- Drew DeVault
- Ember Sawady

M content/blog/2024-02-16-Hare-0.24.0-released.md => content/blog/2024-02-16-Hare-0.24.0-released.md +1 -1
@@ 8,7 8,7 @@ Hare's first versioned release, 0.24.0, was tagged and shipped today. 🎉 We ha
written up a new [release policy][0] for Hare to govern this and future
releases. Here's the rundown on how this is going to work.

[0]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/docs/release.md
[0]: /documentation/process/release.html

*New here? Hare is a systems programming language designed to be simple and
robust, using a static type system, manual memory management, and a minimal

M content/blog/2024-04-01-Introducing-for-each-loops-in-Hare.md => content/blog/2024-04-01-Introducing-for-each-loops-in-Hare.md +1 -1
@@ 66,7 66,7 @@ bigger changes to Hare. This is especially important for new language features
such as for-each. In the three revisions to the RFC, we found solutions for a
number of challenges.

[0]: https://git.sr.ht/~sircmpwn/hare/tree/master/item/docs/rfc.md
[0]: /documentation/process/rfc.html

First of all, there was the syntax question. Do we want `foreach`? Or should we integrate it
into `for`? We quickly reached the conclusion that it is best to introduce a new

M content/tutorials/introduction.md => content/tutorials/introduction.md +2 -1
@@ 19,7 19,8 @@ sections:
      rooms, and so on, and do not hesitate to ask for help, discuss your
      problems, and offer your knowledge and insights to others.

      Here are some quick links to our [community resources](/community):
      Here are some quick links to our
      [community resources](/documentation/community/):

      - [hare-users](https://lists.sr.ht/~sircmpwn/hare-users) is a great place
        to ask questions