Perhaps a use case or two might be useful

yeah, thats probably a good idea for sure

I mean take a task that someone might need and use it to explain how the modular system works and how to achive something.

yeah, agreed... that does make alot of sense

For instance apple seem to have this notepad thing where you can add simple sketch with calendar and make notes, in your case you could simplify that to journal where you can add images or text and nav via date.... it that feasible?

Perhaps something much simpler.

you mean an example application?

Well yes but using maybe 2 or 3 examples to take users through different aspects of what HaxeUI does really well so it's an excuse to expose a few smart parts while still give an overview of something users can directly relate to.

yeah, totally going to do that also, for sure

animations, binding, responsive, etc, etc

for me, personally, i would prefer the example app above the docs, but i think im in the minority there

My concept is think of it as little stories, you add a story that explains an area of functionality

Well breaking down an app and joining it to small md pages.

yeah, i was thinking about adding another set of guides that specifically reference parts of an example application

can work

where as these guides above serve as a more "complete" explanation of the API (separated by specific areas)

These are all successful popular projects with complex code bases: http://away3d.com/tutorials/ https://phaser.io/learn https://threejs.org/docs/index.html#manual/en/introduction/Creating-a-scene I would suggest you consider what you can provide as a minimum to boost users to the point where they would help fill in this level of detail, but notice the high use of images to provide context. People want to scan a doc to get a feel if it provides what they need then they read the text. I don't know if I am being helpful I am just giving my view point, I just know that some aspects of the Haxe manual seemed to have missed the general user, so professional has won over popularist.

I am sure module.md provides technical aspects explained well but it lacks the context and specifics to really start digging in and you can't scan over it to see where it's going and which bits you need to focus on for your need.

So I would keep it but definitely think how did away3d when it as3 was popular lower the entry bar enough for users to get started. Remember these popular projects have thousands of users slowly shaping the document approach, so likely they contain some good approaches.

phasorjs perhaps even more so?

Anyway if you don't find my thoughts useful feel free to ignore sometimes I can really annoy people with my analysis, think your project has huge potential so look forward to more stuff.

Yeah, i defo agree - a very basic "start here" is certainly something i want to (will) create (with an accompanying) That said, i also think guides that have a "this is all the stuff you can do, work it out" is also useful - they arent both mutally exclusive either i suppose

i want to create something more like this as an entry level (but more fleshed out, and with better examples):

(note that is VERRRRY unfinished)

Is the html5 canvas based or dom?

well, haxeui-html5 is dom

haxeui-openfl is "dom" / canvas /webgl depending on options you choose in openfl

same goes for kha, etc

Again first page I really want something visual to tell me something about haxeui