add baseurls to links

_why-cloud/security-compliance.md

@@ -11,7 +11,7 @@ But even the most secure cloud solution still requires you to maintain some secu
 
 ## Responsibilities
 
-The security and compliance you’re responsible for depends on what [type of cloud solution](/why-cloud/basics/) you procure. Software as a service (SaaS) users are typically responsible for very little; platform as a service users only have to secure their applications; on the other hand, infrastructure as a service (IaaS) users will have to secure platforms and software themselves. A good rule of thumb is that you’re usually responsible for what you can customize; if it’s automatically set up for you, your vendor is likely responsible for its security and compliance. (However, there are exceptions to this: for example, sometimes a vendor will provide the tools you need to maintain security and compliance, but it’ll be your responsibility to make sure that tool is used correctly.)
+The security and compliance you’re responsible for depends on what [type of cloud solution]({{ site.baseurl }}/why-cloud/basics/) you procure. Software as a service (SaaS) users are typically responsible for very little; platform as a service users only have to secure their applications; on the other hand, infrastructure as a service (IaaS) users will have to secure platforms and software themselves. A good rule of thumb is that you’re usually responsible for what you can customize; if it’s automatically set up for you, your vendor is likely responsible for its security and compliance. (However, there are exceptions to this: for example, sometimes a vendor will provide the tools you need to maintain security and compliance, but it’ll be your responsibility to make sure that tool is used correctly.)
 
 Understanding this shared responsibility model is fundamental to procuring and implementing cloud. That way, you know what you’re getting for your money — and you won’t be surprised down the line by requirements you thought were being covered by a vendor.
 

_why-cloud/technical-capabilities.md

@@ -37,4 +37,4 @@ In addition to new functionality, cloud computing offers new concepts and ways o
 
 * **Virtualization** is effectively the same thing as having virtual machines (i.e., multiple instances of the same operating system on a physical computer). Instead of running these virtual machines yourself, however, your CSP will typically provide the virtualization for you. (Note: Software licensing can become sticky in virtualization, because providers may charge you based on how many virtual instances you have instead of how many physical computers you have — since you don’t own those computers yourself anymore.) 
 
-As you complete your [cloud inventory and prioritization](/implementation/technical/migration/), make sure you take a deep dive into the capabilities cloud service providers have to offer. There’s likely to be functionality you didn’t have on-prem that could change your opinion about which services should be ported first. For example, records-keeping doesn’t seem like a particularly interesting system to port to the cloud — however, some cloud service providers offer exceptionally low-cost storage in exchange for high latency rates, which may be an acceptable trade-off for files you don’t plan to look at often (or ever). Think holistically about your needs, and then explore how cloud solutions could help meet them. 
+As you complete your [cloud inventory and prioritization]({{ site.baseurl }}/implementation/technical/migration/), make sure you take a deep dive into the capabilities cloud service providers have to offer. There’s likely to be functionality you didn’t have on-prem that could change your opinion about which services should be ported first. For example, records-keeping doesn’t seem like a particularly interesting system to port to the cloud — however, some cloud service providers offer exceptionally low-cost storage in exchange for high latency rates, which may be an acceptable trade-off for files you don’t plan to look at often (or ever). Think holistically about your needs, and then explore how cloud solutions could help meet them. 

pages/acquisition.md

