enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-11-22 22:10:15 +03:00
Code Issues Projects Releases Wiki Activity

Update all references to dev.enso.org

Browse Source
This commit is contained in:
Ara Adkins 2021-04-07 20:16:05 +01:00
parent 6d3ebedf27
commit 9f60e22508
No known key found for this signature in database
GPG Key ID: D9EB39C019A0D6E1
6 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -214,7 +214,7 @@ If you would like to gain a better understanding of the principles on which Enso
is based, or just delve into the why's and what's of Enso's design, please take
a look in the [`docs/` folder](./docs/). It is split up into subfolders for each
component of Enso. You can view this same documentation in a rendered form at
[the developer docs website](https://dev.enso.org).
[the developer docs website](https://enso.org/docs/developer).
This folder also contains a document on Enso's
[design philosophy](./docs/enso-philosophy.md), that details the thought process

5
docs/CONTRIBUTING.md
View File

@ -715,8 +715,9 @@ the best results through open collaboration.
Documentation improvements are very welcome! For now, the main documentation
available is the _developer_ documentation for the language, which can be found
at the [dev docs site](https://dev.enso.org). The source for this documentation
is found in the [`docs/`](.) folder, and can be altered from there.
at the [dev docs site](https://enso.org/docs/developer). The source for this
documentation is found in the [`docs/`](.) folder, and can be altered from
there.
Documentation pull requests will be reviewed in exactly the same way as normal
pull requests.

2
docs/distribution/packaging.md
View File

@ -200,7 +200,7 @@ definitions.
For more information on how visualization definitions should work with the Enso
IDE, see
[this example](https://dev.enso.org/docs/ide/product/visualizations.html#custom-visualization-example).
[this example](https://enso.org/docs/developer/docs/ide/product/visualizations.html#custom-visualization-example).
## Build Reproducibility

2
engine/launcher/src/main/scala/org/enso/launcher/releases/fallback/staticwebsite/FileStorageFallbackReleaseProvider.scala
View File

@ -23,7 +23,7 @@ import scala.util.{Failure, Success, Try}
* release tag which contain the listed assets.
*
* It must adhere to the fallback mechanism specification as defined at
* [[https://dev.enso.org/docs/enso/distribution/fallback-launcher-release-infrastructure.html#fallback-infrastructure-specification]].
* [[https://enso.org/docs/developer/docs/enso/distribution/fallback-launcher-release-infrastructure.html#fallback-infrastructure-specification]].
*/
class FileStorageFallbackReleaseProvider(
storage: FileStorage,

2
engine/launcher/src/main/scala/org/enso/launcher/releases/fallback/staticwebsite/StaticWebsiteFallbackReleaseProvider.scala
View File

@ -22,7 +22,7 @@ import scala.util.Try
* release tag which contain the listed assets.
*
* It must adhere to the fallback mechanism specification as defined at
* [[https://dev.enso.org/docs/enso/distribution/fallback-launcher-release-infrastructure.html#fallback-infrastructure-specification]].
* [[https://enso.org/docs/developer/docs/enso/distribution/fallback-launcher-release-infrastructure.html#fallback-infrastructure-specification]].
*
* @param bucketRoot root URI that should contain the described files
*/

4
lib/rust/lexer/definition/src/token.rs
View File

@ -1,8 +1,8 @@
//! This file defines the various tokens requried by the Enso lexer.
//!
//! This file makes heavy use of terminology from the Enso design documentation, particularly the
//! [syntax](https://dev.enso.org/docs/enso/syntax) documentation. For the sake of brevity, many
//! terms will _not_ be defined here.
//! [syntax](https://enso.org/docs/developer/docs/enso/syntax) documentation. For the sake of
//! brevity, many terms will _not_ be defined here.
use crate::prelude::*;