LATER [#B] I will publish this after tweaking and adding the configuration after completion some day because it is not yet completeand there are hyprlinks to be added When I first came into the world of neovim and started tweaking it, I found so many things that weren't mentioned clearly and specifically, I grew and passed myself through so many pitfalls(and believe me, there are a lot of them) that now if someone would say me to rewrite my config, I can do it. It is now in my veins. The beauty of this setup is that it is an ever changing landscape, so things changed very fastly. I too followed basic setup tutorials and blog posts for setting up my config, but to be frank, it never felt like me, I changed things up but at sometime or the other, things would just break(once lsp setup did, then the theme had few issue, I was a novice, don't judge !) and I would end up writing the whole config again. Throughout this amazing struggle I always felt the need of an advanced setup, which to be frank, they were not available anywhere. Hence, I created this series of configuration blogs. When I grew with neovim, I took bits and pieces from here and there, understood the code and combined to make my config. I don't want this for anyone else. There was no common archive where things would sum up. I saw people updating their blogs yearly to maintain relevency, single config transformed into various lua files, null-ls was changed by conform and mason, blogs changed but just the bare minimum to maintain relevent, I will try my best to maintain this series too, but I don't promise. Someday, it will also become autdated, people will move on and so will I, So sit back and read the making of an IDE.

Disclaimer!!

This is not your CV selection process and I don't care if it matches with the writing style of the world, I wouldn't be telling things fast, I wouldn't be writing bullet points to be concise. If you want a quick setup, go away, if you want things to just work without understanding what they do, go away, if you think this blog is not your type, go away!!
I grew with neovim in my screen I airn't be hurrying, it is an archieve/journey or whatever you may like to call it. And I should say that this blog will tell the basic setup, but it is not stopping there only, actually you can also think of it as a course.
I will tell how I did the things, I will also discuss alternatives whereever necessary to do so, you can follow to setup or branch off from references to make your config, the software is all yours.

Learn Lua!!

I am not going to lie, and if you have gather the courage to read past that disclaimer, I am also not going to send you away. When I started customizing lua, I hadn't even started coding. See, this the magic, you might have thought, at least that you want to get into using neovim because you love the concept, when I started, I didn't even properly knew that I would only be using it if I am thinking to code some day, yet just the idea of having such a good piece of software inside a terminal was enough to encourage me to play around with it, and it's what drived me into using TUI apps for almost all of my work. So, as a matter of fact, if you don't no lua, just see simply the basics of lua (ADD LINK) just so that you can start getting a better sense of this or else get ready to make your hands dirty.

Installing Neovim

Obviously, as you have seen the software somewhere, maybe downloaded it too, if not you can do so by following the official instructions(Add link) or even better, build it from source.(ADD LINK)

I find it of extreme importance that you should always be aware of a few things you are using. So, welcome to the history class, oh no no, I wouldn't be teaching it all day.So, vi is one of the primitive text editors which came into existance somewhere near the creation of linux itself, It was later improved by (ADD NAME), into vim, which further had a descendant named Neovim, what's the difference? Just the extension of capabilities, in vim and later addition of lua programming language to manage configuration better and more robustly in neovim rather than using Vimscript for the purpose.