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
re: pictures of lab members: how about fetching (if it exists) the picture from github? that would ensure most pictures are up there (without "pushing" lab members) and make it automated (for new members)
where the script is responsible for generating team/_*.md.
It's really easy to make this go one-way. Where this gets tricky is with preserving people's custom profile links, alternate social media, email addresses, deciding between a local embedded profile or using a link to an external page. Not impossible, but it means actually parsing the pre-existing markdown and that's likely to be buggy.
We could tell people that everything will be pulled from github, so e.g. if they want an email address listed they need to also make it public on github, and if they want to use a personal site they need to list it publically on github.
The text was updated successfully, but these errors were encountered:
We could tell people that everything will be pulled from github, so e.g. if they want an email address listed they need to also make it public on github, and if they want to use a personal site they need to list it publically on github.
yes, as i was reading your post, i though exactly about that option. That would be neat!
Originally posted by @jcohenadad in #21 (comment)
Given that we have our org-chart recorded on https://github.com/orgs/neuropoly/teams
it should be possible to generate most of
/team
. To make it easier to manage, we can useinclude
, e.g.:where the script is responsible for generating
team/_*.md
.It's really easy to make this go one-way. Where this gets tricky is with preserving people's custom profile links, alternate social media, email addresses, deciding between a local embedded profile or using a link to an external page. Not impossible, but it means actually parsing the pre-existing markdown and that's likely to be buggy.
We could tell people that everything will be pulled from github, so e.g. if they want an email address listed they need to also make it public on github, and if they want to use a personal site they need to list it publically on github.
The text was updated successfully, but these errors were encountered: