PfSense added the "V" as in view part of the MVC to the static pages. No API to my knowledge. Pages still static although they do have a unified design now.The "M" as in model is really useful to micro-managing service configuration and doing inline migrations vs. a single point config.xml migration plus the validation of data / integrity verification is a nice bonus.As for "C" that is where we implement the API parts as well as the flat UI ends where the views are rendered. It also acts as a middleware to broker with the backend.I think the whole problem started in 2015 with the pfSense 3.0 roadmap blog post[1]... APIs were shuffled to TNSR, where no GUI seems to be available. The crossover back to FreeBSD didn't happen, so CE was born and moved up the food chain as Plus. PHP was never removed, a framework never implemented. It's an interesting read in retrospect.The FreeBSD side is still quite active and has good fixes nowadays going into FreeBSD, something that was always a major problem in the days past (one that we were vocal about).I counted again today and from 271 static pages since the fork we have only 103 left. That doesn't sound like much but it is. It's a huge effort and worth the time.Cheers,Franco[1] https://www.netgate.com/blog/further-a-roadmap-for-pfsense
