From 1ea7a46e5731b83f5c6cc1ead8d9915cf4617252 Mon Sep 17 00:00:00 2001 From: Serge Bornow Date: Mon, 5 Aug 2024 18:16:47 -0700 Subject: [PATCH 1/2] Update CONTRIBUTING.md - fixing a link, wording Excited to see this unframework framework as a long time (since 1998 coder) HTML appreciator. I wanted to learn about extensions but noticed a broken link that others might stumble upon. Consider rephrasing a question to invite a person to contribute their issue. (this can be ignored if you like). --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ee13fb903..a1a585e12 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,10 +3,10 @@ Thank you for your interest in contributing! Because we're a small team, we have ## Issues 1. Issues are the best place to propose a new feature. Keep in mind that htmx is a small library, so there are lots of great ideas that don't fit in the core; it's always best to check in about an idea before doing a bunch of work on it. -1. When proposing a new features, we will often suggest that you implement it as an [extension](https://htmx.org/extensions), so try that first. Even if we don't end up supporting it officially, you can publish it yourself and we can link to it. +1. When proposing a new features, we will often suggest that you implement it as an [extension](https://htmx.org/docs/#extensions), so try that first. Even if we don't end up supporting it officially, you can publish it yourself and we can link to it. 1. Search the issues before proposing a feature to see if it is already under discussion. Referencing existing issues is a good way to increase the priority of your own. 1. We don't have an issue template yet, but the more detailed your description of the issue, the more quickly we'll be able to evaluate it. -1. See an issue that you also have? Give it a reaction (and comment, if you have something to add). We note that! +1. Do you see an issue that you have? Give it a reaction (and comment, if you have something to add). We note that! 1. If you haven't gotten any traction on an issue, feel free to bump it in the #issues-and-pull-requests channel on our Discord. 1. Want to contribute but don't know where to start? Look for issues with the "help wanted" tag. From 76b30b5a8eda45c25a0e95bc132eb3768f4aaa45 Mon Sep 17 00:00:00 2001 From: Serge Bornow Date: Thu, 8 Aug 2024 17:28:13 -0700 Subject: [PATCH 2/2] Update CONTRIBUTING.md Removed change to grammar/style of writing back to original. Providing a more updated reference to extensions with greater detail. --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a1a585e12..873530251 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,10 +3,10 @@ Thank you for your interest in contributing! Because we're a small team, we have ## Issues 1. Issues are the best place to propose a new feature. Keep in mind that htmx is a small library, so there are lots of great ideas that don't fit in the core; it's always best to check in about an idea before doing a bunch of work on it. -1. When proposing a new features, we will often suggest that you implement it as an [extension](https://htmx.org/docs/#extensions), so try that first. Even if we don't end up supporting it officially, you can publish it yourself and we can link to it. +1. When proposing a new features, we will often suggest that you implement it as an [extension](https://github.com/bigskysoftware/htmx-extensions), so try that first. Even if we don't end up supporting it officially, you can publish it yourself and we can link to it. 1. Search the issues before proposing a feature to see if it is already under discussion. Referencing existing issues is a good way to increase the priority of your own. 1. We don't have an issue template yet, but the more detailed your description of the issue, the more quickly we'll be able to evaluate it. -1. Do you see an issue that you have? Give it a reaction (and comment, if you have something to add). We note that! +1. See an issue that you also have? Give it a reaction (and comment, if you have something to add). We note that! 1. If you haven't gotten any traction on an issue, feel free to bump it in the #issues-and-pull-requests channel on our Discord. 1. Want to contribute but don't know where to start? Look for issues with the "help wanted" tag.