|
1 |
| -# API Docs for Apigee Edge |
| 1 | +# Apigee API Catalog for Drupal |
2 | 2 |
|
3 |
| -A module to render OpenAPI specs as documentation to your API developers. |
| 3 | +Render OpenAPI specs as documentation to your API developers. |
4 | 4 |
|
5 | 5 | ## Overview
|
6 | 6 |
|
7 | 7 | When you enable this module, it creates a new Drupal entity in your system named
|
8 |
| -"API Doc". You can add new API Docs under Structure > API Docs in the admin menu. |
| 8 | +"API Doc". You can add new API docs under __Configuration > API catalog__ in the admin menu. |
9 | 9 |
|
10 | 10 | Once added, the API name and description for each API Doc will be displayed in the
|
11 |
| -"APIs" menu item on the site to all visitors. |
| 11 | +"APIs" menu item on the site using a Drupal view. Make sure to change the |
| 12 | +"View published API docs" permissions if you want to allow registered or anonymous users |
| 13 | +to be able to view published API documentation. |
12 | 14 |
|
13 | 15 | The OpenAPI spec by default is shown on the API Doc detail page by default.
|
14 | 16 | To render the OpenAPI spec using Swagger UI:
|
15 | 17 |
|
16 | 18 | 1. Install an enable the [Swagger UI Field Formatter](https://www.drupal.org/project/swagger_ui_formatter) module.
|
17 | 19 | 2. Install the Swagger UI JS library as documented [on the module page](https://www.drupal.org/project/swagger_ui_formatter).
|
18 |
| -3. Go to Structure > API Doc settings > Manage display in the admin menu. |
| 20 | +3. Go to __Configuration > API catalog > Manage display__ in the admin menu. |
19 | 21 | 4. Change "OpenAPI specification" field format to use the Swagger UI field formatter.
|
20 | 22 |
|
21 |
| -The API Doc is an entity, you can configure it at Structure > API Doc settings in the admin |
| 23 | +The API Doc is an entity, you can configure it at __Configuration > API catalog__ in the admin |
22 | 24 | menu.
|
23 | 25 |
|
24 |
| -The "APIs" menu link is a view, you can modify it by editing the "API Documentation" view |
| 26 | +The "APIs" menu link is a view, you can modify it by editing the "API Catalog" view |
25 | 27 | under Structure > Views in the admin menu.
|
26 | 28 |
|
27 | 29 | ## Planned Features
|
28 | 30 |
|
29 | 31 | - Create additional field formatters to use for rendering OpenAPI specs
|
30 | 32 | - Integration with Apigee API Products
|
31 |
| -- Allow OpenAPI specs to be associated to a source location such as Apigee Edge or |
32 |
| - a URL |
| 33 | +- Allow OpenAPI specs to be associated to a source location such as Apigee Edge or a URL |
33 | 34 | - Add visual notifications when source URL specs have changed on the API Doc admin screen
|
34 | 35 | - Ability to update API Docs when source location changes
|
35 | 36 |
|
36 | 37 | ### Known issues
|
37 | 38 |
|
38 | 39 | - none
|
| 40 | + |
| 41 | +## Installing |
| 42 | + |
| 43 | +This module must be installed on a Drupal site that is managed by Composer. Drupal.org has documentation on how to |
| 44 | +[use Composer to manage Drupal site dependencies](https://www.drupal.org/docs/develop/using-composer/using-composer-to-manage-drupal-site-dependencies) |
| 45 | +to get you started quickly. |
| 46 | + |
| 47 | +1. Install the module using [Composer](https://getcomposer.org/). |
| 48 | + Composer will download the this module and all its dependencies. |
| 49 | + **Note**: Composer must be executed at the root of your Drupal installation. |
| 50 | + For example: |
| 51 | + ``` |
| 52 | + cd /path/to/drupal/root |
| 53 | + composer require drupal/apigee_api_catalog |
| 54 | + ``` |
| 55 | + For more information about installing contributed modules using Composer, read |
| 56 | + [how to download contributed modules and themes using Composer](https://www.drupal.org/docs/develop/using-composer/using-composer-to-manage-drupal-site-dependencies#managing-contributed). |
| 57 | +2. Choose **Extend** in the Drupal administration menu. |
| 58 | +3. Select the **Apigee API catalog** module. |
| 59 | +4. Choose **Install**. |
| 60 | + |
| 61 | +## Development |
| 62 | + |
| 63 | +Development is happening in our [GitHub repository](https://github.com/apigee/apigee-api-catalog-drupal). The Drupal.org issue |
| 64 | +queue is disabled; we use the [Github issue queue](https://github.com/apigee/apigee-api-catalog-drupal) to coordinate |
| 65 | +development. See [CONTRIBUTING.md] for more information on contributing through development. |
| 66 | + |
| 67 | +## Disclaimer |
| 68 | + |
| 69 | +This is not an officially supported Google product. |
0 commit comments