Recent versions of Firefox, Chrome, or Opera.The search algorithm is kept simple because it needs to be fast even searching through 100,000 strings.ĭevDocs being a developer tool, the browser requirements are high: A service worker (which comes with its own set of constraints) and localStorage are used to speed up the boot time, while memory consumption is kept in check by allowing the user to pick his/her own set of documentations. scripts and stylesheets) to avoid polluting the main frame, and prefixing all CSS class names with an underscore to prevent conflicts.Īnother driving factor is performance and the fact that everything happens in the browser. This includes stripping the original documents of most of their HTML markup (e.g. Many of the code's design decisions were driven by the fact that the app uses XHR to load content directly into the main frame. It relies on files generated by the scraper. The web app is all client-side JavaScript, written in CoffeeScript, and powered by a small Sinatra/ Sprockets application. Tutorials, guides and other content that don't meet this requirement are outside the scope of the project. Its backbone is metadata each piece of content is identified by a unique, "obvious" and short string. All our content is pulled from third-party sources and the project doesn't intend to compete with full-text search engines. Note: DevDocs is neither a programming guide nor a search engine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |