...
Lynicon is not a platform, or 'box' in which to put things, in the sense that most CMSs are. ASP.Net MVC Core remains the platform on which you are building your site, and Lynicon does not interfere with that or stop you doing anything in the normal MVC way. This means since Lynicon is a tool, you can add it to an existing MVC ASP.Net Core project, use it to only provide content management to a subset of pages, you can even use Lynicon as an editor frontend for existing database tables.
...
An essential part of allowing Lynicon to be retrofitted to an existing MVC ASP.Net Core site is that it does not rely on any of MVC's the extension points by, for instance, changing any of the default service classes like model binding, view engine, etc. and so therefore it will not break any usage by a client application of these extension points.
...
Lynicon lets you use your existing platform skills by avoiding the tendency of CMSs to rebuild features their platforms already do perfectly well. This allows the work taken to build Lynicon to be focussed in areas that are actually useful. For instance, it has no 'web part' system as ASP.Net MVC Core already has all the tools you need to reuse elements of presentation, and actually does this much better than most of the other options. It doesn't have its own system for building content types, you simply use standard .Net classes (with a few limitations) and it does the rest.