@@ -17,9 +17,9 @@ Here are some tips to keep in mind as you work with your contract officers.
 * **Understand the limits**. Current financial management systems weren’t designed for commercial cloud computing models; in fact, they work directly against the intended business advantages of cloud computing. If progress is slow, it isn’t because contracting officers are being contrary — it’s because they’re trying to fit a square peg into a round hole.
 * **Research different vehicles**. There are multiple ways to acquire cloud solutions, and each has its own strengths. [Within GSA alone](https://www.gsa.gov/technology/technology-programs) you can choose from IT Schedule 70, government-wide acquisition contracts (GWACs), and software blanket purchase agreements (BPAs). 
 * **Explore Acquisition Gateway**. [Acquisition Gateway](https://hallways.cap.gsa.gov/login-information) offers resources and contacts for both contract officers and buyers. Within the tool you can see current and past successful contracts, as well as points of contact to learn more.
-* **Share best practices**. Ask colleagues at other agencies about what’s worked for them. There may be templates or guidance they can share. Also, our [Procurement process](/acquisition/procurement-process/) page can help guide acquisition officers who haven’t worked with cloud contracts before.
+* **Share best practices**. Ask colleagues at other agencies about what’s worked for them. There may be templates or guidance they can share. Also, our [Procurement process]({{ site.baseurl }}/acquisition/procurement-process/) page can help guide acquisition officers who haven’t worked with cloud contracts before.
 * **Don’t blame acquisition for other challenges**. Because cloud migration is complex, it can be tempting to assign all the blame to contracting. But many of the individual steps, like taking inventory or understanding pricing differences between vendors, are less about contracts than they are about the process itself.
 
-Although it can be confusing, government cloud acquisition is definitely possible — agencies across government are acquiring and implementing cloud systems every day. And if you have more questions about cloud acquisition, [we can help](/105-OverviewCloudSolutions/support/). 
+Although it can be confusing, government cloud acquisition is definitely possible — agencies across government are acquiring and implementing cloud systems every day. And if you have more questions about cloud acquisition, [we can help]({{ site.baseurl }}/105-OverviewCloudSolutions/support/). 
 
 

pages/acquisition/procurement-process.md

@@ -5,7 +5,7 @@ permalink: /acquisition/procurement-process/
 sidenav_ref: acquisition
 ---
 
-As established in the [Basics](/why-cloud/basics/) section, there is no one “cloud” — rather, there are a handful of cloud types and cloud models. Cross that with the fact that government uses multiple types of contracts and offers multiple ways of purchasing, and you’ll find that there’s no shortage of options for getting cloud deployed at your agency. You’ll want to conduct market research — about both what cloud solutions meet your mission needs and which acquisition strategies can get you those services.
+As established in the [Basics]({{ site.baseurl }}/why-cloud/basics/) section, there is no one “cloud” — rather, there are a handful of cloud types and cloud models. Cross that with the fact that government uses multiple types of contracts and offers multiple ways of purchasing, and you’ll find that there’s no shortage of options for getting cloud deployed at your agency. You’ll want to conduct market research — about both what cloud solutions meet your mission needs and which acquisition strategies can get you those services.
 
 ## Determine your mission needs
 
@@ -19,24 +19,24 @@ Your acquisition team are experts, and they — along with resources like GSA’
 
 * **What will work best for your agency**? Finding the right tech is only half the battle — you also need to navigate your own internal processes. Ask your acquisition team what’s worked for them so far, especially if they’ve already bought cloud products or services for someone else within the organization.
 
-* **Which cloud deployment do you want**? Take a look at your security needs and determine if you take advantage of a public (or government cloud) or if you’ll need to leverage a private cloud for sensitive assets. Read more about these options on our [Basics](/why-cloud/basics/) page.
+* **Which cloud deployment do you want**? Take a look at your security needs and determine if you take advantage of a public (or government cloud) or if you’ll need to leverage a private cloud for sensitive assets. Read more about these options on our [Basics]({{ site.baseurl }}/why-cloud/basics/) page.
 
-* **Which cloud model do you need**? You’ll first need to see which [products](/cloud-solutions/) meet your need. You can then determine if those solutions are infrastructure as a service (IaaS), platform as a service (PaaS), or software as a service (SaaS). SaaS solutions may be easier to procure than other models because [FedRAMP](https://fedramp.gov/) offers a separate authorization program for what they call "[low-impact software as a service](https://tailored.fedramp.gov/).”
+* **Which cloud model do you need**? You’ll first need to see which [products]({{ site.baseurl }}/cloud-solutions/) meet your need. You can then determine if those solutions are infrastructure as a service (IaaS), platform as a service (PaaS), or software as a service (SaaS). SaaS solutions may be easier to procure than other models because [FedRAMP](https://fedramp.gov/) offers a separate authorization program for what they call "[low-impact software as a service](https://tailored.fedramp.gov/).”
 
 ## Develop an acquisition strategy
 Once you’ve got these questions answered, you can start making decisions about what kind of procurement you want to make. Every agency is different, but if you’re purchasing from GSA, here are the major considerations. 
 
 * **Which vehicle will you choose**? At GSA, cloud services are available via [IT Schedule 70](https://www.gsa.gov/technology/technology-purchasing-programs/it-schedule-70) and [governmentwide acquisition programs (GWACs)](https://www.gsa.gov/technology/technology-purchasing-programs/governmentwide-acquisition-contracts-gwacs).  Each has their advantages — for example, GWACs offer lower prices via pooled purchases, while Schedule 70 has a broader range of products and services available.
 
 
-* **Will you bundle technology with labor**? It’s possible to procure both tech and assistance at the same time. Depending on your agency’s needs, this may or may not be necessary. For more, take a look at our sample [Statement of Objectives on Cloud Migration Services](/templates/statement-of-objectives/).
+* **Will you bundle technology with labor**? It’s possible to procure both tech and assistance at the same time. Depending on your agency’s needs, this may or may not be necessary. For more, take a look at our sample [Statement of Objectives on Cloud Migration Services]({{ site.baseurl }}/templates/statement-of-objectives/).
 
 * **Which type of contract should you use**? Just as in the rest of government, there are three types of contract: firm-fixed-price (FFP), cost reimbursement, and time and materials (T&M). Once again, there are advantages and disadvantages to each; for example, FFP contracts are simpler but won’t ever let you underspend if you need less resource than you anticipated.
 
 * **Will you buy directly or through a cloud service reseller**? Some cloud services are directly available on GSA IT Schedule 70, and some are available via resellers who can help you access discounted pricing rates.
 
 ## Leverage our acquisition templates
-Once you’ve conducted the market research to determine which solutions meet your need, how to bundle services and labor, and where to solicit your request, you can leverage our cloud-friendly [acquisition templates](/templates/). 
+Once you’ve conducted the market research to determine which solutions meet your need, how to bundle services and labor, and where to solicit your request, you can leverage our cloud-friendly [acquisition templates]({{ site.baseurl }}/templates/). 
 Get help
 
-Cloud acquisition is rarely simple, but if done well it can drastically improve your capabilities and save money, too. If you’d like more assistance with acquisition, visit our [support](/support/) page.
+Cloud acquisition is rarely simple, but if done well it can drastically improve your capabilities and save money, too. If you’d like more assistance with acquisition, visit our [support]({{ site.baseurl }}/support/) page.

pages/acquisition/procurement-process/pricing.md

@@ -6,7 +6,7 @@ sidenav_ref: acquisition
 parent: /acquisition/procurement-process/
 ---
 
-Because cloud is built around services, not products, it can be difficult to compare vendors apples-to-apples. Each cloud service provider (CSP) will offer different functionality, will be backed up by different infrastructure configurations, and will offer billing in different units. The more customizable your [cloud model](/why-cloud/basics/), the more complicated these calculations are likely to be — software as a service (SaaS) solutions are typically sold via individual fixed-price licenses, infrastructure as a service (IaaS) solutions are typically metered, and platform as a service (PaaS) solutions can be either (and sometimes both).
+Because cloud is built around services, not products, it can be difficult to compare vendors apples-to-apples. Each cloud service provider (CSP) will offer different functionality, will be backed up by different infrastructure configurations, and will offer billing in different units. The more customizable your [cloud model]({{ site.baseurl }}/why-cloud/basics/), the more complicated these calculations are likely to be — software as a service (SaaS) solutions are typically sold via individual fixed-price licenses, infrastructure as a service (IaaS) solutions are typically metered, and platform as a service (PaaS) solutions can be either (and sometimes both).
 
 While cloud’s pricing structure is different than other products or services you may have worked with before, there are ways to make these differences work on your behalf. Here are a few things to keep in mind as you consider your investment in cloud.
 

pages/implementation.md

@@ -9,10 +9,10 @@ Cloud adoption is bigger than just lift and shift — it’s an opportunity to r
 
 In this section, you’ll learn more about implementing cloud at your agency. We’ve broken this work into two discrete chunks.
 
-  * **[Business considerations](/business/)** takes you through the human side of cloud deployment. What skills does your team need? How do you manage change? What’s the best approach to training?
+  * **[Business considerations]({{ site.baseurl }}/business/)** takes you through the human side of cloud deployment. What skills does your team need? How do you manage change? What’s the best approach to training?
 
 
-* **[Technical considerations](/technical/)** gives you an overview of the mechanics of getting cloud deployed at your agency. How do you take inventory of your current assets? What maintenance will you be responsible for? How do you migrate and scale effectively?
+* **[Technical considerations]({{ site.baseurl }}/technical/)** gives you an overview of the mechanics of getting cloud deployed at your agency. How do you take inventory of your current assets? What maintenance will you be responsible for? How do you migrate and scale effectively?
 
 But whether you’re focusing on the business or the technical aspects of implementation, there are a few universal principles that are worth keeping in mind. 
 

pages/implementation/technical.md

@@ -15,7 +15,7 @@ Once you’ve documented your existing assets, move to rationalization. What’s
 
 After you know this, the final step is actually planning for migration. This includes risk assessments and financial considerations. What can you afford to do now, and what can be budgeted for in the new fiscal year? What’s a good system to use as a pilot — something that can accommodate your learning curve?
 
-If this isn’t work you have capacity to do on your own, there are vendors who can help support you. At the request of OMB, GSA has developed a set of [statement of objectives (SOO)](/acquisition/templates/statement-of-objectives/) templates you can use to acquire migration support for things like assessment, planning, execution, and decommissioning. They’re available in our [templates](/acquisition/templates/) section.
+If this isn’t work you have capacity to do on your own, there are vendors who can help support you. At the request of OMB, GSA has developed a set of [statement of objectives (SOO)]({{ site.baseurl }}/acquisition/templates/statement-of-objectives/) templates you can use to acquire migration support for things like assessment, planning, execution, and decommissioning. They’re available in our [templates]({{ site.baseurl }}/acquisition/templates/) section.
 
 But whether you take it on yourself or bring in outside help, all agencies — regardless of their existing network documentation — should map out their enterprise networks when they decide to move to the cloud. Many agencies thought they knew their networks were surprised when they entered the discovery phase and found unknown endpoints or unexpected traffic patterns. 
 

pages/implementation/technical/migration.md

@@ -14,7 +14,7 @@ Everyone’s modernization is different, but there are some best practices that
 
    Whether you’re handling your agency’s transition yourself or bringing in a vendor to support, getting a sense of how to deploy apps in the cloud can be useful for anyone expecting to manage anything more custom than software as a service (SaaS). Even deploying a “Hello, world!” is a step towards that understanding.
 
-* **Work backwards**. By the time you’re migrating actual programs you should already have your [audit of existing IT resources](/implementation/technical/), as well as rationalizations and risk assessments. Pick something simple and low risk for your first real migration or deployment, not a mission critical service. That way, your inevitable learning curve won’t interfere with mission goals, and you won’t to deal with added pressure you don’t need.
+* **Work backwards**. By the time you’re migrating actual programs you should already have your [audit of existing IT resources]({{ site.baseurl }}/implementation/technical/), as well as rationalizations and risk assessments. Pick something simple and low risk for your first real migration or deployment, not a mission critical service. That way, your inevitable learning curve won’t interfere with mission goals, and you won’t to deal with added pressure you don’t need.
 
 
 * **Refine your processes**. Don’t just move things to the cloud — pay attention to the way you move them. Keep track of every step along the way, and at the end of each migration, talk with your team about what worked and what didn’t. By experimenting with different ways of doing things, and by replicating your successes, you’ll be able to make each migration process a little better than the one before it. Think about which manual processes can be further automated.