Change Details

Description: static site implementing https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal Timeline: FY 21/22 Q4 (April-June 2022) Diagram: {nav icon=firefox, name=browser > icon=cloud, name=Internet > icon=server, name=developer-portal} Technologies: python based static site generator, but deployable asset will be a container with a web server (likely nginx) and a pile of static assets (html, js, css, images) Point person: @bd808 This could be deployed as a more traditional static site as well, but the build process for generating the static content will be based on PipelineLib resulting in a Docker container, so deployment on a Kubernetes cluster seems "simple" once ingress is taken care of.

Description: static site implementing https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal. Demo instance at https://developer-portal.wmcloud.org/ Timeline: FY 21/22 Q4 (April-June 2022) Diagram: {nav icon=firefox, name=browser > icon=cloud, name=Internet > icon=server, name=developer-portal} Technologies: a [[https://docker-registry.wikimedia.org/wikimedia/wikimedia-developer-portal/tags/|single container with nginx and a pile of static assets (html, js, css, images)]. Static content is produced by a python based static site generator which executes in PipelineLib. Point person: @bd808 This could be deployed as a more traditional static site as well, but the build process for generating the static content will be based on PipelineLib resulting in a Docker container, so deployment on a Kubernetes cluster seems "simple" once ingress is taken care of.

Description: static site implementing https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal. Demo instance at https://developer-portal.wmcloud.org/ Timeline: FY 21/22 Q4 (April-June 2022) Diagram: {nav icon=firefox, name=browser > icon=cloud, name=Internet > icon=server, name=developer-portal} Technologies: python based static site generator, but deployable asset will be a container with a web server (likelya [[https://docker-registry.wikimedia.org/wikimedia/wikimedia-developer-portal/tags/|single container with nginx) and a pile of static assets (html, js, css, images)]. images)Static content is produced by a python based static site generator which executes in PipelineLib. Point person: @bd808 This could be deployed as a more traditional static site as well, but the build process for generating the static content will be based on PipelineLib resulting in a Docker container, so deployment on a Kubernetes cluster seems "simple" once ingress is taken care of.