diff --git a/content/about.md b/content/about.md index 5c71c27..e8a13b5 100644 --- a/content/about.md +++ b/content/about.md @@ -4,7 +4,5 @@ active: About type: page --- -# About - - [Charter](/charter/) - [Roadmap](/roadmap/) diff --git a/content/sponsors.html b/content/sponsors.html index f5af942..ffe921a 100644 --- a/content/sponsors.html +++ b/content/sponsors.html @@ -5,53 +5,62 @@
-

Sponsoring Neovim development

-
-
How can I sponsor Neovim?
-
-

- You can sponsor Neovim via GitHub Sponsors - or Open Collective. - This makes it possible for core developers to work full-time for - a month or longer, accelerating projects like Lua stdlib, treesitter - parser engine, LSP framework, extended marks, embedded terminal, job - control, RPC API, and remote UIs. +

Sponsor Neovim

- Sponsorship is very rarely used to maintain (very minimal) infrastructure - costs for the Neovim project, such as hosting fees. 99.999% of the funding goes directly to funding - development work. -

-
-
How are funds dispersed?
-
-

- Donations are managed via Open Collective, which - provides public tracking for all - expenses. Bitcoin transactions are visible - on the blockchain - explorer. The only donation options for neovim are via GitHub sponsors, Open Collective, and - Bitcoin. All prior funding sources have been transferred into Open Collective. -

-
-
What is expected of a contributor doing funded work?
-
-

- Funded work is a way to support active contributors who have weeks of time to focus on the - project. This opportunity is available to contributors who have a developed a reputation for - reliable, high-quality contributions (code/documentation, GitHub review comments, and GitHub - technical discussions; not IRC or other "ephemeral" places). +

+ Donate to Neovim +

- It works like this: funded contributors are expected to focus full-time for weeks or - even months, yielding tangible, high-quality contributions, with conspicuous, reliable, - regular activity on GitHub. -

-
+

100% of funds go to development

+

We don't have an "administrative" staff. Funding goes directly to software development.

+ +

Funds are managed by OpenCollective

+

+ Email: admin@neovim.io
+ Open Source Collective 501(c)(6)
+ EIN: 82-2037583
+ 440 N Barranca Ave #3939 Covina, CA 91723 United States
+ hello@oscollective.org
+ Details
+

+ +

+ You can also donate via GitHub Sponsors, + which will be routed to OpenCollective. +

+ +

How are funds used?

+

+ Funding makes it possible for core developers to work full-time for + a month or longer, accelerating projects like Lua stdlib, treesitter + parser engine, LSP framework, extended marks, embedded terminal, job + control, RPC API, and remote UIs. +

+ +

+ We have minimal infrastructure costs, which are funded from + non-sponsor sources such as the Store. + Those sources are routed to OpenCollective, so expenses will show up in OpenCollective. +

+ +

What is expected of a funded contributor?

+

+ Funded work is a way to support active contributors who have weeks of time to focus on the + project. This opportunity is available to contributors who have a developed a reputation for + reliable, high-quality contributions (code/documentation, GitHub review comments, and GitHub + technical discussions; not IRC or other "ephemeral" places). +

+ +

+ It works like this: funded contributors are expected to focus full-time for weeks or + even months, yielding tangible, high-quality contributions, with conspicuous, reliable, + regular activity on GitHub. +

-
-

Sponsors

+

Sponsors

-

Original fundraiser sponsors

+

Original fundraiser sponsors

diff --git a/layouts/index.html b/layouts/index.html index 16b44d4..cd4b761 100644 --- a/layouts/index.html +++ b/layouts/index.html @@ -50,10 +50,10 @@

Usable

semantic code inspection and refactoring (go-to definition, "find references", format, …).
  • - Client-server architecture allows you to detach the UI and keep the editor session running - (like tmux). Attach multiple UIs to any Nvim session. + Client-server architecture allows you to :detach + the UI and keep the editor session running (like tmux). Attach multiple UIs to any Nvim session.
    • -
  • No "Press ENTER" messages.
    • +
  • No "Press ENTER" messages (Nvim 0.12 feature).
  • Works the same everywhere: one build-type, one command.
  • Modern terminal features such as cursor styling, focus events, bracketed paste.
  • Builtin :terminal set the standard for @@ -117,7 +117,7 @@

    Impressions

    "Full-screen Neovim looks cool as hell!" - —DHH + —DHH

    "A nice looking website, that’s one thing Neovim did right." @@ -143,18 +143,20 @@

    Intro

    Chat

    @@ -195,13 +197,11 @@

    GUIs

    • - \ No newline at end of file + diff --git a/layouts/partials/whatisnvim.html b/layouts/partials/whatisnvim.html index 1492426..a39af55 100644 --- a/layouts/partials/whatisnvim.html +++ b/layouts/partials/whatisnvim.html @@ -18,7 +18,11 @@

    Discuss

    Visit #neovim:matrix.org or #neovim on irc.libera.chat to chat with the team.

    -

    - +

    + +
    + Mastodon +
    + Bluesky

    diff --git a/static/doc2/README.md b/static/doc2/README.md index feb04c6..a33b42f 100644 --- a/static/doc2/README.md +++ b/static/doc2/README.md @@ -1,3 +1,5 @@ -This folder is destined to be crawled by https://github.com/neovim/doc/ and not -served directly. -You must set the `canonical_url: doc/XXXX` to the front matter. +Files in `doc2/` are pulled into https://github.com/neovim/doc/ by +[this script](https://github.com/neovim/doc/blob/4ab2e06af98dadbd35c4282c1b18304d87f8eb59/ci/doc-index.sh#L10-L13). + +This is because `neovim.io/doc/` is served by https://github.com/neovim/doc/ +which is where the user documentation HTML is generated to.