Skip to content
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

Blog: How to write compound promises in Kratix #125

Open
3 tasks
catmo-syntasso opened this issue Oct 7, 2024 · 2 comments
Open
3 tasks

Blog: How to write compound promises in Kratix #125

catmo-syntasso opened this issue Oct 7, 2024 · 2 comments

Comments

@catmo-syntasso
Copy link
Member

catmo-syntasso commented Oct 7, 2024

Our docs contain all the information and possibilities on writing a compound promise.
We want a place we can point customers who are looking at building compound promises - like a step-by-step guide for how to write a compound promise, using promise releases, based on (probably) the app as a service promise You can write it up and get feedback in our notion board if that's easier before publishing.

two paths to compound promises

Tip

Consider using the GACC framework and get feedback before starting the write up

Done When

  • Blog written explaining the step-by-step of writing a basic compound promise
  • Reviewed by @kirederik or @cghsystems (and CA engineers if unavailable)
  • Blog published to docs.kratix.io/blogs
@kirederik
Copy link
Member

any reason for this to be a blog and not a better guide? we have this today btw

@catmo-syntasso
Copy link
Member Author

  1. Boost the amount of content on the blog
  2. Blogs are where we post helpful "point in time" content - given promise releases are something we'd like to improve in the mid-term, a blog means we don't have to go back through all the places we mention them to fix it.
  3. Customer expectation (they've asked for an encapsulated blog on a use case rather than a part of guide or tutorial)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants