Skip to content

Commit

Permalink
ENDOC-418B change dev.entango.org to developer.entando.com
Browse files Browse the repository at this point in the history
  • Loading branch information
Jinah Yun-Mitchell authored and Jinah Yun-Mitchell committed Feb 3, 2022
1 parent be68cdb commit 350ad7a
Show file tree
Hide file tree
Showing 13 changed files with 46 additions and 46 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

This is a source code repository.

For more information and documentation visit: https://dev.entando.org, or https://forum.entando.org. Or for the latest news or product information please visit the main website: https://www.entando.com.
For more information and documentation visit: https://developer.entando.com, or https://forum.entando.org. Or for the latest news or product information please visit the main website: https://www.entando.com.

See the vuepress/README for information on viewing the documentation locally or building from source.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ in some datacenter of your favorite hosting cloud provider.

We assume that you have already a kubernetes cluster up and running (also a minikube running on your local machine), that
you know how to write a yaml file for kubernetes and that you already have your docker images
(http://dev.entando.org/#_docker_overview) published on your docker registry and of course you have kubectl installed
(http://developer.entando.com/#_docker_overview) published on your docker registry and of course you have kubectl installed
(https://kubernetes.io/docs/tasks/tools/install-kubectl/[how to install kubectl]).

[[getting-started-k8s]]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ Entando is a built to be a very light framework requiring limited runtime resour
3. Establish if you can get a K8S cluster admin role for the controllers
4. Download these files for installation

* link:https://dev.entando.org/resources/crds.zip[CRDS]
* link:https://dev.entando.org/resources/custom_resources_yamls.zip[Custom Resource Yamls]
* link:https://developer.entando.com/resources/crds.zip[CRDS]
* link:https://developer.entando.com/resources/custom_resources_yamls.zip[Custom Resource Yamls]

== INTRODUCTION
Many of the services and containers deployed in an Entando 6 instance are meant to be deployed once and be shared
Expand Down
4 changes: 2 additions & 2 deletions docs/src/main/asciidoc/entando-5.3.0/redhat/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -871,10 +871,10 @@ <h4 id="_links_and_resources">1.5.5. LINKS AND RESOURCES</h4>
<p>Explore the code on GitHub: <a href="https://github.com/entando" class="bare">https://github.com/entando</a></p>
</li>
<li>
<p>See our Getting Started guide: <a href="http://dev.entando.org/#getting-started" class="bare">http://dev.entando.org/#getting-started</a></p>
<p>See our Getting Started guide: <a href="http://developer.entando.com/#getting-started" class="bare">http://developer.entando.com/#getting-started</a></p>
</li>
<li>
<p>See our Custom App Building guide: <a href="http://dev.entando.org/#_custom_app_building_with_entando" class="bare">http://dev.entando.org/#_custom_app_building_with_entando</a></p>
<p>See our Custom App Building guide: <a href="http://developer.entando.com/#_custom_app_building_with_entando" class="bare">http://developer.entando.com/#_custom_app_building_with_entando</a></p>
</li>
<li>
<p>Contribute to the software: <a href="https://central.entando.com/en/community.page" class="bare">https://central.entando.com/en/community.page</a></p>
Expand Down
28 changes: 14 additions & 14 deletions docs/src/main/asciidoc/entando-5.3.0/release-notes/current.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@
=== NEW CAPABILITIES AND FEATURES
=== DOCUMENTATION AND DEPLOYMENT
* New OpenShift templates and documentation including a new getting started experience to deploy Entando applications on OpenShift
** See: http://dev.entando.org/#entando-on-openshift
** See: http://developer.entando.com/#entando-on-openshift
* New examples, documentation, and templates to deploy Entando applications and AWS, Azure, and Google Cloud Engine using Kubernetes
** See: http://dev.entando.org/#_cloud_deployments_on_aws_azure_and_gce
** See: http://developer.entando.com/#_cloud_deployments_on_aws_azure_and_gce
* Added documentation and examples for deploying using an Oracle database

=== CONTENT MANAGEMENT
Expand All @@ -26,12 +26,12 @@
by type from versioning plugin. Generally useful when high volume content
delivered by API is generating large numbers of history records.
* For updated CMS documentation and how to use the new features see:
** http://dev.entando.org/#_content_management_system
** http://developer.entando.com/#_content_management_system

=== DIGITAL EXCHANGE
The release of Entando 5.1.0 includes the tech preview release of the Entando Digital Exchange which is a new model for distributing and installing Entando components. This release includes the ability to install and manage all of the UI elements of an Entando application. Follow our blog and YouTube channels for more to come on the Digital Exchange.
For documentation and getting started see:
http://dev.entando.org/#_digital_exchange
http://developer.entando.com/#_digital_exchange

=== APIs AND ENDPOINTS
* Added new PATCH API capability to merge changes to page settings endpoints and established the framework for applying a PATCH in a custom API
Expand Down Expand Up @@ -97,8 +97,8 @@ Added the ability to disable the complete button in the task list

=== LINKS AND RESOURCES
* Explore the code on GitHub: https://github.com/entando
* See our Getting Started guide: http://dev.entando.org/#getting-started
* See our Custom App Building guide: http://dev.entando.org/#_custom_app_building_with_entando
* See our Getting Started guide: http://developer.entando.com/#getting-started
* See our Custom App Building guide: http://developer.entando.com/#_custom_app_building_with_entando
* Contribute to the software: https://central.entando.com/en/community.page


Expand Down Expand Up @@ -140,8 +140,8 @@ None

=== LINKS AND RESOURCES
* Explore the code on GitHub: https://github.com/entando
* See our Getting Started guide: http://dev.entando.org/#getting-started
* See our Custom App Building guide: http://dev.entando.org/#_custom_app_building_with_entando
* See our Getting Started guide: http://developer.entando.com/#getting-started
* See our Custom App Building guide: http://developer.entando.com/#_custom_app_building_with_entando
* Contribute to the software: https://central.apps.entando.com/en/community.page


Expand Down Expand Up @@ -178,12 +178,12 @@ This document contains release notes for Entando 5.0.1.

* This release includes the addition of Swagger API documentation on top of the existing Entando REST endpoints
* Entando applications can extend Entando APIs and configure endpoints to be exposed via Swagger
* Learn more here: http://dev.entando.org/#_configuring_swagger_optional
* Learn more here: http://developer.entando.com/#_configuring_swagger_optional

*REST API Definition*

* Resolved a bug that prevented custom package scans from exposing endpoints in Entando REST endpoints
* Learn more about exposing REST endpoints in an Entando application: http://dev.entando.org/#_building_a_rest_api
* Learn more about exposing REST endpoints in an Entando application: http://developer.entando.com/#_building_a_rest_api

*Red Hat Process Automation Manager (PAM) plugin*

Expand Down Expand Up @@ -262,8 +262,8 @@ Some dependencies in 5.0.1 still reference snapshot versions of components and o
=== Links and Resources

* Explore the code on GitHub: https://github.com/entando
* See our Getting Started guide: http://dev.entando.org/#getting-started
* See our Custom App Building guide: http://dev.entando.org/#_custom_app_building_with_entando
* See our Getting Started guide: http://developer.entando.com/#getting-started
* See our Custom App Building guide: http://developer.entando.com/#_custom_app_building_with_entando
* Contribute to the software: https://central.apps.entando.com/en/community.page


Expand Down Expand Up @@ -367,6 +367,6 @@ We have performed security scans as part of the Entando 5 software release to en

=== LINKS AND RESOURCES
* Explore the code on GitHub: https://github.com/entando
* See our Getting Started guide: http://dev.entando.org/#getting-started
* See our Custom App Building guide: http://dev.entando.org/#_custom_app_building_with_entando
* See our Getting Started guide: http://developer.entando.com/#getting-started
* See our Custom App Building guide: http://developer.entando.com/#_custom_app_building_with_entando
* Contribute to the software: https://central.entando.com/en/community.page
2 changes: 1 addition & 1 deletion vuepress/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ We have a simple versioning system in place currently. Creating a new version in
### Publishing
We have two utility scripts used to publish the docs to staging and publishing, `vuepress/deploy-staging.sh` and `vuepress/deploy-prod.sh`, respectively.
- `deploy-staging.sh` sends files to a Github Pages site available at <https://entando.github.io/entando-docs/> and the script runs with no commands. You should notify the team via slack when updating staging.
- `deploy-prod.sh` sends files to a Github Pages site available at <https://dev.entando.org> and the script runs with two commands - the target branch and a comment which should include the list of ticket numbers included in the publish.
- `deploy-prod.sh` sends files to a Github Pages site available at <https://developer.entando.com> and the script runs with two commands - the target branch and a comment which should include the list of ticket numbers included in the publish.
- Both scripts use a Vuepress-typical force-push. You'll need privileges on the corresponding repository and/or branch to complete the publish.
- After running `deploy-prod.sh` you should tag the current commit with the current date. This will make it easier to rollback to a previous publish if there are issues.

Expand Down
2 changes: 1 addition & 1 deletion vuepress/deploy-prod.sh
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ npm run docs:build
cd docs/.vuepress/dist

# if you are deploying to a custom domain
echo 'dev.entando.org' > CNAME
echo 'developer.entando.com' > CNAME

git init
git add -A
Expand Down
Loading

0 comments on commit 350ad7a

Please sign in to comment.