@pmueller88,
I think, before jumping into creating mega component one-time-use components, we can do something better. Let's think about cutting cost, enabling reusability and flexibility.
- Can we break down the creative into reusable components?
- Can a group of reusable components achieve the same outcome, based on the creative?
If we can strategically create components to shape up the marketing team's landing page, their team can be the ones who create the pages themselves, and since the marketer's components are flexible and robust, they should be able to add styles to whatever their heart contempts.
But... if you really need to create that mega component one-time-use component, then is my suggestion:
- Take inspiration from the AEM Core Components - Breadcrumb; the structure of this component is the way to organise your AEM Components.

- Create a component in /apps/my-project/components/*
- Create default script.html in the component structure.
- Create clientlib folder (with a clientCategory) in the same component structure; this will hold your CSS and JS.
- if editable template, then you can edit the page policy to include the clientCategory.
- if static template, then you can add the clientCategory within the customheadlibs.html andcustomfootlibs.html .
- create new page with the template, and drag the component into the page.
- done!