Project Tab
The Project tab is where you manage metadata about your map project. None of the fields here change how the map looks or what gets exported visually. Instead, they help you organize, identify, and track your work, especially when managing multiple projects or collaborating with others.
The tab is divided into three areas: a read-only File Info section showing automatically tracked statistics, editable Project Fields for naming and describing your project, and a History section (coming in a future release).
File Info
Display-only metadata — no user-editable controls. These values are calculated and tracked automatically by the application. They give you a quick snapshot of your project's current state without needing to count anything manually.
| Feature | Control | Property | Description |
|---|---|---|---|
| Created date | Display | settings.projectCreated | Shows when the project was first created. This timestamp is set automatically the moment you start a new project and never changes afterward, even if you re-import the JSON file later. Displayed in MM/dd/yyyy format in the project info grid. Useful for tracking when a project originated, especially if you're managing multiple map files for different deals or presentations. |
| Last saved | Display | _lastSaved | Shows the date and time the project was last exported as a JSON file. Updates each time you click Export JSON (or click the Unsaved badge in the header). This does not track PNG or SVG exports, only JSON saves. Helps you confirm when the project file was last backed up, so you know whether recent changes have been persisted. |
| Last edited by | Display | settings.lastEditedBy | Shows the name of the person who last saved the project. This value is pulled from the Owner field (see Section 1.2) at the time of each JSON export. In multi-person workflows where a project file gets passed between team members, this field tells you who made the most recent changes. |
| Schema version | Display | CFG.projectSchema (v4) | Shows the internal data format version used by this project file (currently v4). You generally don't need to worry about this value. It exists for backward compatibility: when you load an older project file saved in v3 or earlier format, pitchmappr automatically migrates the data to the current schema. If migration happens, it's seamless and invisible. |
| Location count | Display | locations.length | Auto-counted total of all location markers across all datasets in the project. Updates in real-time as locations are added, imported, or removed. Matches the "Loc" counter in the header bar. Gives you a quick overview of project size without needing to scroll through the location list. |
| Dataset count | Display | datasets.length | Auto-counted total of all datasets in the project. Each dataset is an independent group of locations that share the same marker color, shape, and visibility settings. Every project has at least one dataset, so the minimum value is always 1. |
| View count | Display | savedViews.length | Auto-counted total of saved map views. Each view captures a specific zoom level, center position, and crop ratio so you can consistently reproduce the same export framing. Matches the "Views" counter in the header bar. |
Project Fields (rendered outside sections)
These fields let you attach identifying information to your project. All values are saved in the JSON export file. They're entirely optional, but filling them in makes it much easier to manage projects over time, especially when you have dozens of map files for different clients or deals.
| Feature | Control | Property | Description |
|---|---|---|---|
| Project Name | Text input | settings.projectName | The display name for the project, shown in the app header bar as the primary project identifier. This is the first thing you (or a colleague) will see when working on the file. It's also used as the fallback filename when exporting: if no Job Number is set, exported PNGs, SVGs, and JSON files use the Project Name as their filename prefix. Pick something descriptive enough to identify the project at a glance (e.g. "Acme Corp — US Office Locations"). |
| Job / Ref Number | Text input | settings.projectJobNumber | An optional reference number shown in the header subtitle area, below the Project Name. This is designed for deal IDs, project codes, matter numbers, or any internal tracking identifier your team uses. When set, it takes priority over Project Name for export filenames, so your exported files automatically carry the reference number (e.g. "PRJ-2026-0142_16x9.png"). This keeps exports organized and easy to file. |
| Owner | Text input | settings.projectOwner | The person currently responsible for the project. Stored as metadata in the JSON file and used to populate the "Last edited by" field each time you save. Does not appear on the map or in any visual exports. In team workflows, this helps track who "owns" the file and should be contacted about changes. |
| Creator | Text input | settings.projectCreator | The person who originally created the project. Metadata only — stored in JSON for reference but not displayed on the map. Defaults to the first person to save the file. Unlike Owner, this field is intended to stay fixed even if the project changes hands, so you always know who initiated it. |
| Client | Text input | settings.projectClient | Optional client or company name associated with the project. Metadata only — stored in JSON for reference but has no effect on map rendering or exports. Helpful for organizing projects by client, especially in environments where multiple team members create maps for different clients. |
| Description | Textarea | settings.projectDescription | Free-text project description or notes. Metadata only — stored in JSON for documentation purposes. Supports multiple lines, so you can include context like "Map showing all target portfolio companies for the 2026 Q2 review" or any internal notes about scope, status, or special instructions. Does not appear on the map or in exports. |
History
Placeholder section — currently displays "Change history will appear here in a future update." This will eventually provide a timeline of project changes, making it easier to track what was modified and when. For now, use the "Last saved" timestamp and "Last edited by" fields to track recent activity.