Having a Shared Component Library for the Apum?

It's one c i work flow for the ap and the marketing site. Since they are in separate directories, we do run a like a deaf check. So that speeds up the the deployment of the apum. There are some nice areas where having the c i shared make sense. But it can also be frustrating. We just launched a new templet gallery where you can on the marketing sit andit's,. it's static, next to us pages for each templet. And so yet, when we launched the static marketing site, we did take out the live demo portion. That was made easy by the fact that it's a shared component library.