Skip to main content

​
Packages

A Package is a folder for Panes. It groups the Panes that together make one capability a person can name, such as scenario planning, categorization, or reporting settings, so collaborators can find them, review them together, and move them as one module. A Package holds Panes and other Packages and nothing else. It is not a route, it has no value of its own, and it grants no access. Packages appear with Pages in the Pieces view. Root Packages sit beside Pages, and a Package can contain nested Packages. Each Pane keeps its own Perception, Plots, Palette, and Policies, and they travel with it wherever it moves. Pages stay in the Page hierarchy: a Package never contains a Page, and a Page uses a Pane by declaring it in its Perception, not by copying a Package. A new Package needs a name, an icon and a one-sentence description of the capability it groups, saved together. Every Package, like every Piece, has a handle, a camelCase name unique within the Parable, and a permanent identifier underneath it, so a rename or a move keeps references intact. A Package’s icon is a box, a folder or a piece: the things a Package is and holds. Give a Package one of these Font Awesome glyphs and no other, stored as fa:sharp:solid-duotone:<glyph>, for example fa:sharp:solid-duotone:box-open. The icon picker offers people the same list.
  • Boxes: box, box-open, box-open-full, box-archive, box-taped, box-check, box-circle-check, box-heart, box-dollar, box-isometric, box-isometric-tape, box-magnifying-glass, box-arrow-down, box-arrow-up, box-arrow-down-arrow-up, box-arrow-down-magnifying-glass, boxes-stacked, boxes-packing, square-fragile, square-this-way-up, toolbox, treasure-chest, gift, gifts, crate-empty, crate-apple, container-storage, pallet-box, pallet-boxes, cart-flatbed-boxes, dolly, hand-holding-box, people-carry-box, person-carry-box, truck-ramp-box, parachute-box, conveyor-belt-boxes.
  • Folders: folder, folder-open, folder-closed, folders, folder-tree, folder-grid, folder-gear, folder-bookmark, folder-heart, folder-image, folder-user, folder-music, folder-medical, folder-check, folder-plus, folder-minus, folder-xmark, folder-magnifying-glass, folder-arrow-down, folder-arrow-up, folder-arrow-left, folder-arrow-right, cabinet-filing.
  • Pieces: puzzle, puzzle-piece, puzzle-piece-simple, shapes, cube, cubes, cubes-stacked, block, chess-pawn-piece, chess-knight-piece, chess-bishop-piece, chess-rook-piece, chess-queen-piece, chess-king-piece.
Creating, renaming, moving, and deleting a Package is an edit to the Parable. It follows the Parable’s Collaboration Mode and the editor’s permissions; people who can only read can browse the same tree without the edit actions. Removing a Package from Changes leaves any Page that still declares one of its Panes with a missing reference, which publishing reports as a finding. Repair those Pages before proposing the change.
  1. Name the capability. Ask Ponder to group by what a person would call the capability, not by team, file, or storage location. Ponder chooses a clear name, an icon from that list and a one-sentence description.
  2. Keep the tree shallow. A Package earns its place when it makes discovery, reuse, review, or maintenance easier. Avoid a Package for a single Pane unless that grouping has a stable meaning for customers.
  3. Place the Panes. Ponder puts each Pane that belongs to the capability inside the Package, including the Panes that configure it, so maintainers find configuration next to what it configures.
  4. Before a move or removal, ask Ponder to list every Pane in the Package and every Page or Pane whose Perception declares one of them. Move with the same identities, and repair references before removing anything.
  5. Review the Changes, and publish them when the Parable uses Publishing mode.
A good Package lets a new collaborator find a capability and its configuration in one place, lets permitted readers navigate it, and leaves every existing Page and Pane reference working after a change. Check the result by opening the Pages that use the affected Panes and confirming they still render, and by confirming the Changes report no missing reference. A tidier tree alone does not prove that behavior was preserved. Related Powers: Panes, Pages, Perceptions, Publishing. Find each by its title; do not guess stored names.