docs: naming consistency itk-wasm -> ITK-Wasm

The overall project is called ITK-Wasm. The npm package is still
itk-wasm. The Python package is itkwasm. Keep the idiomatic package
names.

Author: thewtex

CHANGELOG.md

@@ -29,7 +29,7 @@ keywords:
   - scientific-computing
   - visualization
 repository-code: >-
-  https://github.com/InsightSoftwareConsortium/itk-wasm
+  https://github.com/InsightSoftwareConsortium/ITK-Wasm
 url: 'https://wasm.itk.org'
 repository-artifact: 'https://www.npmjs.com/package/itk-wasm'
 license: Apache-2.0

CITATION.cff

@@ -59,7 +59,7 @@ if(NOT ITK_FORBID_DOWNLOADS)
     "https://cloudflare-ipfs.com/ipfs/%(hash)"
 
     # DataLad repository on gin.g-node.org
-    "https://gin.g-node.org/InsightSoftwareConsortium/itk-wasm-testing-data/raw/main/Objects/CID/%(hash)"
+    "https://gin.g-node.org/InsightSoftwareConsortium/ITK-Wasm-testing-data/raw/main/Objects/CID/%(hash)"
     )
 endif()
 

CMake/ITKExternalData.cmake

@@ -1,23 +1,23 @@
-itk-wasm
+ITK-Wasm
 ========
 
