<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on Webscale Product Documentation</title><link>https://docs.webscale.com/docs/getting-started/</link><description>Recent content in Getting Started on Webscale Product Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.webscale.com/docs/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Contact Support</title><link>https://docs.webscale.com/docs/getting-started/support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/getting-started/support/</guid><description>&lt;p&gt;There are multiple ways to contact Webscale Support if you have queries or need help resolving an issue with Webscale products.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Normal support requests, such as information or changes to production systems, should be sent to &lt;a href="mailto:support@webscalenetworks.com"&gt;support@webscalenetworks.com&lt;/a&gt;
.&lt;/li&gt;
&lt;li&gt;Critical requests, such as issues that are impacting your users’ ability to checkout or purchase items through your site, should be sent to &lt;a href="mailto:critical@webscalenetworks.com"&gt;critical@webscalenetworks.com&lt;/a&gt;
.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There is also a &lt;a href="https://support.webscalenetworks.com" target="_blank"&gt;Support Portal&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
. Log in to the Support Portal to open new tickets or manage existing tickets.&lt;/p&gt;</description></item><item><title>How to Complete the Onboarding Questionnaire</title><link>https://docs.webscale.com/docs/getting-started/onboarding/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/getting-started/onboarding/</guid><description>&lt;p&gt;A new application needs to be integrated to the Webscale network in order to be added properly. This integration is customized to each application for the best performance. To ensure the integration is done accurately, Webscale&amp;rsquo;s onboarding team must gather some information about the application. To ensure communication flows properly, some information about your organization is also needed. Webscale&amp;rsquo;s onboarding team will send you a spreadsheet to gather this information.&lt;/p&gt;</description></item><item><title>Webscale Go-live Process</title><link>https://docs.webscale.com/docs/getting-started/go-live/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/getting-started/go-live/</guid><description>&lt;h2 id="what-to-expect-from-the-go-live-process"&gt;What to expect from the go-live process&lt;/h2&gt;
&lt;p&gt;Once your application has been fully integrated into Webscale’s network and tested, it will be ready to go live. Before the final go-live process can take place, there are some checks both you and Webscale will do to ensure a smooth transition.&lt;/p&gt;
&lt;h2 id="before-go-live"&gt;Before go-live&lt;/h2&gt;
&lt;p&gt;Before the site goes live, perform some testing to ensure the application works as expected. You will also work with Webscale’s team to ensure that important information and dates are agreed on to avoid any miscommunication, possible delays, or unforeseen downtime of the application.&lt;/p&gt;</description></item><item><title>How to Deploy Your Code on Webscale</title><link>https://docs.webscale.com/docs/getting-started/deploy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/getting-started/deploy/</guid><description>&lt;p&gt;The Webscale deployment process is a modern &lt;a href="https://en.wikipedia.org/wiki/CI/CD" target="_blank"&gt;CI/CD&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 pipeline, with your code being managed by source control and then deployed using &lt;a href="https://www.docker.com/" target="_blank"&gt;Docker&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 containers. This removes the majority of downtime associated with deploying the code for a new application or website. In the past, it was necessary to set your Magento application to maintenance mode while the build processes were run, often resulting in downtimes of at least 1-2 hours. Using this modern CI/CD pipeline not only ensures little to no downtime, but also allows you to fix any problems with the site much more quickly.&lt;/p&gt;</description></item></channel></rss>