7 ms·
How will it cope when content starts to grow? It will require a massive single request to fetch the content and then JS will have to build the interface. Like
by kostarelo 6y ago
How will it cope when content starts to grow? It will require a massive single request to fetch the content and then JS will have to build the interface.
Like other commented, better split pages and prefer pre-rendering. Documentation is something I usually need immediately and I really don't care how pretty it looks.
- NickBusey 6y agoYea this is my thought. Any sizable project will have enough documentation to make this one page approach unwieldy IMO. MkDocs Material is all I'll ever need for documentation. https://squidfunk.github.io/mkdocs-material/getting-started/ https://squidfunk.github.io/mkdocs-material/getting-started/
- deleted 6y ago[deleted]
- 0x142857 6y agoworks pretty well for lodash. https://lodash.com/docs/4.17.15 https://lodash.com/docs/4.17.15
- 0x142857 6y agoit's indeed a problem for large-scale docs, that's why I have another solution here https://docute.org/ https://docute.org/