Add a feature that allows the context element of a page component to be "optional"

It pretty common for components to exist under certain conditions, but to be absent in others. To model this sort of "optional" component, we should allow for the specification of an optional element as context. Currently, I think it's possible to specify an optional context element, but the base component implementation lack methods to realize "optional" component behavior.