You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to have a separated Elm page that is specialized only on generating Conference pages. These pages contain essentially the same information as the unit's information page, meaning that we can re-use API routes, but the page will have a different layout.
The page will be identified by a Id Unit, which will be the root of the tree.
The main page should contain descriptions, the chair and members.
There should be a menu giving access to subparts, which will have similar pages. This menu should work like a tree, corresponding to the tree in the graph.
Elements in the menu should load lazily, to avoid problems with eventual cycles one created by accident.
Make sure that descriptions are rendered as markdown so that we have correct (and configurable) formatting, and all necessary external links work.
Steps:
Create a second main in Elm, which just displays a unit's information.
Make sure it is exposed by the API.
Add it to the deployment.
Proceed with the other features necessary in the page.
The text was updated successfully, but these errors were encountered:
The idea is to have a separated Elm page that is specialized only on generating Conference pages. These pages contain essentially the same information as the unit's information page, meaning that we can re-use API routes, but the page will have a different layout.
Id Unit
, which will be the root of the tree.Steps:
The text was updated successfully, but these errors were encountered: