folio.PUT IT TO WORK
Step by step
- Create or upload a private directory and organize its notes into useful subfolders. Name the files and folders so their paths explain the structure.
- Select the directory in your workspace, then choose Share selected directory.
- Review the proposed public title, paths and exact file contents in the sharing interface. Confirm only the material you are authorized to publish.
- Publish the reviewed directory snapshot. Readers can find it through shared search or its public directory link.
- Ask readers to choose Preview directory first. They can inspect excerpts and read individual files before installing the shared structure.
Use paths as a table of contents
For a study collection, paths such as 'Foundations/Definitions.md' and 'Exercises/Practice.md' are easier to navigate than a flat set of numbered notes. For a project, separate reference material, procedures and examples so readers can quickly choose the file they need.
The shared preview displays nested relative paths, titles and short plain-text excerpts. These are previews, not executable scripts. File links open the shared document's text rather than running uploaded code.
Search a directory and search the collection
The directory preview has a local filter for its loaded file titles, paths and excerpts. This is useful for navigating a visible chapter list without requesting the server after every keystroke. It does not search the undisplayed remainder of every file body.
For a word somewhere deep inside a chapter, use the homepage's full-text shared search. It searches public note text and can return a contained file or its directory. Combining both views gives you broad discovery and focused navigation.
Publishing does not grant access to private drafts
The public directory contains an explicitly confirmed snapshot, not a live window into your private workspace. Later private edits require another publication review before they become part of the shared edition. Installed shared originals resolve the confirmed public source; readers' private user versions do not automatically synchronize back.
Review every proposed file before confirming. A directory can contain an old chapter, a draft or a private aside that you forgot about. Do not assume that a harmless directory name makes all its contents appropriate to publish.
Keep in mindA directory publication can expose several documents at once. Review the full selected content and respect each source's reuse rights.
Common questions
Does previewing a directory copy every chapter?
No. Previewing reads metadata and excerpts. Installing keeps untouched files shared; a private version is created only when a file is actually modified and saved.
Can a reader search the complete chapter text?
Yes, through the full-text shared collection search. The directory's local preview filter searches the loaded title/path/excerpt fields.
Find a useful starting point.
Search the shared notes and directory collection, then open your own workspace when you are ready to work. Reading a shared document does not create a private file.