In learn/benefits/Introduction.md, Neo.mjs is explicitly positioned as a multi-threaded Application Engine, not just a traditional UI framework.
However, across the 6 new coreengine guides, we slipped back into using the term "framework" 17 times to describe core capabilities. This dilutes the primary messaging.
This issue corrects this by replacing instances of "framework" with "engine" across the learn/guides/coreengine/ directory to ensure consistent terminology and reinforce the platform's architectural identity.
In
learn/benefits/Introduction.md, Neo.mjs is explicitly positioned as a multi-threaded Application Engine, not just a traditional UI framework.However, across the 6 new
coreengineguides, we slipped back into using the term "framework" 17 times to describe core capabilities. This dilutes the primary messaging.This issue corrects this by replacing instances of "framework" with "engine" across the
learn/guides/coreengine/directory to ensure consistent terminology and reinforce the platform's architectural identity.