It would be nice to have a global index page. The guidelines are pretty difficult to search at the moment. I tried and failed to look up iterator best practices. There is a lot of iterator example code in the guidelines that have little or nothing to do with iterators, making them difficult to search.
In terms of implementing this, I noticed you're embedding some semantic info in A tags in # headers. You could add an attribute to it for tags, e.g.:
## <a name="SS-fct-def" tags="function,lambda,return type,template">F.def: Function definitions
You could then write a remark plugin to generate the actual index.
It would be nice to have a global index page. The guidelines are pretty difficult to search at the moment. I tried and failed to look up iterator best practices. There is a lot of iterator example code in the guidelines that have little or nothing to do with iterators, making them difficult to search.
In terms of implementing this, I noticed you're embedding some semantic info in A tags in # headers. You could add an attribute to it for tags, e.g.:
## <a name="SS-fct-def" tags="function,lambda,return type,template">F.def: Function definitions
You could then write a remark plugin to generate the actual index.