Skip to content

Commit 8c07307

Browse files
alexphelpsalexphelps
committed
fix tabbed content headings
1 parent 3fb6948 commit 8c07307

18 files changed

Lines changed: 281 additions & 253 deletions

File tree

‎README.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
# 29 Next Developer Docs
2+
3+
Developer documentation for the 29 Next platform, built with [Fumadocs](https://fumadocs.vercel.app) and [Next.js](https://nextjs.org).
4+
5+
## Stack
6+
7+
- **[Fumadocs](https://fumadocs.vercel.app)** — docs framework (UI, MDX processing, OpenAPI rendering)
8+
- **[Next.js](https://nextjs.org)** — framework
9+
- **[Algolia DocSearch](https://docsearch.algolia.com)** — site search, indexed via GitHub Actions on push to `main`
10+
11+
## Development
12+
13+
Install dependencies:
14+
15+
```bash
16+
npm install
17+
```
18+
19+
Run the dev server (also generates API reference docs from OpenAPI specs):
20+
21+
```bash
22+
npm run dev
23+
```
24+
25+
## Validate Links
26+
27+
Check for broken internal links:
28+
29+
```bash
30+
node scripts/validate-links.mjs
31+
```
32+
33+
## Search Index
34+
35+
The Algolia search index is updated automatically via the `Build Search Index` GitHub Actions workflow on every push to `main`. It uses the `algolia.json` config and requires `ALGOLIA_APPLICATION_ID` and `ALGOLIA_API_KEY` secrets.
36+
37+
## Build
38+
39+
```bash
40+
npm run build
41+
```

‎app/globals.css‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,14 @@
7474
padding-bottom: 0.5rem !important;
7575
}
7676

77+
/* Cards: strip fumadocs' own icon wrapper so custom colorized icon divs show cleanly */
78+
[data-card] > .not-prose {
79+
background: transparent !important;
80+
border: none !important;
81+
padding: 0 !important;
82+
box-shadow: none !important;
83+
}
84+
7785
/* Remove max-height on code blocks inside API example/request panels so content doesn't scroll */
7886
[data-api-requests] .fd-scroll-container {
7987
max-height: none !important;

‎content/docs/admin-api/guides/external-checkout.mdx‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ tags:
66
- Guide
77
---
88
import { Callout } from 'fumadocs-ui/components/callout';
9-
import Tabs from '@theme/Tabs';
10-
import TabItem from '@theme/TabItem';
119

1210
In this guide we'll cover the best practices when building an external checkout flow using the Next Commerce Admin API. Using the API gives you the most flexibility of data and functionality across the platform and external integrations.
1311

‎content/docs/apps/guides/dispute-service.mdx‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,7 @@ tags:
55
- Guide
66
---
77
import { Callout } from 'fumadocs-ui/components/callout';
8-
import Tabs from '@theme/Tabs';
9-
import TabItem from '@theme/TabItem';
8+
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
109

1110
Dispute service apps are integrations that manage the processing of payment disputes (alerts and chargebacks) on behalf of merchants seamlessly within the platform.
1211

@@ -141,8 +140,8 @@ It's desirable to cancel fulfillment for orders that have not shipped yet when t
141140
<Callout type="info">
142141
To retrieve a list of all fulfillment orders and their status, use the [ordersFulfillmentOrdersRetrieve](/docs/admin-api/reference/orders/ordersFulfillmentOrdersRetrieve) endpoint.
143142
</Callout>
144-
<Tabs>
145-
<TabItem value="fulfillment_status-unfulfilled" label="Fulfillment Status - Unfulfilled">
143+
<Tabs items={['Fulfillment Status - Unfulfilled', 'Fulifllment Status - Processing']}>
144+
<Tab value="Fulfillment Status - Unfulfilled">
146145

147146
If order `fulfilmlent_status` is `unfulfilled`, your dispute service can stop fulfillment using the [fulfillmentOrdersHold](/docs/admin-api/reference/fulfillment/fulfillmentOrdersHold) endpoint.
148147

@@ -156,8 +155,8 @@ If order `fulfilmlent_status` is `unfulfilled`, your dispute service can stop fu
156155
}
157156
```
158157

159-
</TabItem>
160-
<TabItem value="fulfillment_status-processing" label="Fulifllment Status - Processing">
158+
</Tab>
159+
<Tab value="Fulifllment Status - Processing">
161160

162161
If order `fulfilmlent_status` is `processing` your dispute service can request processing fulfillment orders be canceled with the fulfillment locations with the [cancellationRequestSend](/docs/admin-api/reference/fulfillment/cancellationRequestSend) endpoint.
163162

@@ -171,7 +170,7 @@ If order `fulfilmlent_status` is `processing` your dispute service can request p
171170
<Callout type="warn">
172171
Fulfillment locations need to accept the cancelation request to confirm they were able to stop fulfillment on their end at. It is possible that the fulfillment order was already shipped and the fulfillment could not be stopped.
173172
</Callout>
174-
</TabItem>
173+
</Tab>
175174
</Tabs>
176175

177176
### RDR Alerts

‎content/docs/apps/guides/fulfillment-service.mdx‎

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,8 @@ tags:
55
- Guide
66
---
77
import { Callout } from 'fumadocs-ui/components/callout';
8-
9-
import Tabs from '@theme/Tabs';
10-
import TabItem from '@theme/TabItem';
118
import Link from 'next/link';
9+
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
1210

1311
Fulfillment service apps are integrations that manage fulfillment of physical products for merchants by enabling transparent communication between fulfillment providers and merchants using the Next Commerce dashboard.
1412

@@ -91,24 +89,24 @@ Fulfullment Requests are sent to the location `callback` + `/fulfillment-order-n
9189
- `fulfillment_requested` - when a new fulfillment order has been requested to be fulfilled.
9290
- `cancellation_requested`- when an already processing fulfillment order has been requested to cancel fulfillment.
9391

94-
<Tabs>
95-
<TabItem value="fulfillment_requested" label="Fulfillment Request">
92+
<Tabs items={['Fulfillment Request', 'Cancellation Request']}>
93+
<Tab value="Fulfillment Request">
9694

9795
```json title="Example Fulfillment Request Payload"
9896
{
9997
"type": "fulfillment_requested"
10098
}
10199
```
102-
</TabItem>
103-
<TabItem value="cancellation_requested" label="Cancellation Request">
100+
</Tab>
101+
<Tab value="Cancellation Request">
104102

105103
```json title="Example Cancellation Request Payload"
106104
{
107105
"type": "cancellation_requested"
108106
}
109107
```
110108

111-
</TabItem>
109+
</Tab>
112110

113111
</Tabs>
114112

@@ -121,24 +119,24 @@ The [Assigned Fulfillment Orders](/docs/admin-api/reference/fulfillment/assigned
121119
<Callout type="info">
122120
Use the appropriate `assignment_status` parameter to filter the fulfillment orders to those that require action.
123121
</Callout>
124-
<Tabs>
125-
<TabItem value="fulfillment_requested" label="Fulfillment Requests">
122+
<Tabs items={['Fulfillment Requests', 'Cancellation Requests']}>
123+
<Tab value="Fulfillment Requests">
126124

127125
Retrieve all pending Fulfillment Requests
128126

129127
```json
130128
GET https://{store}.29next.store/docs/admin-api/assigned-fulfillment-orders/?assignment_status=fulfillment_requested
131129
```
132-
</TabItem>
133-
<TabItem value="cancellation_requested" label="Cancellation Requests">
130+
</Tab>
131+
<Tab value="Cancellation Requests">
134132

135133
Retrieve all pending Cancellation Requests
136134

137135
```json
138136
GET https://{store}.29next.store/docs/admin-api/assigned-fulfillment-orders/?assignment_status=cancellation_requested
139137
```
140138

141-
</TabItem>
139+
</Tab>
142140

143141
</Tabs>
144142

0 commit comments

Comments
 (0)