AtAGlance routing

[Brian Lewis]

// WARNING!!! The way the routes are defined below need to urgently be re-thought // One particular issue is that the selectedEdLevel, selectedSchoolType and selectedSector // are hard coded but they could and likely are different across country deployments // Furthermore, some routes below are specific to Kiribati and SI, some for RMI and some common // to all. A big mess!

[Brian Lewis]

Each AtAGlance display will combine the selected EdLevel, SchoolType, and Sector with a template page; and these will be quite particular for each country and education level. Currently, the navigation menu is based on each navigation item being linked to a specific route, so either: 1) we change the navigation system to pass parameters to a route; or 2) we need a single, specific route for each possible ataglance combination.

1) is a far-reaching change, and probably does not accomplishmuch - we lose a multiplicity of routes by adding a layer of complexity to the menu setup.

So I propose we stick with 2) and can name the routes specific to their particular uses.

[Ghislain Hachey]

I agree with 2)