mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-22 00:25:50 -05:00
15.md:use relative links
This commit is contained in:
parent
18d3c2edb4
commit
b8fe261ce4
14
15.md
14
15.md
|
@ -6,7 +6,7 @@ Nostr Marketplace
|
|||
|
||||
`draft` `optional`
|
||||
|
||||
Based on https://github.com/lnbits/Diagon-Alley.
|
||||
Based on [Diagon-Alley](https://github.com/lnbits/Diagon-Alley).
|
||||
|
||||
Implemented in [NostrMarket](https://github.com/lnbits/nostrmarket) and [Plebeian Market](https://github.com/PlebeianTech/plebeian-market).
|
||||
|
||||
|
@ -139,7 +139,7 @@ Fields that are not self-explanatory:
|
|||
|
||||
## Checkout events
|
||||
|
||||
All checkout events are sent as JSON strings using ([NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md)).
|
||||
All checkout events are sent as JSON strings using [NIP-04](04.md).
|
||||
|
||||
The `merchant` and the `customer` can exchange JSON messages that represent different actions. Each `JSON` message `MUST` have a `type` field indicating the what the JSON represents. Possible types:
|
||||
|
||||
|
@ -150,7 +150,7 @@ The `merchant` and the `customer` can exchange JSON messages that represent diff
|
|||
| 2 | Merchant | Order Status Update |
|
||||
|
||||
### Step 1: `customer` order (event)
|
||||
The below JSON goes in content of [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md).
|
||||
The below JSON goes in content of [NIP-04](04.md).
|
||||
|
||||
```json
|
||||
{
|
||||
|
@ -182,7 +182,7 @@ _Open_: is `contact.nostr` required?
|
|||
|
||||
Sent back from the merchant for payment. Any payment option is valid that the merchant can check.
|
||||
|
||||
The below JSON goes in `content` of [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md).
|
||||
The below JSON goes in `content` of [NIP-04](04.md).
|
||||
|
||||
`payment_options`/`type` include:
|
||||
|
||||
|
@ -217,7 +217,7 @@ The below JSON goes in `content` of [NIP-04](https://github.com/nostr-protocol/n
|
|||
|
||||
Once payment has been received and processed.
|
||||
|
||||
The below JSON goes in `content` of [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md).
|
||||
The below JSON goes in `content` of [NIP-04](04.md).
|
||||
|
||||
```json
|
||||
{
|
||||
|
@ -231,7 +231,7 @@ The below JSON goes in `content` of [NIP-04](https://github.com/nostr-protocol/n
|
|||
|
||||
## Customize Marketplace
|
||||
|
||||
Create a customized user experience using the `naddr` from [NIP-19](https://github.com/nostr-protocol/nips/blob/master/19.md#shareable-identifiers-with-extra-metadata). The use of `naddr` enables easy sharing of marketplace events while incorporating a rich set of metadata. This metadata can include relays, merchant profiles, and more. Subsequently, it allows merchants to be grouped into a market, empowering the market creator to configure the marketplace's user interface and user experience, and share that marketplace. This customization can encompass elements such as market name, description, logo, banner, themes, and even color schemes, offering a tailored and unique marketplace experience.
|
||||
Create a customized user experience using the `naddr` from [NIP-19](19.md#shareable-identifiers-with-extra-metadata). The use of `naddr` enables easy sharing of marketplace events while incorporating a rich set of metadata. This metadata can include relays, merchant profiles, and more. Subsequently, it allows merchants to be grouped into a market, empowering the market creator to configure the marketplace's user interface and user experience, and share that marketplace. This customization can encompass elements such as market name, description, logo, banner, themes, and even color schemes, offering a tailored and unique marketplace experience.
|
||||
|
||||
### Event `30019`: Create or update marketplace UI/UX
|
||||
|
||||
|
@ -331,7 +331,7 @@ Another thing that can happen is - if bids happen very close to the end date of
|
|||
|
||||
## Customer support events
|
||||
|
||||
Customer support is handled over whatever communication method was specified. If communicating via nostr, NIP-04 is used https://github.com/nostr-protocol/nips/blob/master/04.md.
|
||||
Customer support is handled over whatever communication method was specified. If communicating via nostr, [NIP-04](04.md) is used.
|
||||
|
||||
## Additional
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user