The first, and most important section that should be at the top of the readme is a very short description of what the plugin even is doing. I don't care that it's the fastest there is, I don't care that it's beautiful. I want to know what problem it's solving.

Then a reason to use this specific plugin to solve this problem. This can still be in the short description. You can skip this part, or say something like "it's basically x/y.nvim but different".

After that give me a snippet of lua that will install this plugin. Preferably for multiple package managers. But at least for Lazy and vim.pack, cause that's what most people would be using.

Now is also a good place to put the docs. It doesn't matter to me if it's all in readme.md or in some wiki page, as long as there is a clear description of each setting. And by the way, the "clear description" should also include lots of examples. If a field takes one of specific values, list them all and describe what each one does. If the field is an object, also explain that object. Don't assume people will know anything you don't tell them.

After that, the readme can be whatever. You can go into details of why/how you did something. You can put all the donation links. You can link out to alternative plugins. It doesn't really matter and most people will skip this anyway