Add description for /acs/systems #375
Conversation
|
I'd be interested to learn how it's deciding to use "Systems" with a caps "S" as the page title. There should certainly be a page title, and I think there might be circumstances under which we might want to set the page title to be different from the route/endpoint/etc. name. Is this the situation that we're talking about here? For example, devices/get should have the title "Get a Device" and ACS/users/create --> "Create an ACS User" |
| page: | ||
| title: Systems | ||
| description: Access Control Systems | ||
|
|
||
| /acs/systems/get: | ||
| page: | ||
| title: Get an ACS System | ||
| description: Get an ACS System | ||
|
|
||
| /acs/systems/list: | ||
| page: | ||
| title: List ACS Systems | ||
| description: List ACS Systems | ||
|
|
||
| /acs/systems/list_compatible_credential_manager_acs_systems: | ||
| page: | ||
| title: List Compatible Credential Manager ACS Systems | ||
| description: List Compatible Credential Manager ACS Systems |
There was a problem hiding this comment.
@DebbieAtSeam Can you suggest descriptions here? The page titles need to match what is in SUMMARY.md and will be used later to generate that section of SUMMARY.md.
The page descriptions are for SEO. We can't use the long form descriptions because they may be too long or contain markdown formatting.
I am somewhat concerned about duplicated content.
| ``` | ||
| /acs/systems | ||
| ``` |
There was a problem hiding this comment.
@DebbieAtSeam Thoughts on putting the route on the page somewhere? I don't like this format, but how else to show it?
For SEO we should have a page title. This adds the description but maybe we need
titletoo? It's defaulting to justSystems. This would be used later when we autogen the SUMMARY.md file.