@@ -28,8 +28,8 @@ A demo is worth a thousand words — check it out at
28
28
29
29
## How sponsorship works
30
30
31
- New features first land in Insiders, which means that _ sponsors will have access
32
- immediately _ . Every feature is tied to a funding goal in monthly subscriptions.
31
+ New features first land in Insiders, so _ eligible sponsors have immediate
32
+ access _ . Every feature is tied to a funding goal in monthly subscriptions.
33
33
When a funding goal is hit, the features that are tied to it are merged back
34
34
into Material for MkDocs and released for general availability. Bugfixes are
35
35
always released simultaneously in both editions.[ ^ 1 ]
@@ -55,18 +55,25 @@ currently only available to sponsors._
55
55
56
56
## How to become a sponsor
57
57
58
- You can become a sponsor using your individual or organization's GitHub account.
59
- Just visit __ [ squidfunk's sponsor profile] [ 5 ] __ , pick any tier __ from
60
- $10/month__ , and complete the checkout. Then, after a few hours, @squidfunk will
61
- add you as a collaborator to the super-secret private GitHub repositority
58
+ You can become an eligible sponsor with your individual or organization's GitHub
59
+ account. Visit __ [ squidfunk's sponsor profile] [ 5 ] __ , pick any tier __ from
60
+ $10/month__ [ ^ 2 ] , and complete the checkout. Then, after a few hours, @squidfunk
61
+ will add you as a collaborator to the super-secret private GitHub repositority
62
62
containing the Insiders edition, which contains all [ brand new and exclusive
63
63
features] [ 4 ] .
64
64
65
65
__ Important__ : If you're sponsoring @squidfunk through a GitHub organization,
66
66
please send a short email to
[email protected] with the name of your
67
- organization and the account that should be added as a collaborator.[ ^ 2 ]
67
+ organization and the account that should be added as a collaborator.[ ^ 3 ]
68
+
69
+ You can cancel your sponsorship anytime.[ ^ 4 ]
68
70
69
71
[ ^ 2 ] :
72
+ Note that $10/month is the minimum amount to become eligible for Insiders.
73
+ If you sponsor with a lower amount, it's still very much apprecaited, but
74
+ you won't be granted access to Insiders. Custom amounts of $10+ are also eligible.
75
+
76
+ [ ^ 3 ] :
70
77
It's currently not possible to grant access to each member of an
71
78
organization, as GitHub only allows for adding users. Thus, after
72
79
sponsoring, please send an email to
[email protected] , stating which
@@ -79,16 +86,14 @@ organization and the account that should be added as a collaborator.[^2]
79
86
private Insiders GitHub repository, and grant access to all members of the
80
87
organizations.
81
88
82
- You can cancel your sponsorship anytime.[ ^ 3 ]
83
-
84
- [ ^ 3 ] :
89
+ [ ^ 4 ] :
85
90
If you cancel your sponsorship, GitHub schedules a cancellation request
86
- which will become effective at the end of the billing cycle, which ends at
87
- the 22nd of a month for monthly sponsorships. This means that even though
88
- you cancel your sponsorship, you will keep your access to Insiders as long
89
- as your cancellation isn't effective. All charges are processed by GitHub
90
- through Stripe. As we don 't receive any information regarding your payment,
91
- and GitHub doesn't offer refunds, sponsorships are non-refundable.
91
+ which will become effective at the end of the billing cycle. This means
92
+ that even though you cancel your sponsorship, you will keep your access to
93
+ Insiders as long as your cancellation isn't effective. All charges are
94
+ processed by GitHub through Stripe. As we don't receive any information
95
+ regarding your payment, and GitHub doesn 't offer refunds, sponsorships are
96
+ non-refundable.
92
97
93
98
[ :octicons-heart-fill-24:{ .mdx-heart }   ; Join our <span class =" mdx-sponsorship-count " data-mdx-component =" sponsorship-count " ></span > awesome sponsors] [ 5 ] { .md-button .md-button--primary .mdx-sponsorship-button }
94
99
@@ -272,14 +277,27 @@ your `GH_TOKEN` to users.
272
277
273
278
[ 34 ] : ../publishing-your-site.md#github-pages
274
279
280
+ ### Payment
281
+
282
+ _ We don't want to pay for sponsorship every month. Are there any other options?_
283
+
284
+ Yes. You can sponsor on a yearly basis by [ switching your GitHub account to a
285
+ yearly billing cycle] [ 35 ] . If for some reason you cannot do that, you could
286
+ also create a dedicated GitHub account with a yearly billing cycle, which you
287
+ only use for sponsoring (some sponsors already do that).
288
+
289
+ One-time payments are not eligible for Insiders.
290
+
291
+ [ 35 ] : https://docs.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
292
+
275
293
### Terms
276
294
277
295
_ We're using Material for MkDocs to build the developer documentation of a
278
296
commercial project. Can we use Insiders under the same terms and conditions?_
279
297
280
298
Yes. Whether you're an individual or a company, you may use _ Material for MkDocs
281
299
Insiders_ precisely under the same terms as Material for MkDocs, which are given
282
- by the [ MIT license] [ 35 ] . However, we kindly ask you to respect the following
300
+ by the [ MIT license] [ 36 ] . However, we kindly ask you to respect the following
283
301
guidelines:
284
302
285
303
- Please __ don't distribute the source code__ of Insiders. You may freely use
@@ -290,7 +308,7 @@ guidelines:
290
308
- If you cancel your subscription, you're removed as a collaborator and will
291
309
miss out on future updates of Insiders. However, you may __ use the latest
292
310
version__ that's available to you __ as long as you like__ . Just remember that
293
- [ GitHub deletes private forks] [ 36 ] .
311
+ [ GitHub deletes private forks] [ 37 ] .
294
312
295
- [ 35 ] : ../license.md
296
- [ 36 ] : https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository
313
+ [ 36 ] : ../license.md
314
+ [ 37 ] : https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository
0 commit comments