Auto generate docs

Author: github-actions[bot]

doc/lazy-nix-helper.nvim.txt

@@ -12,6 +12,7 @@ Table of Contents                     *lazy-nix-helper.nvim-table-of-contents*
   - Configuration         |lazy-nix-helper.nvim-lazy-nix-helper-configuration|
   - NixOS Configuration|lazy-nix-helper.nvim-lazy-nix-helper-nixos-configuration|
   - Known Limitations |lazy-nix-helper.nvim-lazy-nix-helper-known-limitations|
+  - Alternatives           |lazy-nix-helper.nvim-lazy-nix-helper-alternatives|
   - Troubleshooting     |lazy-nix-helper.nvim-lazy-nix-helper-troubleshooting|
   - Development             |lazy-nix-helper.nvim-lazy-nix-helper-development|
 
@@ -441,6 +442,16 @@ That includes all the plugins that I use, but I think there are other package
 groups where neovim plugins can exist.
 
 
+ALTERNATIVES               *lazy-nix-helper.nvim-lazy-nix-helper-alternatives*
+
+Besides Lazy-Nix-Helper there are other tools and strategies you might choose
+to manage your neovim configuration under NixOS:
+
+- Home-Manager <https://nix-community.github.io/home-manager/> provides options for installing and configuring neovim plugins
+- NixVim <https://github.com/nix-community/nixvim/> is a neovim distribution built around Nix modules. It provides nix-style configuration options for every neovim configuration option as well as options for many plugins
+- Using your existing config as-is. Depending on how complicated your current config is and what it includes, you may be able to copy your dotfiles and have everything work out of the box. The main downside is that you lose the reproducability benefits of nix by using a different package manager
+
+
 TROUBLESHOOTING         *lazy-nix-helper.nvim-lazy-nix-helper-troubleshooting*