Add how-to use content_access_by_path to restrict access to content

[finnlewis]

It'd be good to add this as a how-to here https://docs.localgovdrupal.org/devs/how-to/

@willguv and @markconroy are up for collaborating on this.

[markconroy]

There's already a README.md in the module, are we sure we also need a docs page?

If this module is not part of LGD core and not added by default, it seems a little bit arbitrary to add a page for a random Drupal module? I'm also concerned that we end up having lots of pages of "stuff" in the docs site, some of which is more about "Drupal" than it is about "LGD".

[ekes]

I think the idea is for common LGD council websites requirements that can be solved by installing (and configuring) Drupal contrib, or LGD contrib modules.

So in this case a description of the two or three different ways that councils commonly divide up responsibility of the site content; and the suggested way of configuring the site to facilitate that.

[jpoesen]

I think you both make good points.

Especially since this is not and LGD-specific module, we probably should not have a dedicated documentation page.

But it would be a good idea to have a page that lists, as Ekes suggested, modules commonly installed in LGD projects, with a short explanation and perhaps link to README on github and (if available) link to d.o. docs page.

Parallel with that, an LGD docs section on common requirements and how to deal with them would work too.
Like "Here's how councils do content access control", and one of the approaches is content_access_by_path.

(I'm working on a docs template for hosting solutions / approaches. Not the same thing but similar)