You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Top Level Platform Menu & Side Nav
-> Consistency: "Unchained Admin UI" instead of "Admin UI"
We copied the docs initially from https://www.apollographql.com/docs/
They have a "Home" part and once you select one of the productsI you see completely different side nav with the details.
Is this doable too instead of having just a link to one of the sections on the left when clicking admin ui?
Always stay blockchain-neutral and write something like: If you add a crypto currency, you can optionally configure a contract address that can be used to distinguish tokens on a blockchain. A cryptocurrency payment plugin (for ex. cryptopay) can then optionally read that information and knows which currency is actually meant.
AI help for more elegant texts:
Make sure to use ChatGPT to help you write better text:
For example "Unchained engine supports multiple authentication flows users can use to register and access it. The admin ui is designed to support most of this authentication and authorization flows with the exception of some that are better suited to a storefront instead of a control panel." is not very clear and needs further explanation. restructuring the text with chatgpt can help you get more specific for example you can write that although Unchained Engine supports a wider range of auth options like custom login handlers and that the admin ui only supports self-souvereign methods and very popular oAuth providers.
Better explain the different types of products
And also get specific about the product types, there is a lot of questions around that when I discussed this with Joel from Bob Pay, he currently builts a shop based on Unchained Engine for that company as a reference implementation of their service.
He also questioned how somebody can set prices and how the default pricing works, and it was not clear for him that a configurable product cannot have prices for example.
The text was updated successfully, but these errors were encountered:
Top Level Platform Menu & Side Nav
-> Consistency: "Unchained Admin UI" instead of "Admin UI"
We copied the docs initially from https://www.apollographql.com/docs/
They have a "Home" part and once you select one of the productsI you see completely different side nav with the details.
Is this doable too instead of having just a link to one of the sections on the left when clicking admin ui?
Ethereum neutral:
http://localhost:8000/admin-ui/currency/ -> Don't use the word "Ethereum" because Unchained could support Solana, Cardano etc.
Always stay blockchain-neutral and write something like: If you add a crypto currency, you can optionally configure a contract address that can be used to distinguish tokens on a blockchain. A cryptocurrency payment plugin (for ex. cryptopay) can then optionally read that information and knows which currency is actually meant.
AI help for more elegant texts:
Make sure to use ChatGPT to help you write better text:
For example "Unchained engine supports multiple authentication flows users can use to register and access it. The admin ui is designed to support most of this authentication and authorization flows with the exception of some that are better suited to a storefront instead of a control panel." is not very clear and needs further explanation. restructuring the text with chatgpt can help you get more specific for example you can write that although Unchained Engine supports a wider range of auth options like custom login handlers and that the admin ui only supports self-souvereign methods and very popular oAuth providers.
Better explain the different types of products
And also get specific about the product types, there is a lot of questions around that when I discussed this with Joel from Bob Pay, he currently builts a shop based on Unchained Engine for that company as a reference implementation of their service.
He also questioned how somebody can set prices and how the default pricing works, and it was not clear for him that a configurable product cannot have prices for example.
The text was updated successfully, but these errors were encountered: