diff --git a/change/@ni-nimble-components-e7154892-b084-429e-8d98-417c2721f61b.json b/change/@ni-nimble-components-e7154892-b084-429e-8d98-417c2721f61b.json
new file mode 100644
index 0000000000..4f4ac28d3a
--- /dev/null
+++ b/change/@ni-nimble-components-e7154892-b084-429e-8d98-417c2721f61b.json
@@ -0,0 +1,7 @@
+{
+ "type": "none",
+ "comment": "Add design document for table columns containing formatted text",
+ "packageName": "@ni/nimble-components",
+ "email": "jattasNI@users.noreply.github.com",
+ "dependentChangeType": "none"
+}
diff --git a/packages/nimble-components/src/table/specs/README.md b/packages/nimble-components/src/table/specs/README.md
index 15555d933e..ec7c1c92a4 100644
--- a/packages/nimble-components/src/table/specs/README.md
+++ b/packages/nimble-components/src/table/specs/README.md
@@ -105,6 +105,7 @@ The various APIs/features of the `nimble-table` will be split up amongst several
- What column gets used for sorting?
- List the set of column providers that Nimble will provide and provide their respective APIs where unique (e.g., formatter for DateTime column)
- [TableColumnText](table-column-specs/table-column-text-field.md)
+ - [Formatted Text Columns](table-column-specs/table-column-formatted-text.md)
- [TableColumnAnchor](table-column-specs/table-column-anchor-hld.md)
- Headers
- Define the anatomy of headers in the table DOM
diff --git a/packages/nimble-components/src/table/specs/table-column-specs/table-column-formatted-text.md b/packages/nimble-components/src/table/specs/table-column-specs/table-column-formatted-text.md
new file mode 100644
index 0000000000..137b93e3c5
--- /dev/null
+++ b/packages/nimble-components/src/table/specs/table-column-specs/table-column-formatted-text.md
@@ -0,0 +1,382 @@
+# Formatted Text Columns
+
+## Overview
+
+Clients will wish to display non-string text data in table columns for use cases like the following:
+
+1. integer data like counts, formatted to be displayed with no trailing decimals ("4", "100")
+2. floating point data formatted to display values in standard ways ("3.1415", "1.04E47", "Infinity", "-0.03")
+3. a mix of the above with formatting determined by the application ("1.000", "-0.030", "1024.000")
+4. numeric values with a static unit string appended before or after (e.g. "$4.23" or "15%")
+5. numeric values with custom unit logic. Examples:
+ - a file size column that could show the value 1000 as "1000 bytes" but the value 1024 as "1KB"
+ - an elapsed time column that could show 63 seconds as "00:01:03" or "1 minute, 3 seconds"
+6. enum and boolean values formatted as localized strings (0 -> "Fail", 1 -> "Pass")
+7. date/time values formatted in various ways ("October 27", "yesterday", "2023-12-28 08:27")
+
+In all of the above cases:
+
+- data should be sortable and groupable by its actual numeric value, not the string representation
+- text styling like font and alignment should be provided by Nimble
+- columns should support i18n behaviors like decimal separators, date/time formats, and localized content
+- there should be an option to show "placeholder" text if no value is specified
+- there should be a way to show the full value of truncated text (likely via a title / tooltip on hover)
+
+We may not choose to support all of the above initially but we should design our solutions with these use cases in mind.
+
+### Background
+
+[Number column work item](https://github.com/ni/nimble/issues/1011)
+
+[Date/time column work item](https://github.com/ni/nimble/issues/1014)
+
+[Boolean text column work item](https://github.com/ni/nimble/issues/1103)
+
+[Table Column API](../table-columns-hld.md)
+
+[Table Spec](../README.md)
+
+[Table Column Text Spec](./table-column-text-field.md)
+
+[Visual Design Spec](https://xd.adobe.com/view/5b476816-dad1-4671-b20a-efe796631c72-0e14/specs/)
+
+### Non-goals
+
+- Combinations of the use cases listed above in a single column. This will be needed in cases where the source data isn't uniformly typed (e.g. SLE tag values or notebook outputs). This HLD focuses on uniform data types; future HLDs will discuss ways to configure multiple types of columns to be conditionally displayed together.
+- Editable numbers. This is not supported by the text column yet either.
+- Numeric formatting for `nimble-number-field`. While we may choose to expose similar APIs for its numeric formatting, the complexities of it being an editable input control make this out of scope for now.
+- Customizing the styling of the column content (other than possibly text alignment). This is not supported by the text column yet either.
+
+---
+
+## Design
+
+### Summary
+
+Nimble will provide base classes that can be derived from to define columns that call a formatting function to render their data as text. Clients which require app-specific formatting logic to support above use cases like 5 (custom unit logic) will define custom columns in their application that derive from these base classes.
+
+Nimble will also provide several columns that derive from these base classes and provide higher level formatting APIs for specific data types. We plan to provide column implementations that can handle the above use cases 1-4 (numeric formatting and static units) in a first pass with 6 and 7 (enum/boolean and date) coming later. These will be easier to use than the above custom column approach:
+ - the columns will be configurable via HTML attributes, saving clients from writing JS code (a particular challenge in Blazor)
+ - they provide strict type validation of the data field
+ - clients don't need to manage the lifecycle of registering a new column custom element in their application
+
+### Formatted text column base classes
+
+*Originally called "Alternative 2: Client specifies formatting function"*
+
+Nimble will provide abstract base classes, templates, and styles which handle rendering a string as text. Just like `nimble-table-column-text` today, these columns will:
+- offer attributes to control which field is displayed and placeholder text when that field isn't a number.
+- sort and group by the field value, not the display value.
+- allow sizing by fractional widths with a minimum pixel width.
+- truncate using an ellipsis and show a tooltip on hover when the value is truncated
+
+The base classes provided will be:
+- `TableColumnTextBase` - specifies the custom element logic to configure the column
+- `TableColumnTextCellViewBase` - derives from `TableCellView` to specify the custom element logic that renders a cell
+- `TableColumnTextGroupHeaderViewBase` - derives from `TableGroupHeaderView` to specify the custom element logic that renders a group row
+
+Both clients and Nimble itself will derive from these base classes to specify the type of data that the column supports and how to convert it to a string. They will register the derived classes as custom elements using the same FAST APIs that Nimble itself uses.
+
+*** Use column custom element in an application**
+
+```html
+
+
+ Progress
+ `
+
+```
+
+***Define and register column custom element**
+
+```ts
+export class MyAppProgressColumn extends TableColumnTextBase {
+ public constructor() {
+ super({
+ cellRecordFieldNames: ['value'],
+ cellViewTag: tableColumnNumericTextCellViewTag,
+ groupHeaderViewTag: tableColumnNumericTextGroupHeaderTag
+ });
+ this.columnInternals.sortOperation = TableColumnSortOperation.basic;
+ }
+}
+
+const myAppProgressColumn = MyAppProgressColumn.compose({
+ baseName: 'table-column-progress',
+ template,
+ styles
+});
+
+DesignSystem.getOrCreate()
+ .withPrefix('my-app')
+ .register(myAppProgressColumn());
+export const myAppProgressColumnTag = DesignSystem.tagFor(MyAppProgressColumn);
+```
+
+***Specify formatting of cells and group headers in their custom elements**
+
+```ts
+export class MyAppProgressColumnCellView extends TableColumnTextCellViewBase<
+TableColumnNumericTextCellRecord,
+TableColumnNumericTextColumnConfig
+> {
+ public override get text(): string {
+ return `${100 * this.cellRecord.value}%`;
+ }
+
+ public override get placeholder(): string {
+ return this.columnConfig.placeholder;
+ }
+
+ public override get shouldUsePlaceholder(): boolean {
+ return typeof this.cellRecord.value !== 'number';
+ }
+}
+
+export class MyAppProgressColumnGroupHeaderView extends TableColumnTextGroupHeaderViewBase<
+TableNumberFieldValue,
+TableColumnNumericTextColumnConfig
+> {
+ public override get text(): string {
+ return `${100 * this.groupHeaderValue}%`;
+ }
+
+ public override get placeholder(): string {
+ return this.columnConfig.placeholder;
+ }
+
+ public override get shouldUsePlaceholder(): boolean {
+ return typeof this.groupHeaderValue !== 'number';
+ }
+}
+
+// Not shown: registering the above two custom elements
+```
+
+This is prototyped in the [formatted-text-column branch](https://github.com/ni/nimble/compare/main...users/jattas/formatted-text-column?expand=1).
+
+
+### Nimble formatted text columns
+
+*Originally called "Alternative 3: Nimble provides column implementation for common use cases"*
+
+#### Text column
+
+`nimble-table-column-text` will continue to present the same API it does today, but will derive from the base classes described above.
+
+#### Number column
+
+
+Nimble could introduce `nimble-table-column-number` which formats a numeric field value and displays it as text. It will offer sufficient configuration to support use cases 1-4 above.
+
+The API will be specified in a future update to this HLD.
+
+The primary formatting API will leverage the native browser [`Intl.NumberFormat` API](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat) which gives highly configurable formatting with great documentation. It supports features like locale-specific formatting, decimal separators, thousands separators, digits of precision, and units. Since it doesn't support some unit strings required by clients, the column will also offer ways to set a fixed prefix or suffix on every number.
+
+##### ``nimble-table-column-number` API
+
+_*Props/Attrs*_
+- `field-name` -
+- `placeholder` - The string value to use if the value of the field is `undefined`, `null`, `NaN`, or isn't of type `number`. Note that other "special" values like `Infinity` will be formatted and displayed.
+- TODO: ALIGNMENT
+- `prefix` - A string to append before the formatted value of each cell. It will not include any spacing.
+- `suffix` - A string to append after the formatted value of each cell. It will not include any spacing.
+- `number-format-locales` - Corresponds to the [`locales` parameter of `NumberFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#parameters). Note that initially we will not support an array of locales; if this is necessary we could consider parsing this field as a comma-separated list.
+- `number-format-options-*` - attributes that correspond to the properties of the [`options` parameter of `NumberFormat`]. Each property name will be converted from `camelCase` to `dash-case`. For example, `number-format-options-compact-display="long"` or `number-format-options-currency-display="narrowSymbol"`.
+
+For values being passed through to the `NumberFormat` API we will provide types similar to [the TypeScript types from the browser API](https://github.com/microsoft/TypeScript/blob/0f724c04308e20d93d397e82b11f82ad6f810c44/src/lib/es2020.intl.d.ts#L232). Default values if the attribute is not provided will match the `NumberFormat` API.
+
+```html
+
+
+ Progress
+
+
+
+ Count
+
+
+
+ Voltage
+
+
+```
+
+
+
+#### Boolean Text Column
+
+We will eventually provide an column type that maps boolean values to localized strings. This is an example API but the details will be updated in this document before implementation.
+
+```html
+
+
+ Test Result
+
+
+```
+
+##### Example E: Enum Text Column
+
+We will eventually provide an column type that maps enum values to localized strings. This is an example API but the details will be updated in this document before implementation.
+
+```html
+
+
+ Status
+ Pass
+ Fail
+
+
+```
+
+### API
+
+_Component Name_
+
+_*Props/Attrs*_
+
+_Type Reference_
+
+### Anatomy
+
+### Angular integration
+
+### Blazor integration
+
+I propose we **would not** encourage Blazor clients to write formatting code in .NET due to performance concerns.
+
+### Visual Appearance
+
+###
+TODO Items I asked Mert to include on hyperlink spec
+
+---
+
+## Implementation
+
+### Alternatives considered
+
+#### Other ways to provide a formatting function
+
+1. setting the formatting function as a property on a column element.
+2. setting an [`Intl.NumberFormat`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat) object as a property on a column element.
+
+Both of these require JS code which finds a specific column element and configures it. This is difficult to achieve in Blazor.
+
+#### Use `table-column-text`
+
+*Originally called "Alternative 1"*
+
+With the changes proposed in [HLD for programmatically sorting columns](../table-column-sort-hld.md) to allow a column to be sorted by a different data field than the one being used for display, many of the above use cases could be met with minor changes to the existing text column. Clients would write custom logic to populate their data with a new string field that contains formatted values. Then they would configure the table to display that string field while sorting by the original numeric field.
+
+```html
+
+
+ Progress
+ `
+
+```
+
+```ts
+const originalData = [{ progress: 0.1 }, { progress: 0.2 }];
+const tableData = originalData.map(x => {
+ progress: x.progress;
+ formattedProgress: x ? `${100 * x.progress}%` : undefined;
+});
+table.setData(tableData);
+```
+
+**Pros:**
+
+- formatted data is specified up front, guaranteeing fast scroll performance
+- powerful; clients can format data however they want, including via browser APIs which are i18n-friendly or via server-side logic
+
+**Cons:**
+
+- Increased memory usage and data update time from clients pre-populating data with field for each formatted column
+- Added complexity of writing procedural code even for simple numeric formatting use cases
+- Potential cross-app inconsistency if numeric formatting code isn't shared (versus Alternative 3)
+- Difficult to enforce styling differences between string and numeric columns (e.g. right vs left text alignment)
+
+**Implementation Cost:**
+
+- Exposing `operand-data-record-name` to be set by client code rather than column definition
+- Exposing an API for clients to indicate their data should be styled as numeric data (right aligned)
+
+
+#### Client provides custom column implementation for each use case
+
+*Originally called "Alternative 4"*
+
+Nimble already has a mechanism for clients to provide custom columns by deriving from a base class, specifying the data fields / template / styling, and registering the column type with Nimble. We could ask clients to use this mechanism for text column types.
+
+**Pros:**
+
+- Zero implementation cost to Nimble team
+- Powerful; clients can format data however they want, including via browser APIs which are i18n-friendly
+
+**Cons:**
+
+- Higher burden on clients to specify template, styling, numeric formatting, etc in JS. This is especially burdensome in frameworks like Blazor.
+- Difficult to enforce styling differences between string and numeric columns (e.g. right vs left text alignment)
+- Potential cross-app inconsistency if formatting code isn't shared
+
+
+
+### States
+
+### Accessibility
+
+### Globalization
+
+### Security
+
+### Performance
+
+### Dependencies
+
+### Test Plan
+
+### Tooling
+
+### Documentation
+
+---
+
+## Open Issues
+
+1. API to configure text alignment of column content and column headers (e.g. right align numeric columns but left align string columns). We'll update the HLD with a recommendation once we reach consensus on which alternatives to pursue (you're welcome to comment with ideas now though).
+2. The APIs in this document are examples, not yet proposals. Once we agree on high-level direction I will do more prototyping to propose concrete APIs.