Where do documents reside?
When you create a document from inside the UD app without specifying a path location, it is a native document. Native documents exist in the following local file system location:
This means that, if you upgrade to a different version of the app, you must be very careful not do delete the resources that live in that install directory. Instead, follow the migration steps given in this documentation.
Link to a local directory
This is an experimental feature at the moment. Testing of links to a target FS directory is next up on the to-do list but users should be able to get some value from this option.
Link to a local directory
To try this feature out, select a context node label, and click on the 'configure' menuitem from the main menu. In this dialog you can choose to the 'Redirect export to FS directory' option. You must provide a path on the local file system, a place where things will be redirected to when the export command is executed. When you export, you should see this part of the vault written to the file system as you specified. Exporting is talked about later in this section.
NOTE: PLEASE IGNORE ALL OF THE OPTIONS IN THE DROPDOWN EXCEPT THE 'Redirect export to FS directory target' OPTION, AS THEY DO NOT DO ANYTHING.
Limitations on linked nodes Motivations for FS links Exporting to the file system
This relates to branches of a vault that are linked to a file system location which currently has not been implemented yet.
This relates to something currently on the todo list but has not yet been implemented.
There is an export feature that writes the contents of the currently open vault to locations in the file system. To begin the process of exporting hit the 'x' key. There is not an export menuitem... we tried to streamline the main menu and 'export' didn't make the cut.
Limitations on linked nodes
Motivations for FS links
Exporting to the file system
Immediately you will see an export popup to allow you to specify a default directory that will be the target location for the export. It looks like this:
If you leave the target directory edit window blank, it is still possible to run the export routine. In this case, only items (resources and context nodes) that have been given targets using the 'configure' action, will be written to the file system.
By setting it up this way, links to urls and documents can be dumped to different locations in the file system for more permanent, conventional file system access.
Native text documents are copied to a new home inside a target location, and url links are placed inside a '.bat' file or '.sh' file (depending on your OS) so that they can be launched from the file system inside the current browser.
Other resources, the ones that are not native and are not url pointers, are exported by creating symbolic links. The sym links in the target directories will point back to the actual physical files that were specified when the resources were originally added to the vault.
Exporting to HTML
In order to share some or all of your vault with others who do not have the UD app, there is a convenient option to generate an HTML view of a single branch or of the entire tree of your vault.
Exporting to HTML
To export to HTML, first navigate to the branch you would like to include. If you want to include the entire vault, navigate to the top level node in the 'locator path'. The locator path alone determines what is exported, so it doesn't matter if items on the page are selected or not, when it comes to exporting.
Next, do an 'ALT+x'. So just hold down the 'ALT' key and then press 'x'.
Finally, when you see the HTML source being displayed in the popup window, select it and paste it into an empty .html document inside your favorite text editor. Save that and you are basically done.
Our company was founded in July 2017 by Bradley Pliam.
The headquarters is currently in Austin, Texas.
Ideas that have been in gestation since the early 2000s have now finally been given 'wings'.
The mission of the company is to deliver happiness in the form of value and great user experience via high quality software, being honest about what is being delivered, and up-front about any current limitations. The world of software has some great things, along with some insidiously bad aspects. We intend to be a positive influence.
Meet our current staff...