I*can deal with that. However I would like to know the rationale behind it because what you say does not make much sense to me and the whole
https://github.com/kovidgoyal/calibr...ze/profiles.py looks mostly ten years old after which new profiles more or less stopped being added. I really fail to see how Kindle is that special from say Pocketbook (periodicals without navbar are perfectly usable on both).
I think it would deserve a cleanup (fbsizes seem to be a function of fbase, some profile do not inherit from each other like KindleDXOutput not inheriting from output profile etc.). However, since new profiles are not being added, it would make sense to allow users to "create" their own profile. A generic profile where they could fill in dpi and screen size etc. I include a mockup.
That would easily accomodate making navbar (and date in title) optional (now, some recipes set no_inline_navbars to True, for example, but should this really be left to recipe authors?)
I would be willing to implement these changes and I do not really see much downsides to it. People with modern e-ink devices are just puzzled by the current design as they typically cannot find their device there anyway.