feat: remove old plugins for snacks.nvim migration

Author: mehalter

src/assets/recipes/picker_theme.png

@@ -324,7 +324,7 @@ return {
 
 ### Extending Core Plugin Config Functions
 
-Many of our core plugins have additional code that runs during setup which you might want to extend. For this reason we have included our own modules in `require("astronvim.plugins.configs.X")` (replacing `X` with the plugin `require` string) that returns the AstroNvim default config function in each plugin specification that has a `config` function which can be easily called if you want to extend a plugin configuration. This is particularly useful if you want to do something like add rules to `nvim-autopairs`, add user snippets to `luasnip`, or add more extensions to `telescope` without having to rewrite our entire configuration function. Here is an example of adding the `media_files` Telescope extension:
+Many of our core plugins have additional code that runs during setup which you might want to extend. For this reason we have included our own modules in `require("astronvim.plugins.configs.X")` (replacing `X` with the plugin `require` string) that returns the AstroNvim default config function in each plugin specification that has a `config` function which can be easily called if you want to extend a plugin configuration. This is particularly useful if you want to do something like add rules to `nvim-autopairs` or add user snippets to `luasnip` without having to rewrite our entire configuration function. Here is an example of adding extending LuaSnip to use extend snippet filetypes:
 
 :::note
 
@@ -335,30 +335,27 @@ Not all plugins have custom `config` functions and will not have an `astronvim.p
 ```lua title="lua/plugins/extended_config.lua" {10-11}
 return {
   {
-    "nvim-telescope/telescope.nvim",
-    dependencies = { -- add a new dependency to telescope that is our new plugin
-      "nvim-telescope/telescope-media-files.nvim",
-    },
+    "L3MON4D3/LuaSnip",
     -- the first parameter is the plugin specification
     -- the second is the table of options as set up in Lazy with the `opts` key
     config = function(plugin, opts)
       -- run the core AstroNvim configuration function with the options table
-      require("astronvim.plugins.configs.telescope")(plugin, opts)
+      require("astronvim.plugins.configs.luasnip")(plugin, opts)
 
-      -- require telescope and load extensions as necessary
-      require("telescope").load_extension("media_files")
+      -- require luasnip and use it's API as normal
+      require("luasnip").filetype_extend("javascript", { "javascriptreact" })
     end,
   },
 }
 ```
 
 ## Disabling Plugins
 
-Plugins can be easily disabled by simply setting the `enabled` option to `false`. Here is an example of disabling the core dashboard plugin, `alpha`:
+Plugins can be easily disabled by simply setting the `enabled` option to `false`. Here is an example of disabling the core easy escape plugin, `better-escape`:
 
 ```lua title="lua/plugins/disabled.lua" "enabled = false"
 return {
-  { "goolord/alpha-nvim", enabled = false },
+  { "max397574/better-escape.nvim", enabled = false },
 }
 ```
 
@@ -390,7 +387,7 @@ return {
   },
 
   -- this plugin will be loaded on the autocmd event "UIEnter"
-  { "rcarriga/nvim-notify", event = "UIEnter" },
+  { "rebelot/heirline.nvim", event = "UIEnter" },
 }
 ```
 
@@ -445,10 +442,10 @@ return {
 
 AstroNvim has many plugins that we load on the first real file that is open. This is used internally for plugins like Treesitter, LSP related plugins, and other various plugins related to interacting with files. We achieve this by creating a custom `User` `autocmd` event called `AstroFile`. This can also be used by users for lazy loading plugins on the first real file that is opened:
 
-```lua title="lua/plugins/indent-blankline.lua" {4}
+```lua title="lua/plugins/illuminate.lua" {4}
 return {
   {
-    "lukas-reineke/indent-blankline.nvim",
+    "RRethy/vim-illuminate",
     event = "User AstroFile",
   },
 }

src/assets/recipes/telescope_theme.png

@@ -30,7 +30,7 @@ AstroNvim is an aesthetically pleasing and feature-rich neovim config that is ex
 - A clipboard tool is necessary for the integration with the system clipboard (see [`:help clipboard-tool`](https://neovim.io/doc/user/provider.html#clipboard-tool) for supported solutions)
 - Terminal with true color support (for the default theme, otherwise it is dependent on the theme you are using) <sup>[[2]](#2)</sup>
 - Optional Requirements:
-  - [ripgrep](https://github.com/BurntSushi/ripgrep) - live grep telescope search (`<Leader>fw`)
+  - [ripgrep](https://github.com/BurntSushi/ripgrep) - live grep file search (`<Leader>fw`)
   - [lazygit](https://github.com/jesseduffield/lazygit) - git ui toggle terminal (`<Leader>tl` or `<Leader>gg`)
   - [go DiskUsage()](https://github.com/dundee/gdu) - disk usage toggle terminal (`<Leader>tu`)
   - [bottom](https://github.com/ClementTsang/bottom) - process viewer toggle terminal (`<Leader>tt`)
@@ -40,19 +40,20 @@ AstroNvim is an aesthetically pleasing and feature-rich neovim config that is ex
 :::note
 
 <sup id="1">\[1\]</sup> All downloadable Nerd Fonts contain icons which are used
-by AstroNvim. Install the Nerd Font of your choice to your system and in your terminal
-emulator settings, set its font face to that Nerd Font. If you are using AstroNvim
-on a remote system via SSH, you do not need to install the font on the remote system.
+by AstroNvim. Install the Nerd Font of your choice to your system and in your
+terminal emulator settings, set its font face to that Nerd Font. If you are
+using AstroNvim on a remote system via SSH, you do not need to install the font
+on the remote system.
 
 :::
 
 :::note
 
-<sup id="2">\[2\]</sup> When using default theme: For MacOS, the default terminal
-does not have true color support. You will need to use [iTerm2](https://iterm2.com/),
-[Kitty](https://sw.kovidgoyal.net/kitty/), [WezTerm](https://wezfurlong.org/wezterm/),
-or another [terminal emulator](https://github.com/termstandard/colors) that has true
-color support.
+<sup id="2">\[2\]</sup> When using default theme: For MacOS, the default
+terminal does not have true color support. You will need to use
+[iTerm2](https://iterm2.com/), [Kitty](https://sw.kovidgoyal.net/kitty/),
+[WezTerm](https://wezfurlong.org/wezterm/), or another [terminal
+emulator](https://github.com/termstandard/colors) that has true color support.
 
 :::
 
@@ -188,7 +189,7 @@ docker run -w /root -it --rm alpine:edge sh -uelic '
 - Autocompletion with [Cmp](https://github.com/hrsh7th/nvim-cmp)
 - Git integration with [Gitsigns](https://github.com/lewis6991/gitsigns.nvim)
 - Terminal with [Toggleterm](https://github.com/akinsho/toggleterm.nvim)
-- Fuzzy finding with [Telescope](https://github.com/nvim-telescope/telescope.nvim)
+- Fuzzy finding with [snacks.picker](https://github.com/folke/snacks.nvim/blob/main/docs/picker.md)
 - Syntax highlighting with [Treesitter](https://github.com/nvim-treesitter/nvim-treesitter)
 - Formatting and linting with [none-ls](https://github.com/nvimtools/none-ls.nvim)
 - Language Server Protocol with [Native LSP](https://github.com/neovim/nvim-lspconfig)

src/content/docs/configuration/customizing_plugins.mdx

@@ -181,45 +181,53 @@ AstroNvim generally relies on `<Leader>` driven mappings, which is default set t
 | Toggle Debugger UI      | `Leader + du`              |
 | Debugger Hover          | `Leader + dh`              |
 
-## Telescope Mappings
+## Picker Mappings
 
 | Action                            | Mappings             |
 | --------------------------------- | -------------------- |
 | Resume previous search            | `Leader + f + Enter` |
 | Marks                             | `Leader + f'`        |
+| AstroNvim config files            | `Leader + fa`        |
 | Buffers                           | `Leader + fb`        |
 | Word at cursor                    | `Leader + fc`        |
 | Commands                          | `Leader + fC`        |
 | Find files                        | `Leader + ff`        |
 | Find files (include hidden files) | `Leader + fF`        |
+| Git tracked files                 | `Leader + fg`        |
 | Help Tags                         | `Leader + fh`        |
 | Keymaps                           | `Leader + fk`        |
+| Lines                             | `Leader + fl`        |
 | Man Pages                         | `Leader + fm`        |
 | Notifications                     | `Leader + fn`        |
 | Old Files                         | `Leader + fo`        |
+| Old Files (current directory)     | `Leader + fO`        |
+| Projects                          | `Leader + fp`        |
 | Registers                         | `Leader + fr`        |
+| Smart (buffers,recent,files)      | `Leader + fs`        |
 | Colorschemes                      | `Leader + ft`        |
 | Live Grep                         | `Leader + fw`        |
 | Live Grep (include hidden files)  | `Leader + fW`        |
 | Git Branches                      | `Leader + gb`        |
 | Git Commits (repository)          | `Leader + gc`        |
 | Git Commits (current file)        | `Leader + gC`        |
+| Git browse (open)                 | `Leader + go`        |
 | Git Status                        | `Leader + gt`        |
+| Git Stash                         | `Leader + gT`        |
 | LSP Symbols                       | `Leader + ls`        |
 | LSP Workspace Symbols             | `Leader + lG`        |
 
 ## Terminal Mappings
 
-| Action                   | Mappings                |
-| ------------------------ | ----------------------- |
-| Open Floating Terminal   | `Leader + tf`           |
-| Open Horizontal Terminal | `Leader + th`           |
-| Open Vertical Terminal   | `Leader + tv`           |
-| Open Toggle Lazygit      | `Leader + tl`           |
-| Open Toggle node         | `Leader + tn`           |
-| Open Toggle Python       | `Leader + tp`           |
-| Open Toggle btm          | `Leader + tt`           |
-| Toggle Current Terminal  | `<F7>`                  |
+| Action                   | Mappings      |
+| ------------------------ | ------------- |
+| Open Floating Terminal   | `Leader + tf` |
+| Open Horizontal Terminal | `Leader + th` |
+| Open Vertical Terminal   | `Leader + tv` |
+| Open Toggle Lazygit      | `Leader + tl` |
+| Open Toggle node         | `Leader + tn` |
+| Open Toggle Python       | `Leader + tp` |
+| Open Toggle btm          | `Leader + tt` |
+| Toggle Current Terminal  | `<F7>`        |
 
 ## UI/UX Mappings
 
@@ -255,3 +263,4 @@ AstroNvim generally relies on `<Leader>` driven mappings, which is default set t
 | Toggle syntax highlighting (buffer)    | `Leader + uy`  |
 | Toggle LSP semantic tokens (buffer)    | `Leader + uY`  |
 | Toggle color highlighting              | `Leader + uz`  |
+| Toggle zen mode                        | `Leader + uZ`  |

src/content/docs/index.mdx

@@ -0,0 +1,78 @@
+---
+id: dashboard
+title: Dashboard Customizations
+---
+
+AstroNvim comes with [snacks.dashboard](https://github.com/folke/snacks.nvim/blob/main/docs/dashboard.md) by default for providing a dashboard/home screen. This page provides a few common customization options.
+
+### Customize Dashboard Header
+
+If you want to customize your header on the dashboard you can do this easily by overriding the `snacks.nvim` options in your plugins:
+
+```lua title="lua/plugins/dashboard.lua"
+return {
+  "folke/snacks.nvim",
+  opts = {
+    dashboard = {
+      preset = {
+        header = table.concat({
+          "My Custom",
+          "Dashboard Header",
+        }, "\n"),
+      },
+    },
+  },
+}
+```
+
+### Customize Buttons
+
+In order to customize buttons presented on the dashboard, you can modify `snacks.nvim` options:
+
+```lua title="lua/plugins/dashboard_buttons.lua"
+return {
+  "folke/snacks.nvim",
+  opts = {
+    dashboard = {
+      preset = {
+        keys = {
+          {
+            key = "h",
+            action = function()
+              vim.notify("Hello World!")
+            end,
+            desc = "Say Hi",
+          },
+        },
+      },
+    },
+  },
+}
+```
+
+### Open Dashboard Automatically When No More Buffers
+
+If you want to make the dashboard/home screen open automatically when you close the last buffer in your session you can add the following to your AstroCore mappings configuration:
+
+```lua title="lua/plugins/astrocore.lua"
+return {
+  "AstroNvim/astrocore",
+  ---@type AstroCoreOpts
+  opts = {
+    mappings = {
+      n = {
+        ["<Leader>c"] = {
+          function()
+            local bufs = vim.fn.getbufinfo({ buflisted = true })
+            require("astrocore.buffer").close(0)
+            if not bufs[2] then
+              require("snacks").dashboard()
+            end
+          end,
+          desc = "Close buffer",
+        },
+      },
+    },
+  },
+}
+```

src/content/docs/mappings.mdx

@@ -5,7 +5,7 @@ title: Detached Git Worktrees
 
 Some users prefer tracking their dotfiles in bare git repos which rely on setting a detached worktree to work. However, without a `.git` folder, it's difficult to tell whether a file is being tracked by a bare repo or not. Unfortunately, this also means that while editing dotfiles, it's not possible to see git diffs in the gutter or open lazygit in the correct repository — at least not without further configuration.
 
-AstroNvim provides an easy way to enable git integration when editing files within detached worktrees, allowing gitsigns gutter highlighting, lazygit toggleterm, and telescope mappings to work as you would expect them to.
+AstroNvim provides an easy way to enable git integration when editing files within detached worktrees, allowing gitsigns gutter highlighting, lazygit toggleterm, and picker mappings to work as you would expect them to.
 
 This functionality is opt-in. To enable it, configure AstroCore and set the `git_worktrees` option to an array-like table, where each entry represents a separate worktree with entries `toplevel` and `gitdir` specifying paths on your system.