LearnNewsExamplesServices
Frontmatter
id6854
titleresources/data/deck/learnneo => learn/
stateClosed
labels
enhancement
assigneestobiu
createdAtJun 22, 2025, 10:43 PM
updatedAtOct 23, 2025, 12:55 AM
githubUrlhttps://github.com/neomjs/neo/issues/6854
authortobiu
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtJun 22, 2025, 10:46 PM

resources/data/deck/learnneo => learn/

Closed v10.0.0-alpha.4 enhancement
tobiu
tobiu commented on Jun 22, 2025, 10:43 PM

Let me first explore the current structure of the learning content to understand how it's organized and accessed. Based on your question about whether moving the learning content from resources/data/deck/learnneo to a top-level folder like learn or guides would help LLMs better access it for training data, here's my analysis:

Yes, it would likely help for several reasons:

1. Discoverability & Crawling

  • Top-level visibility: Content in root-level directories like or /guides is more easily discovered by web crawlers and automated systems that index repositories /learn
  • Standard conventions: Many projects use top-level directories like docs/, guides/, tutorials/, or for documentation, making it a recognizable pattern for LLMs learn/

2. Path Semantics

  • The current path resources/data/deck/learnneo/pages/ is deeply nested and less semantically clear
  • A path like or /guides/ immediately signals educational content to both humans and automated systems /learn/

3. Repository Structure Best Practices

Looking at your current structure, you already have top-level directories like:

  • docs/ (likely for API documentation)
  • (for code examples) examples/

Adding would follow this established pattern and create better organization. /learn/

4. Web Accessibility

Since the content is accessible via #/learn on your website, having the source files in a directory would create better alignment between the URL structure and the repository structure. /learn

Recommendation:

Move to /learn/ rather than /guides/ because:

  • It matches your existing URL structure (#/learn)
  • It's more inclusive (covers tutorials, guides, getting started, etc.)
  • It's shorter and more memorable

The structure could become:

/learn/
  ├── benefits/
  ├── getting-started/
  ├── tutorials/
  ├── guides/
  ├── javascript/
  ├── Glossary.md
  └── UsingTheseTopics.md

This would make your learning content much more discoverable for LLM training while maintaining the same organizational structure within the moved directory.

tobiu assigned to @tobiu on Jun 22, 2025, 10:43 PM
tobiu added the enhancement label on Jun 22, 2025, 10:43 PM
tobiu referenced in commit 52db3f7 - "resources/data/deck/learnneo => learn/ #6854" on Jun 22, 2025, 10:45 PM
tobiu
tobiu Jun 22, 2025, 10:46 PM

FYI: the portal app has legacy support. it can still pull in the trainings deck from its old location if needed.

tobiu closed this issue on Jun 22, 2025, 10:46 PM