-
Notifications
You must be signed in to change notification settings - Fork 4
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
Ambokar - ForestGEO Application Rework w/ NextJS App Router #138
Conversation
…ogout. added loading spinner
* endpoints have been added and routed to require a plot key/number combination for access ** initial state has been converted to new Plot {key: 'none', num: 0} instead of '' * MUI JoyUI has been partially implemented as a replacement for MaterialUI. However, due to time limitations, MaterialUI has still been incorporated into converted sections from ForestGeoHack ** The current plan is to solely implement either NextUI or ChakraUI instead of either of these options, and future updates will include this information. * SelectPlotProps has been removed and replaced with NextJS dynamic routing (each endpoint will dynamically retrieve plot information). Endpoints have been updated to reflect dynamic param-based retrieval ** The navigation bar has been updated to use useEffect to push live endpoint updates when the plot is changed (if you are at an endpoint and the plot is changed, the page will be reloaded to reflect that) * New components/moved-over information: ** Dropzone --> css code has been udpated to be dark theme-friendly ** FileList --> moved over ** Loginlogout --> created component, login/logout process has been relegated to avatar icon dropdown menu ** Plotselection --> partially created from SelectPlot, changed to utilize dynamic routing/selection instead of requiring a new dropdown in each page
…l for exactly what it's doing
…to work with app router. need to re-implement and test
…ver confirmed. saving changes in order to confirm data upload functionality
…om directory structure and simplified remaining code
… to 13.5.1-canary.1 because that actually installs instead
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
2 similar comments
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://agreeable-wave-08a957210-138.centralus.1.azurestaticapps.net |
Introducing NextJS v14 into ForestGEO application:
ForestGEO application is moving to NextJS in order to ensure long-term application stability and support and improved baseline application design and mechanics.
Changelog:
NextJS ForestGEO Application Changes: