Aidan Feldman
Aidan Feldman
I understand... just seems like a pretty big limitation, and one that doesn't require too much cleverness to work around.
@angela-tran discovered that this was due to the [`Cross-Origin-Opener-Policy` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy) being set to `same-origin` by our server. Not sure if relevant, but sharing just in case.
This also seems to come up for links to Markdown anchors, e.g. ```markdown [some other page](page.md#something) ```
> Is this a suggestion that policies become the primary organizing hierarchy instead of components? I believe he is suggesting that we go back to organizing by component within this...
> Maybe all the *Policy components should be organized under a 18F_Governance_Documents component. Agreed! See https://github.com/18F/cg-compliance/issues/148.
Need to look into it more closely, but seems to be taken care of already: https://github.com/concourse/autopilot
_Pretty_ sure Scrollspy can be used standalone, but that would be something to test: - https://github.com/twbs/bootstrap/blob/master/js/scrollspy.js - http://getbootstrap.com/customize/?id=5000ef8619d4208de45b Since Bootstrap docs don't make that explicit, would be good include in...
CSS classes in use that use styles from Bootstrap: - `.affix` - `.nav`
Just discovered that there's a site: https://certitude.readthedocs.io/ Would be great to link to that from the repository.
It's not, no. Not sure when I'll get around to it, but happy to accept a pull request getting it all ready!