Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team Page #38

Open
nishant-nayak opened this issue Oct 6, 2023 · 0 comments
Open

Team Page #38

nishant-nayak opened this issue Oct 6, 2023 · 0 comments
Assignees
Labels
backend Django related issues frontend Frontend (HTML, CSS, JS) related issues p1 Priority 1 tasks. Affects all users
Milestone

Comments

@nishant-nayak
Copy link
Member

nishant-nayak commented Oct 6, 2023

Migrate the existing Team Page into Corpus.

  • Use tabs for each SIG.
  • Within each tab, there should be 3 sections for:
    • Faculty
    • Core
    • Members
  • Use dummy data in dev environments to test changes. (use loaddata)
  • In production, faculty advisors will have to be added in by developers. Other users will go through an onboarding process.
  • Each user's entry should link to their own user page (with data filled in from ExecutiveMember model). Faculty will only be Users, so we won't have user pages for them.

Alumni will come in v0.5 milestone of the project.

@nishant-nayak nishant-nayak added backend Django related issues frontend Frontend (HTML, CSS, JS) related issues p1 Priority 1 tasks. Affects all users labels Oct 6, 2023
@nishant-nayak nishant-nayak added this to the v0.1 milestone Oct 6, 2023
This was referenced Feb 28, 2024
@yukitya-1811 yukitya-1811 linked a pull request Mar 12, 2024 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Django related issues frontend Frontend (HTML, CSS, JS) related issues p1 Priority 1 tasks. Affects all users
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants