Make all of the buttons and fields on the FRQ Editor Page fully functional. Venkata will implement the save button's functionality after this PR is complete, so don't do that. Focus on local FRQ editing functionality.
To start, on the left of the footer, make the FRQ name and visibility status uneditable. These should be converted to plain text displays. It's cleaner to keep visibility status and name editing in the Admin Dashboard. This page should just display that information. Make sure to fetch it from Firebase and display it accordingly.
Implement FRQ and Question adding and modification. This should all work with the FRQ data model and example data sets. Make sure the time limit editor works as well. Implementations should resemble the UI mockups.
The "preview" button's functionality is not required this week.
Acceptance Criteria:
Make all of the buttons and fields on the FRQ Editor Page fully functional. Venkata will implement the save button's functionality after this PR is complete, so don't do that. Focus on local FRQ editing functionality.
To start, on the left of the footer, make the FRQ name and visibility status uneditable. These should be converted to plain text displays. It's cleaner to keep visibility status and name editing in the Admin Dashboard. This page should just display that information. Make sure to fetch it from Firebase and display it accordingly.
Implement FRQ and Question adding and modification. This should all work with the FRQ data model and example data sets. Make sure the time limit editor works as well. Implementations should resemble the UI mockups.
The "preview" button's functionality is not required this week.
Acceptance Criteria: