Rename ocis-phoenix to ocis-web

docs/extensions/ocis-phoenix/_index.md

@@ -1,13 +0,0 @@
----
-title: "ownCloud Web"
-date: 2018-05-02T00:00:00+00:00
-weight: 20
-geekdocRepo: https://github.com/owncloud/ocis
-geekdocEditPath: edit/master/docs/extensions/ocis-phoenix
-geekdocFilePath: _index.md
-geekdocCollapseSection: true
----
-
-Note: Work in progress to rename Phoenix to ownCloud Web.
-
-This service embeds [Phoenix](https://github.com/owncloud/phoenix) to provide a UI for ownCloud Infinite Scale.

docs/extensions/settings/_index.md

@@ -15,7 +15,7 @@ for other extensions to register new settings within oCIS. It is responsible for
 settings values as well.
 
 For ease of use, this extension provides an ocis-web extension which allows users to change their settings values.
-Please refer to the [ocis-web extension docs]({{< relref "../../ocis/development/extensions/#external-phoenix-apps" >}})
+Please refer to the [ocis-web extension docs]({{< relref "../../ocis/development/extensions/#external-ownCloud-Web-apps" >}})
 for running ocis-web extensions.
 
 {{< mermaid class="text-center">}}

docs/extensions/web/_index.md

@@ -0,0 +1,10 @@
+---
+title: "ownCloud Web"
+date: 2018-05-02T00:00:00+00:00
+weight: 20
+geekdocRepo: https://github.com/owncloud/ocis
+geekdocEditPath: edit/master/docs/extensions/web
+geekdocFilePath: _index.md
+---
+
+This service embeds [ownCloud Web](https://github.com/owncloud/web) to provide a UI for ownCloud Infinite Scale.

docs/extensions/web/releasing.md

@@ -2,7 +2,7 @@
 title: "Releasing"
 weight: 40
 geekdocRepo: https://github.com/owncloud/ocis
-geekdocEditPath: edit/master/docs/extensions/ocis-phoenix
+geekdocEditPath: edit/master/docs/extensions/web
 geekdocFilePath: releasing.md
 ---
 
@@ -10,29 +10,29 @@ geekdocFilePath: releasing.md
 
 ## Releasing
 
-The next generation Web Frontend is shipped as an oCIS Extension. The `ocis-phoenix` extension is also embedded in the single binary and part of the `ocis server` command.
+The next generation Web Frontend is shipped as an oCIS Extension. The `ocis-web` extension is also embedded in the single binary and part of the `ocis server` command.
 
 To update this package within all the deliveries, we need to update the package in the following chain from the bottom to the top.
 
 ### Package Hierarchy
 
 - [ocis](https://githug.com/owncloud/ocis)
-    - [ocis-phoenix](https://github.com/owncloud/ocis-phoenix)
-      - [ocis-pkg](https://github.com/owncloud/ocis-pkg)
-      - [phoenix](https://github.com/owncloud/phoenix)
+    - [ocis-web](https://github.com/owncloud/ocis/tree/master/web)
+      - [ocis-pkg](https://github.com/owncloud/ocis/tree/master/ocis-pkg)
+      - [ownCloud Web](https://github.com/owncloud/web)
 
 #### Prerequisites
 
-Before updating the assets, make sure that [Phoenix](https://github.com/owncloud/phoenix) has been released first
+Before updating the assets, make sure that [ownCloud Web](https://github.com/owncloud/web) has been released first
 and take note of its release tag name.
 
-#### Updating ocis-phoenix
+#### Updating ocis-web
 
-1. Create a branch `release-$version`. in <https://github.com/owncloud/ocis-phoenix>
+1. Create a branch `release-$version`. in <https://github.com/owncloud/ocis>
 2. Create a Folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`.
 3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.
 4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> .
-5. Update the phoenix asset by adjusting the value of `PHOENIX_ASSETS_VERSION` at the top of the Makefile and specify the tag name of the latest [Phoenix release](https://github.com/owncloud/phoenix/tags).
+5. Update the ownCloud Web asset by adjusting the value of `WEB_ASSETS_VERSION` at the top of the Makefile and specify the tag name of the latest [ownCloud Web release](https://github.com/owncloud/web/tags).
 6. Run `make clean generate`.
 7. Create a changelog item for the update in the `changelog/$major.$minor.$patchVersion_YYYY-MM-DD` folder.
 8. Commit your changes.
@@ -41,7 +41,3 @@ and take note of its release tag name.
 11. Use `v$major.$minor.$patch` as a tag (the `v` prefix is important) and publish it.
 12. The tag and the Release artifacts will be created automatically.
 
-#### Next steps
-
-Next steps is usually updating the ocis-phoenix version in the [ocis](https://githug.com/owncloud/ocis) repository.
-