Learn by example with this sample stack that creates a sample control section. See the Element API Reference for more info on control types and conditions. The only difference here is that you will use a
group-sub-module type as a top level as opposed to a
Stack Configuration Options
These are keys and values that are passed to
|id to store in database under
|Localized title to display under the stack selector.
|Using Cornerstones Element API to build out controls or a function that returns an array.
|Associative array which saves value data used in controls.
|Associative array with stylesheet id pointing to a URL. These are loaded in the head.
|CSS to be post processed by theme option configuration. These are loaded inline.
|Function to run when the stack is active and Theme Options is ready.
|Extend from the controls, css, and stylesheets of another stack.
When in relation to custom to non-custom. Non-custom means they are an X stacks (Integrity etc...) and you will always be creating a Custom Stack.
See something inaccurate? Let us know