codingthat / dakt Goto Github PK

I.e. in the menu data format.

As mentioned in the readme, it would be good to have the option of making sure you aren't sending users in circles.

Ironically our current test data, which was good for quick manual testing during prototype development, would fail this. So I guess this is tied to #10 as well.

This would still have to read the stored JS file, but the idea would be that the generated HTML itself wouldn't have any need for JS. Every page would redirect if JS was enabled to the SPA URL, but if not, would display via pure HTML+CSS.

Could use Node for this...

This is because 'dakt.html' is hardcoded into DaKT's pushState URL formatter...

As a simpler alternative to the full tree editor.

For an intranet site, allowing users to add internal URLs from a set list would be helpful.

Like a traditional navigation system, showing the path you've taken would be helpful to see (also for jumping back quickly, but it should be done with pushState integration if possible, I think.)

With drag-n-drop, colour picker, and image uploader.

Undecided on neatest/simplest/most user-friendly solution to this.

We'll also need to add a config file sample for paths and optional features, I think.