9 ms·
A browser interface for reading can easily be done by exporting to html. There is an option to output in a texinfo-like interface,with prev next and up navigat
by deerpig 12y ago
A browser interface for reading can easily be done by exporting to html. There is an option to output in a texinfo-like interface,with prev next and up navigation. Latex equations, charts, images and graphs (if you want to learn a little R) can all be integrated easily. Bibliographies can be handled using BibTex.
There is a learning curve to be sure, but the payoff is incredible since you can then directly build research papers and books that output to LaTex/PDF....
- hsitz 12y agoAnd a browser interface for recording and linking web pages in your Org files can be found here (although there are other ways to do it): http://orgmode.org/worg/org-contrib/org-annotation-helper.html http://orgmode.org/worg/org-contrib/org-annotation-helper.ht... Also, because Org files are at heart just some pretty simply formatted plain text, it would be easy enough to write Org entries in any simple text editor and add the file to your main Org repository of Org files at a later time, possibly by using the 'refile' functionality to have each entry in the "scratch" file routed to correct spot in permanent files. I think Org-mode is probably one of the best knowledgebase solutions, but only for a limited range of users, who must be pretty savvy power users and also willing to devote a bit of time to get setup to their liking so they can then leverage it to their benefit. It's pretty hard to wrap your head around all the different things that Org-mode can do, and then a bit harder to create a workflow that's easy and fast to use. But many have done it, some for the knowledgebase scenario and some for the wide variety of things the very flexible Org-mode app can do.