search

bushwallyta271828 / logic_graph_scalable

This repository should support the logicgraph.dev website, taking over from logic_graph.
MIT License
0 stars 0 forks source link

Frontend organization #111

Closed bushwallyta271828 closed 6 months ago

bushwallyta271828 commented 7 months ago

Current thoughts:

It would be reasonable to organize the website as follows:

(/) (Sign-in) (/claims) (where you enter the claims) (/analysis) (where you see analysis of your claims) (/documentation) (the documentation page)

However, from a user experience perspective, I don't love this setup. I dislike how ChatGPT's chat interface isn't the first thing you get when you google ChatGPT: you have to click a further link from that website.

Instead, I'm thinking of:

(/) (where you enter the claims, can't save unless you're signed in) (/analysis) (where you see analysis of your claims) (/documentation) (the documentation page) (/sign-in) (the sign-in page, you get directed here if you try to save while signed out)

Along the navbar, this would be displayed as:

Claims Analysis Documentation Account

bushwallyta271828 commented 7 months ago

Maybe I should use Context to share state data? https://medium.com/inato/how-to-develop-a-navigation-menu-with-react-context-9f4d14db3d55

bushwallyta271828 commented 7 months ago

This tutorial on state management looks excellent: https://www.youtube.com/watch?v=I7dwJxGuGYQ

bushwallyta271828 commented 7 months ago

For context, I'm thinking (1) a dictionary claimID --> claim and (2) an array of claimID's.