prior to #23, looks like @Martmists is reporting CORS issues when interacting with the backend. We have never encountered this on Nuxt so this might be something you guys need to fix.

from what I can see the frontend is 100% clientside so that means you guys need to enforce the headers manually.

Mod Overview is currently placeholders, we need to make it handle live data now, its been long overdue on such.

White-labeling allows hosters to provide a service using our open source website. Some things we should allow via the admin for the webmaster are:

• Custom Logo
• Custom Colors
• Feature Toggling

Since we're going with the Server-Client layout, we need to ratify how we can make the mods easier to launch from the web client. A Protocol seems to do that for us and allows a agnostic approach to distribute mods.

Current RFC Spec

The server would be distributing this via sayonika:// <BASE_URL>/project/<PROJECT_ID>.

This is GraphQL-based to allow us to publish one common schema language, and promote flexibility on the API.

this is JSON-REST based and this is how our output would look like:

{
 "project_id": "19271726462637237",
 "cdn_url" : "https://cdn.sayoni.ca/project/19271726462637237/mod.tar.gz
}

Query Lang schema will still be drafted , will update issue once finalized

Seems the dialog does not POST. It fails with this error in the clientside

be7decef39e0c7def02b.js:1 TypeError: Cannot read property 'slice' of undefined
    at f.gridContent (4949efbd4ae29c7f75a3.js:1)
    at xn.get (be7decef39e0c7def02b.js:1)
    at xn.evaluate (be7decef39e0c7def02b.js:1)
    at f.gridContent (be7decef39e0c7def02b.js:1)
    at f.<anonymous> (4949efbd4ae29c7f75a3.js:1)
    at f.t._render (be7decef39e0c7def02b.js:1)
    at f.r (be7decef39e0c7def02b.js:1)
    at xn.get (be7decef39e0c7def02b.js:1)
    at new xn (be7decef39e0c7def02b.js:1)
    at t (be7decef39e0c7def02b.js:1)```

To load our pages faster, we will cache them clientside, and effectively turn our Frontend into a PWA. This will be done via Workbox.

Currently mod submit cards and mod overview cards overrides it as a page, the dialog should not be a page but a part of index that can be exited, so does submit-mod. It should be exitable when clicking to the dimmed screen space.

For this high priority TODO these are needed:

• Mod Submission and Mod Overview should be a component, not a PAGE.
• Mod Submission and Mod Overview should be a exitable dialog, and should not override the home screen with its own page, ie /submit-mod and /mod should be reserved for a full page version of the mod overview.

Currently profile in Frontend does not reflect user info in backend, we need to set this properly.

TODO

• Profile bio, username, and badges should reflect their respective user data.
• Allow people to set their profile picture via Settings
• Allow people to also change their username if need be

Since this is not customer-facing and intended for people with privileges and roles, the content and structure of the components should be unique when entering this views.

Publisher

ModCard State

• on Pending, Favorite button along with the stats counter is disabled since its not yet seen by the general crowd.
• Add a Hamburger that would bring a context to allow the publisher of the mod to delete the mod, this will only be available to the Author, and not to the collaborators.

Sidenav State

• Hidden in view.

Admin

ModCard State

• on Pending, Favorite button along with the stats counter is disabled since its not yet seen by the general crowd.
• Replace Download and Favorite Button with Accept and Reject button, use the same style if necessary.

Sidenav State

• Remove the Home's Sidenav content.
• Add entries for:
  • Pending Mods
  • User Reports

Even if we have CloudFlare firewall rules, there is a marginal chance we can get baad traffic through, that's why we have ReCaptcha v3 on login as discussion with @Ovyerus.

According to @Ovyerus, it should be easier to use Vue since it's a more established platform, plus it's easy to use Vue for our use case since we came from a pure HTML background (and Angular/React sucks).

Todo

• Nuxt rewrite - Client
• handle foreachs for cards
• die inside I guess

Regardless of Title size, the Mod card should remain a fixed size, else it looks terrible.

I designed it to tile in a fixed constraint size, and we should not deviate from that.

Since after the new UI fixes I created, the login app didn't conform well with smaller screens - pretty bad for responsive design.

escalating this to high priority, urgently needing @Ovyerus to work on this

Currently our mod tiles are still placeholders, we still need to make them live data.

Cards has differed sizings based on titles, UI wise, it looks ugly.

Admin should remain hidden unless the requestee has a qualifying token with admin perms. Currently users can navigate to the admin-dashboard. We should try to redirect them back to home page or block them with 401.

Currently Admin dashboard is a big heckin chonk of a template. We need to finish it by next week so we can onboard everyone

TODO

• Live data on Home
• Report Queue (Mods and Users)
• Pending Mods
• User Access Control (Deleting and setting the properties of a user)

This will replace our current FAB implementation since it allows us to embed our server within the site. This will be done seperate of the master branch.

This may cause some elements to be completely hidden by the footer if you drag the browser's bottom window side up.

Basic Attention Token is a initiative by Brave to allow creators to monetize their content without resorting to ads. Allowing us to support this will allow us and future white-labeling users to support their website along with a donation page.

Due to the unreliability and increased diifculty to maintain a Vue-based frontend, we have a consensus to redo everything to React and Next.js. This is the Backlog to track issues in:

• Convert Nuxt-based frontend to Next.js
• Feature Parity
  • All of the implemented views and features
  • Twitter-style mod overview (clicking on a mod card will return a new route ala mod/:id).