Documentation improvements discussion
See original GitHub issueIssue type:
[ ] bug report [ ] feature request [x] documentation issue
TypeORM version:
[x] latest
[ ] @next
[ ] 0.x.x
(or put your version here)
I am opening this issue to start a discussion about improving TypeORM documentation. I have created a repo using VuePress to make TypeORM documentation better and to demonstrate the benefits of this approach. I picked VuePress because it looks the most similar to the current design and is well supported.
Current problems:
- Docs are not SEO-friendly, for example when you Google search for TypeORM docs you only get typeorm.io landing page (no other pages are indexed) and docs on github that are hard to search. In VuePress each Markdown file is compiled into HTML that can be easily crawled and indexed by search engines.
- Docs are not searchable. Currently in VuePress example repo I am using vuepress-plugin-fulltext-search package that provides fulltext search using flexsearch library. Even though I have come across some problems using this approach, it is a lot better than no search. Recently I have found that Algolia provides free search for documentation and powers a lot of popular open source projects. For search, I think Algolia would be the best approach.
I would like to ask @pleerock and @imnotjames is such a change desirable and what everyone else thinks about this?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Discussion about the documentation improvements #contributeit
Hello everyone . We want to improve the documentation of aiohttp. To do this, we need to know what, in your opinion, is...
Read more >How do I document a performance improvement discussion?
The best way to document a performance discussion is to send the employee a memo summarizing your conversation and the employee's agreement to...
Read more >3 Tips to Improve Documentation Productivity - Nuance Blog
1. Make accuracy the cornerstone of documentation process improvement · 2. Factor mobility into your documentation workflow · 3. Acknowledge ...
Read more >How do I Document a Performance Improvement Discussion?
The best way to document a performance discussion is to send the employee a memo summarizing your conversation and the employee's agreement ...
Read more >Process Documentation: Definition & Best Practices - Helpjuice
In this post, we'll discuss: What process documentation is; The goal of business process documentation; Who should be involved when creating ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Setting up a separate repo for documentation would be much better and easier to maintain and track issues.
I created the documentation of nature-ui using Nextjs, Markdown, and Algolia, and we can easily customise the codebase for this use case, so we have fewer things to worry about since the documentation is written in Markdown.
It’s accessible, SEO friendly and follows best practices.
@merfire @imnotjames @pleerock
I think Docsaurus 2 would be a great solution, it covers all the points I mentioned and also has built-in support for Algolia search, I think typeorm can easily apply and get free for open source projects Algolia package.