There's a lot of duplicated "error message" code at the moment. A global error notification deployment system would help resolve this.

A Store module can be created to deploy Snackbar messages to the user.

Some pages/links on the website exist, but are currently blank, 404, or otherwise incomplete. Links to these pages should either be removed or the pages themselves should be modified to have a "Work in progress" message.

• "Join The Club" page
• "Donate" page
• "Contact Us" page
• "Account" page

If the "Login" button is in the "More" dropdown (i.e., on smaller screens), then when the user clicks it, the pop up opens briefly and immediately closes. This is because the source LoginLogoutPopupButton element is removed from the DOM.

The best fix is likely to move the LoginLogoutPopupButton outside of the dropdown and link it's visibility via v-model to a variable.

App.vue contains a <Suspense> for Page.vue, which is responsible for fetching account information from the API. If these requests ever fail, the <Suspense> never resolves, and the screen says loading forever. Possible scenarios where this could happen

• User is missing required permissions (i.e., user can't read their own ID or their own permissions).
• Server error (e.g. server unreachable).

This can be resolved by showing an error message when the Page.vue async methods throw an error.

Some navigation header buttons are missing or being shown at incorrect times. Specifically, what I have found so far is:

• Login/logout button does not appear in the dropdown.
• Buttons which should be hidden are shown in dropdown regardless.

Due to the login/logout button not being shown, this is high priority.

Typescript would probably be preferred over Javascript if we can get it working seamlessly.

The footer should be redesigned to include more information and probably be more block-like. Specifically, things which should be added:

• Mailing address
• "An RCOS Project"
• GitHub links

vue-apollo doesn't behave when fetching data during SSR. There are workarounds for this until this issue is fixed.
See vuejs/apollo#585

The navigation menu at the moment has a hard-coded structure based on screen size. As a result, not only is it harder to maintain and has duplicate code, but also means that if we want to show/hide various buttons based on user permissions, the menu will appear different.

This should probably be solved by first calculating the list of visible menu options, and then dynamically calculating which should be displayed and where based on size.

When switching from a "plain-layout" page to a "wave-layout" page, the wave at the top of the page briefly blinks.

Caused by ced5e8c.

Some groundwork has been laid for the admin tables in the dashboard in the Groups page, however it's not complete, and it needs to be standardized for all dashboard table pages. Ideally, there would be one component which takes in set(s) of properties that can be created/edited/displayed/etc.

The direction of this issue has been changed to instead focus on creating unique tables for each data type. While this may involve more repetition within code that seemingly serve the same purpose, each data type needs to be represented in vastly different ways. Creating unique components for each type seems to make the most sense (at least in the short term). Thus, this issue is now focused on only getting dashboard pages completed for the core data types:

• Images
• Productions
  • Production Images
  • Production Videos
  • Production Categories
  • Production RSVPs
• Stream
• Videos
• Groups
  • Group Permissions
• Users
  • User Permissions
  • User Groups
• People
  • People Roles
  • People Images
• Roles
• Logs
• Categories

Testing has fallen behind due to uncertainties in how things would change. I think everything is on track now, so testing should start back up and CI should be fixed.

There are a couple features which remain incomplete in PeopleList.vue, specifically:

• Linked Users
• Searching

Both of these features require work to be done on the backend first.