You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For issues like #3721 - it would be handy to know if we can link to somewhere for non-authors in the byline. Marcel isn't going to get an author page, but we could still link to /team#marcel-gerber
Technical notes
Currently we serialize anchor tags in the team page via the full title of the individual, e.g. dr-lars-yencken - so unless we want to include Lars' full title in the byline every time, we can't do a naive serialization to solve this problem.
This suggests we need some way of specifying a slug-friendly name for each of our team members.
For example, a page in the admin that allows us to set information in a table that tracks people, their name, their profile picture, their slug, etc.
This table would ideally be linked to our users table (if not the same thing) to potentially power an updates feed feature in the future.
Impact
Beyond fixing #3721, this will likely be a consideration when it comes time to converting the /team page to gdocs, either making that a fairly explicit/hard-coded template, or something that is generated more dynamically.
The text was updated successfully, but these errors were encountered:
Overview
For issues like #3721 - it would be handy to know if we can link to somewhere for non-authors in the byline. Marcel isn't going to get an author page, but we could still link to /team#marcel-gerber
Technical notes
Currently we serialize anchor tags in the team page via the full title of the individual, e.g.
dr-lars-yencken
- so unless we want to include Lars' full title in the byline every time, we can't do a naive serialization to solve this problem.This suggests we need some way of specifying a slug-friendly name for each of our team members.
For example, a page in the admin that allows us to set information in a table that tracks people, their name, their profile picture, their slug, etc.
This table would ideally be linked to our users table (if not the same thing) to potentially power an updates feed feature in the future.
Impact
Beyond fixing #3721, this will likely be a consideration when it comes time to converting the /team page to gdocs, either making that a fairly explicit/hard-coded template, or something that is generated more dynamically.
The text was updated successfully, but these errors were encountered: