-
-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revise and improve branding, readability and SEO for integration pages. #1352
Comments
Hey @pavlenex Odoo doesn't exist on the documentation page. Don't know if it is still a valid integration |
It's still a work in progress, I'd expect @ndeet to work on completing it after BTCPrague. |
@TChukwuleta there was a typo, it is Shopware https://docs.btcpayserver.org/Shopware/#plugin-for-shopware-6 We are not on their marketplace anymore because they want thousands of EUR just to be listed there even if you are open source it seems |
Context:
Often, new users discover BTCPay Server by finding a way to accept bitcoin in their e-commerce software (CMS). This is usually done by Googling "Accept bitcoin/crypto in XYZ".
It seems with a bit of cleanups and improvements, that allows for better experience overal, we can boost discoverability of those pages.
When a user lands on a page Shopify, by googling How to accept Bitcoin in Shopify for example ,they're expecting to get context, understand the features/advantages and how to get started as quickly as possible.
This issue is a tracker for multiple smaller issues that we can tackle, by striving to improve our integrations landing pages. In most cases the readme of the integration repo has to be addressed since we pull docs from them. Please reach out before tackling any of this issues for consensus and approach alignment.
Good example on how a page should look is our newly updated WooCommerce plugin.
Ideal description of an integration should have:
6.Have clear instructions on how to connect integration to BTCPay Server
Sorted in order of priority, each of these should be tackled:
Tasks
The text was updated successfully, but these errors were encountered: