Rename formats doc to languages
This commit is contained in:
parent
2669f5b860
commit
62e11f37e0
|
@ -1,6 +1,6 @@
|
|||
# Mu Formats
|
||||
# Mu Languages
|
||||
|
||||
Mu cloud services are described to the toolchain with three logical formats: MetaMus, MuPack/MuIL, and MuGL.
|
||||
Mu cloud services are described to the toolchain with three languages: MetaMus, MuPack/MuIL, and MuGL.
|
||||
|
||||
At the highest level, developers write Mu packages using a high-level language. There are multiple languages to choose
|
||||
from, and each is a proper subset of an existing popular programming language; MuJS is a subset of JavaScript, MuPy is
|
|
@ -1,7 +1,7 @@
|
|||
# Mu Stacks
|
||||
|
||||
This document describes how Mu Stacks and Services show up in Mu's various [formats](formats.md) (MetaMus, MuPack, MuIL,
|
||||
and MuGS). Those are the definitive resources on the low-level formats, but this document describes the overall
|
||||
This document describes how Mu Stacks and Services show up in Mu's various [languages](languages.md) (MetaMus, MuPack,
|
||||
MuIL, and MuGS). Those are the definitive resources on the low-level formats, but this document describes the overall
|
||||
programming model that a developer will encounter. For more details on how this results in concrete resources
|
||||
provisioned in the target cloud provider, please refer to [the cloud targeting design document](clouds.md).
|
||||
|
||||
|
|
|
@ -104,7 +104,7 @@ creating new providers, which amounts to implementing create, read, update, and
|
|||
|
||||
More details are left to the respective design documents. Here are some key ones:
|
||||
|
||||
* [**Formats**](design/formats.md): An overview of Mu's three file formats: MetaMus, MuPack/MuIL, and MuGS.
|
||||
* [**Languages**](design/languages.md): An overview of Mu's three languages: MetaMus, MuPack/MuIL, and MuGS.
|
||||
* [**MuPack/MuIL**](design/mupack.md): A detailed description of Mu's packaging and computation formats.
|
||||
* [**Stacks**](design/stacks.md): An overview of how stacks are represented using the above fundamentals.
|
||||
* [**Dependencies**](design/deps.md): An overview of how package management and dependency management works.
|
||||
|
|
Loading…
Reference in a new issue