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.
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/learnneoto a top-level folder likelearnorguideswould help LLMs better access it for training data, here's my analysis:Yes, it would likely help for several reasons:
1. Discoverability & Crawling
/guidesis more easily discovered by web crawlers and automated systems that index repositories/learndocs/,guides/,tutorials/, or for documentation, making it a recognizable pattern for LLMslearn/2. Path Semantics
resources/data/deck/learnneo/pages/is deeply nested and less semantically clear/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)examples/Adding would follow this established pattern and create better organization.
/learn/4. Web Accessibility
Since the content is accessible via
#/learnon your website, having the source files in a directory would create better alignment between the URL structure and the repository structure./learnRecommendation:
Move to
/learn/rather than/guides/because:#/learn)The structure could become:
This would make your learning content much more discoverable for LLM training while maintaining the same organizational structure within the moved directory.