|
1 | | -# Adobe I/O Documentation Template |
| 1 | +# Adobe Developer Console Documentation |
2 | 2 |
|
3 | | -This is a site template built with the [Adobe I/O Theme](https://github.com/adobe/aio-theme). |
| 3 | +Adobe Developer Console documentation site deployed to EDS. |
| 4 | +The production address is https://developer.adobe.com/developer-console/docs/ |
4 | 5 |
|
5 | | -View the [demo](https://adobedocs.github.io/dev-site-documentation-template/) running on Github Pages. |
| 6 | +## Quick Start |
6 | 7 |
|
7 | | -## Where to ask for help |
| 8 | +For local development, you need to start three servers: |
8 | 9 |
|
9 | | -The slack channel #adobeio-onsite-onboarding is our main point of contact for help. Feel free to join the channel and ask any questions. |
10 | | - |
11 | | -## How to develop |
| 10 | +1. **Main dev server** (this repo): |
| 11 | +```bash |
| 12 | +npm run dev |
| 13 | +``` |
12 | 14 |
|
13 | | -For local development, simply use : |
| 15 | +2. **ADP Devsite** ([adp-devsite](https://github.com/AdobeDocs/adp-devsite)): |
| 16 | +```bash |
| 17 | +git clone https://github.com/AdobeDocs/adp-devsite |
| 18 | +cd adp-devsite |
| 19 | +npm install |
| 20 | +npm run dev |
14 | 21 | ``` |
15 | | -$ npm install |
16 | | -$ npm run dev |
| 22 | + |
| 23 | +3. **Runtime connector** ([devsite-runtime-connector](https://github.com/aemsites/devsite-runtime-connector)): |
| 24 | +```bash |
| 25 | +git clone https://github.com/aemsites/devsite-runtime-connector |
| 26 | +cd devsite-runtime-connector |
| 27 | +npm install |
| 28 | +npm run dev |
17 | 29 | ``` |
18 | 30 |
|
19 | | -For the documentation developer, please read these sections on how to: |
20 | | -- [Arrange the structure content of your docs](https://github.com/adobe/aio-theme#content-structure) |
21 | | -- [Linking to pages](https://github.com/adobe/aio-theme#links) |
22 | | -- [Using assets](https://github.com/adobe/aio-theme-aio#assets) |
23 | | -- [Setting Global Navigation](https://github.com/adobe/aio-theme#global-navigation) |
24 | | -- [Setting Side Navigation](https://github.com/adobe/aio-theme#side-navigation) |
25 | | -- [Using content blocks](https://github.com/adobe/aio-theme#jsx-blocks) |
26 | | -- [Notes on using Markdown](https://github.com/adobe/aio-theme#writing-enhanced-markdown) |
| 31 | +Once all three servers are running, navigate to http://localhost:3000 |
27 | 32 |
|
28 | | -For more in-depth [instructions](https://github.com/adobe/aio-theme#getting-started). |
| 33 | +## Commands |
29 | 34 |
|
30 | | -## How to deploy |
| 35 | +**Development** |
| 36 | +- `npm run dev` - Start local server (requires other services above) |
31 | 37 |
|
32 | | -For any team that wishes to deploy to the adobe.io and stage.adobe.io website, they must be in contact with the dev-site team. Teams will be given a path that will follow the pattern `adobe.io/{product}/`. This will allow doc developers to setup their subpaths to look something like: |
33 | | -``` |
34 | | -adobe.io/{product}/docs |
35 | | -adobe.io/{product}/community |
36 | | -adobe.io/{product}/community/code_of_conduct |
37 | | -adobe.io/{product}/community/contribute |
38 | | -``` |
| 38 | +**Content Management** |
| 39 | +- `npm run buildNavigation` - Generate navigation structure (one-time Gatsby migration only) |
| 40 | +- `npm run buildRedirections` - Build URL redirections (one-time Gatsby migration only) |
| 41 | +- `npm run renameFiles` - Rename files to Adobe conventions |
| 42 | +- `npm run normalizeLinks` - Normalize internal/external links |
| 43 | + |
| 44 | +**Validation** |
| 45 | +- `npm run lint` - Run linting checks |
| 46 | + |
| 47 | +**Site Features** |
| 48 | +- `npm run buildSiteWideBanner` - Generate site-wide banner |
| 49 | + |
| 50 | +*All commands use `@AdobeDocs/adp-devsite-utils` for standardized tooling.* |
| 51 | + |
| 52 | +## Linting |
| 53 | + |
| 54 | +**Automated**: Runs on PRs when `src/pages/**` files change |
| 55 | +**Manual**: `npm run lint` |
| 56 | + |
| 57 | +Validates markdown syntax, links, content structure, and Adobe style guidelines. |
| 58 | + |
| 59 | +**Troubleshooting**: If pages are not showing up as expected, check lint warnings to identify potential issues. |
| 60 | + |
| 61 | +## Navigation |
| 62 | + |
| 63 | +To update navigation structure: |
| 64 | +1. Edit `src/pages/config.md` directly |
| 65 | + |
| 66 | +*Note: `npm run buildNavigation` is only needed for initial Gatsby migration.* |
| 67 | + |
| 68 | +## Redirects |
| 69 | + |
| 70 | +To manage URL redirections: |
| 71 | +1. Edit `src/pages/redirects.json` directly |
| 72 | + |
| 73 | +*Note: `npm run buildRedirections` is only needed for initial Gatsby migration.* |
| 74 | + |
| 75 | +## Deployment |
| 76 | + |
| 77 | +**Staging**: |
| 78 | +- Actions > Deployment > Run workflow |
| 79 | +- Can deploy from any branch to staging |
| 80 | +- Uses incremental builds from last commit by default |
| 81 | +- Use `deployAll` function for full rebuild if needed |
| 82 | +- **URL**: `developer-stage.adobe.com/developer-console/docs/` |
| 83 | + |
| 84 | +**Production**: |
| 85 | +- Automatically deploys from `main` branch |
| 86 | +- Uses incremental builds from last commit |
| 87 | +- **URL**: `developer.adobe.com/developer-console/docs/` |
39 | 88 |
|
40 | | -### Launching a deploy |
| 89 | +## Support |
41 | 90 |
|
42 | | -You can deploy using the GitHub actions deploy workflow see [deploy instructions](https://github.com/adobe/aio-theme#deploy-to-azure-storage-static-websites). |
| 91 | +Join `#adobe-developer-website` Slack channel for help. |
0 commit comments