We have a pretty strange requirement for a CMS. We don’t want our CMS to actually serve up pages to the end user, but instead need it to build out the completed page to a specific directory, where we will then sync (FTP most likely) to our e-commerce server to integrate with our main ecom site. The main thing is that end-users will never see a page directly served up from the CMS.
So… can EE be customized to use something like template Caching (or Dynamic Page Caching) to build out all publishable pages so they can be served up by a different HTTP server? And… can this process be set to build on demand when needed or build on a schedule? In then end, we need EE to manage the content and build the pages, but then hand the files off to a different web server to get served up.
Any insight would be greatly appreciated.
thanks!