-[![Examples](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/examples.yml)
-[![Toolchains](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/toolchains.yml)
-[![JavaScript, TypeScript](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/javascript-typescript.yml)
-[![Python Wasm](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/python-wasm.yml)
-[![C++,Native Python](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/cxx-python.yml)
-[![WASI](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/wasi.yml)
-[![Documentation](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/documentation.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/itk-wasm/actions/workflows/documentation.yml)
+[![Examples](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/examples.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/examples.yml)
+[![Toolchains](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/toolchains.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/toolchains.yml)
+[![JavaScript, TypeScript](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/javascript-typescript.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/javascript-typescript.yml)
+[![Python Wasm](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/python-wasm.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/python-wasm.yml)
+[![C++,Native Python](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/cxx-python.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/cxx-python.yml)
+[![WASI](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/wasi.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/wasi.yml)
+[![Documentation](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/documentation.yml/badge.svg)](https://github.com/InsightSoftwareConsortium/ITK-Wasm/actions/workflows/documentation.yml)
 
 [![npm version](https://badge.fury.io/js/itk-wasm.svg)](https://www.npmjs.com/package/itk-wasm)
 [![npm version](https://badge.fury.io/py/itkwasm.svg)](https://pypi.org/project/itkwasm/)
 [![npm version](https://badge.fury.io/py/itk-webassemblyinterface.svg)](https://pypi.org/project/itk-webassemblyinterface/)
 
 [![DOI](https://zenodo.org/badge/45812381.svg)](https://zenodo.org/badge/latestdoi/45812381)
 
-![License](https://img.shields.io/github/license/InsightSoftwareConsortium/itk-wasm) ![GitHub commit activity](https://img.shields.io/github/commit-activity/y/InsightSoftwareConsortium/itk-wasm)
+![License](https://img.shields.io/github/license/InsightSoftwareConsortium/ITK-Wasm) ![GitHub commit activity](https://img.shields.io/github/commit-activity/y/InsightSoftwareConsortium/ITK-Wasm)
 
-*itk-wasm* combines [ITK](https://www.itk.org/) and
+*ITK-Wasm* combines [ITK](https://www.itk.org/) and
 [WebAssembly](https://webassembly.org/) to enable high-performance spatial
 analysis in a web browser, Node.js, Python, and reproducible execution across
 programming languages and hardware architectures.
@@ -27,7 +27,7 @@ The project provides tools to a) build C/C++ code to
 JavaScript/TypeScript/Python data structures, and traditional file formats, c)
 transfer data efficiently in and out of the WebAssembly runtime, and d)
 asynchronous, parallel execution of processing pipelines in a worker pool.
-*itk-wasm* can be used to execute [ITK](https://www.itk.org/)
+*ITK-Wasm* can be used to execute [ITK](https://www.itk.org/)
 or arbitrary C++ codes in the browser, on a
 workstation / server with [Node.js](https://nodejs.org/) or [Python](https://python.org), or standalone
 execution and wrapped in [WASI](https://wasi.dev/) runtimes.

README.md

@@ -51,7 +51,7 @@
 # Furo options
 html_theme_options = {
     "top_of_page_button": "edit",
-    "source_repository": "https://github.com/InsightSoftwareConsortium/itk-wasm/",
+    "source_repository": "https://github.com/InsightSoftwareConsortium/ITK-Wasm/",
     "source_branch": "main",
     "source_directory": "docs",
 }

docs/conf.py

@@ -1,6 +1,6 @@
 # Interface Types
 
-itk-wasm execution pipelines support the following [interface types](https://github.com/InsightSoftwareConsortium/itk-wasm/tree/main/src/core/InterfaceTypes.ts):
+itk-wasm execution pipelines support the following [interface types](https://github.com/InsightSoftwareConsortium/ITK-Wasm/tree/main/src/core/InterfaceTypes.ts):
 
 - [TextFile](../typescript/interface_types/TextFile)
 - [BinaryFile](../typescript/interface_types/BinaryFile)
@@ -15,7 +15,7 @@ These interfaces types are supported in the [Emscripten interface](../typescript
 
 ---
 
-The following [CLI11](https://github.com/CLIUtils/CLI11) [`itk::wasm::Pipeline`](https://github.com/InsightSoftwareConsortium/itk-wasm/tree/main/include/itkPipeline.h) components can be included in a C++ to ingest and produce these interface types. For `Input` types, use `Get()` to get the corresponding C++ object value after `ITK_WASM_PARSE_ARGS` is called. For `Output` types, use `Set(value)` to output the value before `main` exits. For example,
+The following [CLI11](https://github.com/CLIUtils/CLI11) [`itk::wasm::Pipeline`](https://github.com/InsightSoftwareConsortium/ITK-Wasm/tree/main/include/itkPipeline.h) components can be included in a C++ to ingest and produce these interface types. For `Input` types, use `Get()` to get the corresponding C++ object value after `ITK_WASM_PARSE_ARGS` is called. For `Output` types, use `Set(value)` to output the value before `main` exits. For example,
 
 ```cpp
 #include "itkPipeline.h"

docs/cxx/interface_types.md

@@ -24,7 +24,7 @@ int main() {
 }
 ```
 
-[The example](https://github.com/InsightSoftwareConsortium/itk-wasm/tree/main/examples/debugging) provides npm scripts as a convenient way to execute debugging commands that you may also invoke directly in a command line shell.
+[The example](https://github.com/InsightSoftwareConsortium/ITK-Wasm/tree/main/examples/debugging) provides npm scripts as a convenient way to execute debugging commands that you may also invoke directly in a command line shell.
 
 To run these examples, first [install and test](./hello_world) Podman or Docker and Node/NPM. Then, install the package dependencies and run the example commands.
 

docs/cxx/tutorial/debugging.md

@@ -6,7 +6,7 @@ This example walks through how to compile a *hello world* executable written in
 
 Before getting started, make sure [Node.js](https://nodejs.org/en/download/) and [Podman (recommended)](https://podman.io/docs/installation) or [Docker](https://docs.docker.com/install/) are installed. On Linux, make sure you can run [`podman` or `docker` without `sudo`](https://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo). On Windows, we highly recommend [Podman](https://podman.io/docs/installation).
 
-While we recommend following along step-by-step, the complete example can also be found in the [`examples/` directory of the project repository](https://github.com/InsightSoftwareConsortium/itk-wasm/tree/main/examples/hello-world).
+While we recommend following along step-by-step, the complete example can also be found in the [`examples/` directory of the project repository](https://github.com/InsightSoftwareConsortium/ITK-Wasm/tree/main/examples/hello-world).
 
 Let's get started! 🚀
 

docs/cxx/tutorial/hello_world.md

@@ -45,7 +45,7 @@ cmake -BITK-build -SITK -DBUILD_TESTING=OFF -DModule_MeshToPolyData=ON
 cmake --build ITK-build
 
 # Build the WebAssemblyInterface module from this module against ITK
-git clone https://github.com/InsightSoftwareConsortium/itk-wasm
+git clone https://github.com/InsightSoftwareConsortium/ITK-Wasm
 cmake -Bitk-wasm-build -Sitk-wasm -DBUILD_TESTING=ON -DITK_DIR=$PWD/ITK-build
 cmake --build itk-wasm-build
 
@@ -108,7 +108,7 @@ Development requires:
 To build and test the CLI,
 
 ```sh
-git clone https://github.com/InsightSoftwareConsortium/itk-wasm
+git clone https://github.com/InsightSoftwareConsortium/ITK-Wasm
 cd itk-wasm/packages/core/typescript/itk-wasm
 pnpm install
 pnpm build
@@ -128,7 +128,7 @@ The development of `itk-wasm` is described above in the Command line interface s
 To develop the `itkwasm` Python package, which configured with [hatch](https://hatch.pypa.io/latest/):
 
 ```sh
-git clone https://github.com/InsightSoftwareConsortium/itk-wasm
+git clone https://github.com/InsightSoftwareConsortium/ITK-Wasm
 cd itk-wasm/packages/core/python/itkwasm
 
 pip install hatch
@@ -236,7 +236,7 @@ and rebuild whenever the documentation changes.
 [C++ compiler toolchain]: https://docs.itk.org/en/latest/supported_compilers.html
 [CMake]: https://cmake.org
 [conventional commit]: https://www.conventionalcommits.org/en/v1.0.0/#summary
-[current repository and branch]: https://github.com/InsightSoftwareConsortium/itk-wasm/blob/main/src/docker/itk-wasm-base/Dockerfile#L39-L41
+[current repository and branch]: https://github.com/InsightSoftwareConsortium/ITK-Wasm/blob/main/src/docker/itk-wasm-base/Dockerfile#L39-L41
 [data.kitware.com]: https://data.kitware.com/
 [FileBase]: https://filebase.com/
 [hatch]: https://hatch.pypa.io/latest/

docs/development/hacking_itk_wasm.md

@@ -82,7 +82,7 @@ The io packages are:
 2. `@itk-wasm/mesh-io`
 3. `@itk-wasm/dicom`
 
-An example that vendors these package's webassembly assets into an application for deployment can be found in the [Vite-based test applcation configuration](https://github.com/InsightSoftwareConsortium/itk-wasm/blob/main/packages/mesh-io/typescript/vite.config.js).
+An example that vendors these package's webassembly assets into an application for deployment can be found in the [Vite-based test applcation configuration](https://github.com/InsightSoftwareConsortium/ITK-Wasm/blob/main/packages/mesh-io/typescript/vite.config.js).
 
 ### DICOM image IO functions