Skip to content

Commit 18e89ec

Browse files
committed
Revise Catalog alt text
1 parent 7eda702 commit 18e89ec

5 files changed

Lines changed: 15 additions & 15 deletions

File tree

content/en/docs/catalog/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ aliases:
1818

1919
The [Catalog](https://catalog.mendix.com) is a development tool provided in Mendix Cloud.
2020

21-
{{< figure src="/attachments/catalog/catalog-home.png" class="no-border" >}}
21+
{{< figure src="/attachments/catalog/catalog-home.png" alt="Catalog home page" class="no-border" >}}
2222

2323
REST services provided by Mendix Apps running in Mendix Cloud (published [OData](/refguide/published-odata-services/) and OpenAPI REST Services), Web Services, and Business Events are automatically registered in your organization's Catalog upon deployment. This provides you with an up-to-date view of all the OData, OpenAPI, Web Service and Business Event endpoints published and consumed by your Mendix apps. These assets can be [curated](/catalog/manage/curate/) in the Catalog to ensure that they are exposed to the relevant users and can be found easily.
2424

content/en/docs/catalog/manage/curate.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Information that is added or changed during curation is stored in the Catalog fo
2727

2828
Owners and curators of registered assets can click **Curate** from the Catalog home page to see the curation list screen. This page provides an overview of all the registered assets you can curate as an owner under the **My Assets** tab. Curators will also see the **Company Assets** tab that lists all the registered assets.
2929

30-
{{< figure src="/attachments/catalog/curate/curate-list.png" alt="curate list" class="no-border" >}}
30+
{{< figure src="/attachments/catalog/curate/curate-list.png" alt="List of company assets with filters settings" class="no-border" >}}
3131

3232
These lists include registered service and also individual datasets that are exposed for the service.
3333

@@ -124,7 +124,7 @@ To **Upload a different icon** for the app, follow these steps:
124124

125125
1. In the **Application** tab of the selected service, click **Upload a different icon** to display the **Upload Application Icon** pop-up window.
126126

127-
{{< figure src="/attachments/catalog/curate/icon-upload-dialog.png" alt="upload icon" width="300" class="no-border" >}}
127+
{{< figure src="/attachments/catalog/curate/icon-upload-dialog.png" alt="Upload icon dialog box" width="300" class="no-border" >}}
128128

129129
2. Drag the image file into the upload area or click **Upload** to browse and select a file from your file system. Click **Step 2: Crop image** to proceed.
130130
3. Move the wire-frame to select an area of the loaded image and change the size of the wire-frame to crop the image to the area that you want to use. When you are satisfied, click **Apply Changes**.
@@ -133,11 +133,11 @@ To **Upload a different icon** for the app, follow these steps:
133133

134134
4. A preview of the application icon is shown. Click **Save** to upload the selected icon.
135135

136-
{{< figure src="/attachments/catalog/curate/icon-preview.png" alt="upload icon" width="300" class="no-border" >}}
136+
{{< figure src="/attachments/catalog/curate/icon-preview.png" alt="Preview of sample application icon" width="300" class="no-border" >}}
137137

138138
5. The **Application** tab now displays the selected icon.
139139

140-
{{< figure src="/attachments/catalog/curate/asset-metadata-new-icon.png" alt="upload icon" class="no-border" >}}
140+
{{< figure src="/attachments/catalog/curate/asset-metadata-new-icon.png" alt="" class="no-border" >}}
141141

142142
6. Click **Save** to return to the Service details page. The custom icon will be stored in the **Icon Library**.
143143

@@ -158,7 +158,7 @@ If a description was included in the contract, it will be displayed in the Servi
158158
To edit the asset metadata, follow these steps:
159159

160160
1. On the **Curate** page, click **Edit** to display the Edit Service screen.
161-
{{< figure src="/attachments/catalog/curate/service-metadata-box.png" alt="service metadata" class="no-border" >}}
161+
{{< figure src="/attachments/catalog/curate/service-metadata-box.png" alt="Data source description box" class="no-border" >}}
162162

163163
2. The description from the service metadata is displayed in the **Description provided by the contract**. This cannot be changed, as it is part of the service definition. You can provide an alternative description in the **Description** box.
164164

@@ -172,7 +172,7 @@ Add tags to categorize a registered service and provide additional means for fin
172172
1. On the Service details page of a selected service, click **Edit** to display the Edit Service screen.
173173
2. To add tags, click the empty **Tags** input area.
174174

175-
{{< figure src="/attachments/catalog/curate/service-metadata-tags.png" alt="tags" class="no-border" >}}
175+
{{< figure src="/attachments/catalog/curate/service-metadata-tags.png" alt="List of tag suggestions" class="no-border" >}}
176176

177177
3. To add or edit the tags, enter a tag string and press <kbd>Enter</kbd> or select one from the list of existing tags that are used in the Catalog. To separate multiple tags, use spaces.
178178

content/en/docs/catalog/manage/landscape.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Services are depicted as a round node with the icon that indicates the **Technol
6262

6363
Apps are displayed as square icons with the application icon and the environment that the app is deployed to is given below the app name. The example below shows a non-Mendix app (**TeamcenterMfg**), a Mendix app (**CompanyCarDemo**) which are deployed to the Mendix Free App environment, **Sandbox**. The third example shows another Mendix app (**HRSample_App**) deployed to the production environment which has a custom icon. For further information on adding a custom icon to your app see [Changing the Application Icon](/catalog/manage/curate/#application-icon).
6464

65-
{{< figure src="/attachments/catalog/landscape/node-apps.png" alt="different app logos" class="no-border" >}}
65+
{{< figure src="/attachments/catalog/landscape/node-apps.png" alt="Three different company icons" class="no-border" >}}
6666

6767
### Dependencies
6868

content/en/docs/catalog/manage/search.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The **Search** screen is divided into the [search](#search-pane) pane on the lef
7272

7373
The collapsible **Search** pane is used to search for registered assets in the Catalog.
7474

75-
{{< figure src="/attachments/catalog/search/search-pane.png" alt="search pane" width="300" class="no-border" >}}
75+
{{< figure src="/attachments/catalog/search/search-pane.png" alt="Studio Pro search pane" width="300" class="no-border" >}}
7676

7777
#### Specifying the Search
7878

@@ -139,7 +139,7 @@ When a **Dataset** is selected in the search results, the following details are
139139

140140
The source and endpoint details of the dataset are displayed:
141141

142-
{{< figure src="/attachments/catalog/search/dataset-details.png" alt="associations info" >}}
142+
{{< figure src="/attachments/catalog/search/dataset-details.png" alt="Sample dataset with example attributes" >}}
143143

144144
* Dataset name
145145
* **Part of** – a link to the service details page that the dataset is exposed in
@@ -160,7 +160,7 @@ The **Attributes** tab lists the attributes that are exposed for the dataset in
160160

161161
Under the **Associations** tab for each dataset, the associations are displayed:
162162

163-
{{< figure src="/attachments/catalog/search/attributes-associations.png" alt="associations info" class="no-border" >}}
163+
{{< figure src="/attachments/catalog/search/attributes-associations.png" alt="Sample dataset with example association" class="no-border" >}}
164164

165165
* **Name** – the name of the association that is exposed in the OData service contract.
166166
* **Navigates to** – the dataset the association is made with. Click the link to see the details of the associated dataset in the Catalog.
@@ -170,7 +170,7 @@ Under the **Associations** tab for each dataset, the associations are displayed:
170170

171171
The metadata panel at the right of the asset details screen displays details from the service metadata contract and values that have been curated in the Catalog:
172172

173-
{{< figure src="/attachments/catalog/search/metadata.png" alt="metadata pane" width="300" class="no-border" >}}
173+
{{< figure src="/attachments/catalog/search/metadata.png" alt="Sample Catalog metadata pane" width="300" class="no-border" >}}
174174

175175
#### Tags
176176

@@ -219,7 +219,7 @@ The environment type indicates the quality and the status of the data that the e
219219

220220
The **Curation Option** is displayed in the asset detail screen if you are the owner of the selected asset or a curator. In **Edit**, you can edit the information that is displayed in the Catalog for an asset.
221221

222-
{{< figure src="/attachments/catalog/search/curation-option.png" alt="curation option" width="300" >}}
222+
{{< figure src="/attachments/catalog/search/curation-option.png" alt="Sample app curation option" width="300" >}}
223223

224224
For the selected service, you can edit the [Application Details](/catalog/manage/curate/#curate-application), the [Service Details](/catalog/manage/curate/#service-details), and the Authentication.
225225

@@ -237,7 +237,7 @@ The resulting ZIP file is named `DataHub_<service_name>_<service_version>_<techn
237237

238238
Here is an example:
239239

240-
{{< figure src="/attachments/catalog/search/download_example.png" alt="download example" class="no-border" >}}
240+
{{< figure src="/attachments/catalog/search/download_example.png" alt="Sample app download location" class="no-border" >}}
241241

242242
When you click **Download**, the following file is downloaded: `DataHub_SAP_Intelligence_1.0_OData4.zip`. This ZIP file has the folder `DataHub_SAP_Intelligence_1.0_OData4`, which contains all the metadata files that define the service.
243243

content/en/docs/catalog/register/register-non-odata-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ There are certain limitations on consumed OData services. For more information o
2929

3030
The diagram below represents how an OData API wrapper can be used to connect a custom app service to a Mendix Studio Pro app:
3131

32-
{{< figure src="/attachments/catalog/register-non-odata-resources/non-odata.png" alt="Catalog connecting to non-OData resources" class="no-border" >}}
32+
{{< figure src="/attachments/catalog/register-non-odata-resources/non-odata.png" alt="Diagram of Catalog resources connecting to non-OData resources" class="no-border" >}}
3333

3434
Once the OData service is available, find the generated *$metadata* file for your data, and use that to register your service in the Catalog via the connector on the home page. For more information on setting up the connection, see [Published OData Services](/refguide/published-odata-services/).
3535

0 commit comments

Comments
 (0)