chore: fix broken links by adding inline filters (#7356)

* chore: fix broken links by adding inline filters * chore: remove the line instead of use InlineFilter since flutter is the only platform with this page * chore: remove getting started link under storage subheading that was being used as a placeholder
aws-amplify · May 4, 2024 · 6b05e17 · 6b05e17
1 parent f6dc40c
commit 6b05e17
Show file tree

Hide file tree

Showing 5 changed files with 17 additions and 8 deletions.
diff --git a/src/constants/feature-lists-data.ts b/src/constants/feature-lists-data.ts
@@ -266,12 +266,6 @@ const featureListData = {
               'Upload and download files to and from cloud storage with advanced controls like pausing and resuming upload operations.',
             linkText: 'Upload and Download files',
             link: 'build-a-backend/storage/upload/'
-          },
-          {
-            content:
-              'Manage content through APIs for listing, accessing, and manipulating files. Set file permission levels, configure automatic events and triggers, and more.',
-            linkText: 'Advanced file operations and access control',
-            link: 'build-a-backend/storage/configure-access/'
           }
         ],
         heading: 'Storage'

diff --git a/src/fragments/lib-v1/graphqlapi/native_common/getting-started/common.mdx b/src/fragments/lib-v1/graphqlapi/native_common/getting-started/common.mdx
@@ -137,6 +137,8 @@ Congratulations! You've created a `Todo` object in your database. Check out the
 - [Update data](/gen1/[platform]/prev/build-a-backend/graphqlapi/mutate-data/)
 - [Subscribe to data](/gen1/[platform]/prev/build-a-backend/graphqlapi/subscribe-data/)
 - [Concepts](/gen1/[platform]/prev/build-a-backend/graphqlapi/api-graphql-concepts/)
+<InlineFilter filters={['ios', 'android']}>
 - [Configure authorization modes](/gen1/[platform]/prev/build-a-backend/graphqlapi/customize-authz-modes)
+</InlineFilter>
 
 {/* TODO: * [Authorizing API calls with Cognito User Pool] */}
diff --git a/src/fragments/lib/graphqlapi/native_common/getting-started/common.mdx b/src/fragments/lib/graphqlapi/native_common/getting-started/common.mdx
@@ -141,6 +141,8 @@ Congratulations! You've created a `Todo` object in your database. Check out the
 - [Update data](/gen1/[platform]/build-a-backend/graphqlapi/mutate-data/)
 - [Subscribe to data](/gen1/[platform]/build-a-backend/graphqlapi/subscribe-data/)
 - [Concepts](/gen1/[platform]/build-a-backend/graphqlapi/api-graphql-concepts/)
+<InlineFilter filters={['ios', 'android']}>
 - [Configure authorization modes](/gen1/[platform]/build-a-backend/graphqlapi/customize-authorization-rules)
+</InlineFilter>
 
 {/* TODO: * [Authorizing API calls with Cognito User Pool] */}
diff --git a/src/pages/[platform]/prev/build-a-backend/storage/import/index.mdx b/src/pages/[platform]/prev/build-a-backend/storage/import/index.mdx
@@ -67,8 +67,6 @@ By default, Amplify Libraries assumes that S3 buckets are configured with the fo
 - `protected/{user_identity_id}/` - Readable by all users, but writable only by the creating user
 - `private/{user_identity_id}/` - Only accessible for the individual user
 
-You can either configure your IAM role to use the Amplify-recommended policies or in your Amplify libraries configuration [overwrite the default storage path behavior](/[platform]/build-a-backend/storage/configure-access/#customize-object-key-path).
-
 It is highly recommended to review your S3 bucket's CORS settings. Review the [recommendation guide here](/[platform]/build-a-backend/storage/set-up-storage/#amazon-s3-bucket-cors-policy-setup).
 
 ### Configuring IAM role to use Amplify-recommended policies

diff --git a/src/pages/gen1/[platform]/build-a-backend/storage/import/index.mdx b/src/pages/gen1/[platform]/build-a-backend/storage/import/index.mdx
@@ -67,8 +67,21 @@ By default, Amplify Libraries assumes that S3 buckets are configured with the fo
 - `protected/{user_identity_id}/` - Readable by all users, but writable only by the creating user
 - `private/{user_identity_id}/` - Only accessible for the individual user
 
+<InlineFilter filters={[
+    'android',
+    'angular',
+    'javascript',
+    'nextjs',
+    'react',
+    'react-native',
+    'swift',
+    'vue'
+]}>
+
 You can either configure your IAM role to use the Amplify-recommended policies or in your Amplify libraries configuration [overwrite the default storage path behavior](/gen1/[platform]/build-a-backend/storage/configure-access/#customize-object-key-path).
 
+</InlineFilter>
+
 It is highly recommended to review your S3 bucket's CORS settings. Review the [recommendation guide here](/gen1/[platform]/build-a-backend/storage/set-up-storage/#amazon-s3-bucket-cors-policy-setup).
 
 ### Configuring IAM role to use Amplify-recommended policies