Generate Exec list using LDAP positions API #376

Closed
opened 2022-01-06 14:24:53 -05:00 by n3parikh · 1 comment
Owner

Use the markdown blurb as is now, and use a placeholder if there's no blurb.

Use the markdown blurb as is now, and use a placeholder if there's no blurb.
n3parikh added the
Feature Request
Priority - Medium
labels 2022-01-06 14:24:53 -05:00
j285he added
Priority - High
and removed
Priority - Medium
labels 2022-01-06 14:55:59 -05:00
b72zhou self-assigned this 2022-01-19 20:50:39 -05:00
b72zhou was unassigned by a258wang 2022-01-19 20:52:17 -05:00
b72zhou was assigned by a258wang 2022-01-19 23:23:16 -05:00
Owner

Additional notes from our meeting on Jan. 19/2022:

  • LDAP can be used to get the names of the people in each exec position (president, vice president, etc.). Since (almost) everyone's headshots are named FirstnameLastname.jpg/png/etc., these names can be used to grab the image for each exec. See https://wiki.csclub.uwaterloo.ca/LDAP for some more information on LDAP, and/or look at the code for the Members page since that also uses LDAP.
  • We will continue to use the .md files in content/team/execs to store each exec's blurb, though we can change the file names/contents slightly as needed (eg. we can probably get rid of the numbers in the file names).
  • If an exec does not have a blurb (ie. a .md file does not exist for them), then we should display some kind of placeholder blurb. Unfortunately, there doesn't seem to be a good way to programmatically fetch a user's program or year though.
Additional notes from our meeting on Jan. 19/2022: - LDAP can be used to get the names of the people in each exec position (president, vice president, etc.). Since (almost) everyone's headshots are named `FirstnameLastname.jpg/png/etc.`, these names can be used to grab the image for each exec. See https://wiki.csclub.uwaterloo.ca/LDAP for some more information on LDAP, and/or look at the code for the Members page since that also uses LDAP. - We will continue to use the .md files in `content/team/execs` to store each exec's blurb, though we can change the file names/contents slightly as needed (eg. we can probably get rid of the numbers in the file names). - If an exec does not have a blurb (ie. a .md file does not exist for them), then we should display some kind of placeholder blurb. Unfortunately, there doesn't seem to be a good way to programmatically fetch a user's program or year though.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: www/www-new#376
No description provided.