How shadinmd/nvim works
Core Components (Central Layer)
• It to a "Configuration Manager" component (init.lua)
Configuration Layers (Surrounding the Core)
Create three main configuration groups:
a. Basic Configuration (Light Blue):
• Options (options.lua)
• Keymaps (keymap.lua)
• Utils (utils.lua)
b. Plugin Management (Green):
• LazyVim (lazyvim.lua) as the plugin manager
• Mason (mason.lua) for LSP/DAP management
Editor Enhancement Plugins:
• Treesitter (treesitter.lua)
• Autopair (autopair.lua)
• Formatter (formatter.lua)
• CMP (cmp.lua) for completion
UI Plugins:
• Theme (theme.lua)
• Lualine (lualine.lua)
• Nvim-tree (nvim-tree.lua)
• Trouble (trouble.lua)
Git Integration:
• Gitsigns (gitsigns.lua)
• Lazygit (lazygit.lua)
Search and Navigation:
• Telescope (telescope.lua)
Development Tools:
• LSP Progress (lsp-progress.lua)
• Markdown Preview (markdown-preview.lua)
• Todo (todo.lua)
External Dependencies (Bottom Layer)
• Node.js
• CMake
• FZF
• Ripgrep
• FD
• C Compiler
• Git
Plugin management flow
• How LazyVim manages plugin installation and loading
• Plugin dependencies and load order
Configuration loading sequence
• Initialization flow from init.lua
• Configuration precedence
System requirements
• Minimum Neovim version
• Required external tools
• Optional vs. required dependencies