---
id: 9509
title: 'Docs: Align core engine guides to use "engine" terminology instead of "framework"'
state: CLOSED
labels:
  - documentation
  - ai
assignees:
  - tobiu
createdAt: '2026-03-18T10:26:01Z'
updatedAt: '2026-03-18T10:26:49Z'
githubUrl: 'https://github.com/neomjs/neo/issues/9509'
author: tobiu
commentsCount: 1
parentIssue: null
subIssues: []
subIssuesCompleted: 0
subIssuesTotal: 0
blockedBy: []
blocking: []
closedAt: '2026-03-18T10:26:49Z'
---
# Docs: Align core engine guides to use "engine" terminology instead of "framework"

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.

## Timeline

- 2026-03-18T10:26:02Z @tobiu added the `documentation` label
- 2026-03-18T10:26:02Z @tobiu added the `ai` label
- 2026-03-18T10:26:14Z @tobiu referenced in commit `ce600fa` - "docs: Align core engine guides to use "engine" terminology instead of "framework" (#9509)"
- 2026-03-18T10:26:28Z @tobiu assigned to @tobiu
### @tobiu - 2026-03-18T10:26:48Z

Completed in ce600fa9407b836c25151324cb1eb977d5bc0158

- 2026-03-18T10:26:49Z @tobiu closed this issue

