How mawkler/nvim works
Configuration Layer (First Ring)
a. Basic Settings (init.lua, options.lua)
b. Key Mappings (keymaps.lua)
c. Auto Commands (autocmds.lua)
d. Commands (commands.lua)
Plugin Management Layer
• Lazy.nvim as the plugin manager
• It to both the core and the plugin layers
• Utils/lazy.lua as the configuration bridge
Feature Clusters (Outer Ring)
Plugins into functional groups:
a. UI/UX Enhancement Cluster:
• Theme Management (catppuccin.lua, onedark.lua)
• Status Line (feline.lua, statusline.lua)
• File Navigation (nvim-tree.lua, oil.lua)
• Visual Aids (indent-blankline, colorizer)
b. Development Tools Cluster:
• LSP Configuration (lsp.lua)
• Completion (cmp.lua)
• Debugging (dap.lua, dap-ui.lua)
• Git Integration (gitsigns.lua, neogit.lua)
c. Language Support Cluster:
• TreeSitter (treesitter folder)
• Language-specific configs (rust.lua, go.lua, typescript.lua)
• Snippets (snippets directory)
d. Editor Enhancement Cluster:
• Search/Navigation (telescope.lua, fzf.lua)
• Text Manipulation (surround.lua, comment.lua)
• Window Management (smart-splits.lua, windows.lua)
Utility Layer (Outer Edge)
• Utility modules (utils directory)
• Them to relevant components
Relationship between
• LSP configurations and language-specific settings
• TreeSitter and syntax highlighting
• Custom commands and their related plugins
A small section showing external dependencies
• Python support (neovim Python module)
• System requirements
• Optional external tools