Merge pull request #492 from mulesoft/W-12213767-add-policy-page

W 12213767 add policy page

Author: glenn-rodgers-sf

modules/ROOT/nav.adoc

@@ -50,6 +50,7 @@
  ** xref:enable-https-mule3-proxies.adoc[Enable HTTPS in Mule 3.x API Proxies]
   ** xref:proxy-mule3-elements.adoc[Filter Mule Headers in Mule 3.x API Proxies]
  ** xref:proxy-domain-support.adoc[Automatic Domain Support for Mule 4 API Proxies]
+* xref:manage-policies-overview.adoc[Policies]
 * xref:analytics-landing-page.adoc[View Analytics]
  ** xref:viewing-api-analytics.adoc[Review Analytics Usage]
  ** xref:analytics-chart.adoc[Review Analytics Charts Usage]

modules/ROOT/pages/manage-policies-overview.adoc

@@ -0,0 +1,54 @@
+= Gateway Policies in API Manager
+ifndef::env-site,env-github[]
+include::_attributes.adoc[]
+endif::[]
+:imagesdir: ../assets/images
+:page-aliases: 
+
+From API Manager, you can apply policies to APIs in Flex Gateway Connected Mode or in Mule Gateway.
+
+Policies enable you to enforce regulations to help manage security, control traffic, and improve adaptability of your APIs. For example, a policy can control authentication, access, allotted consumption, and service level access (SLA).
+
+With policies, you can implement these regulations with no modification to the code implementation. 
+
+Because the policies are implemented by the Gateway, policies are documented in the xref:gateway-home::gateway-overview.adoc[Gateway documentation]. For more information, see the xref:policies::policies-overview.adoc[Policy documentation] or use the links in the following sections.
+
+== Policies Included in Flex Gateway and Mule Gateway
+
+* xref:policies::policies-included-directory.adoc[Included Policies Directory]
+
+== Applying Policies in Flex Gateway Connected Mode and in Mule Gateway
+
+* xref:policies::policies-included-apply.adoc[Apply an Included Policy]
+
+== See Also
+
+* xref:policies::policies-included-reorder.adoc[]
+* xref:policies::policies-policy-categories.adoc[Policy Categories]
+* xref:policies::policies-compare-versions.adoc[Comparison of Mule 3 and Mule 4 Policies]
+* xref:policies::policies-flex-dataweave-support.adoc[DataWeave Support in Flex Gateway Policies]
+* xref:policies::policies-automated-overview.adoc[Automated Policies]
+* xref:policies::policies-resource-level-overview.adoc[Resource-Level Policies]
+* xref:policies::policies-custom-overview.adoc[Custom Policies]
+
+
+
+// You can apply policies to any HTTP-based APIs, such as:
+
+// An APIkit project
+
+// For example, deploy the APIkit project to Anypoint Platform using API Autodiscovery, and then apply a policy.
+
+// An API running on CloudHub
+
+// Design an API on Anypoint Platform, configure a proxy for Cloudhub, and apply a policy.
+
+// An API running on Anypoint Runtime Fabric
+
+// Design an API on Anypoint Platform, configure a proxy for Runtime Fabric, and apply a policy.
+
+// An API deployed to a private or cloud-based Mule runtime engine (Mule) 3.8.x or later
+
+// You can apply a policy to any API implemented in Anypoint Platform, as long as the API is exposed through an HTTP listener. You can also apply a policy to APIs not implemented in Anypoint Platform by deploying a proxy application to control how and when a received request is forwarded to its implementation endpoint. Anypoint API Manager supports RAML, HTTP, or SOAP-based proxies.
+
+// When applying a policy with SLA, you can set an API alert to notify you when an API request violates that policy. By default, a policy applies to the entire API, filtering traffic requests to every resource and method. You can configure this to provide resource-level granularity if needed.