mirror of https://github.com/dapr/docs.git
start workflow api skeleton
Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
This commit is contained in:
parent
bf2475d053
commit
9f84a888e9
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Workflow engines"
|
||||
linkTitle: "Workflow"
|
||||
weight: 100
|
||||
description: Expose workflows as APIs with HTTP and Dapr SDK support
|
||||
---
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
type: docs
|
||||
title: "How to: Set up a workflow"
|
||||
linkTitle: "How to: Set up workflows"
|
||||
weight: 2000
|
||||
description: Integrate, manage, and expose workflows with the built-in workflow runtime component
|
||||
---
|
||||
|
||||
<!-- Introductory paragraph
|
||||
Required. Light intro that briefly describes what the how-to will cover and any default Dapr characteristics. Link off to the appropriate concept or overview docs to provide context. -->
|
||||
|
||||
<!--
|
||||
Include a diagram or image, if possible.
|
||||
-->
|
||||
|
||||
<!--
|
||||
If applicable, link to the related quickstart in a shortcode note or alert with text like:
|
||||
If you haven't already, [try out the <topic> quickstart](link) for a quick walk-through on how to use <topic>.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Make sure the how-to includes examples for multiple programming languages, OS, or deployment targets, if applicable.
|
||||
-->
|
||||
|
||||
## <Action or task>
|
||||
|
||||
<!--
|
||||
Unlike quickstarts, do not use "Step 1", "Step 2", etc.
|
||||
-->
|
||||
|
||||
## <Action or task>
|
||||
|
||||
<!--
|
||||
Each H2 step should start with a verb/action word.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Include code snippets where possible.
|
||||
-->
|
||||
|
||||
## Next steps
|
||||
|
||||
<!--
|
||||
Link to related pages and examples. For example, the building block overview, the related tutorial, API reference, etc.
|
||||
-->
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Invoking workflows: HTTP vs gRPC"
|
||||
linkTitle: "Invoke with HTTP vs gRPC"
|
||||
weight: 3000
|
||||
description: Learn how to invoke the workflow API using either HTTP or gRPC
|
||||
---
|
||||
|
||||
<!-- Introductory paragraph
|
||||
Required. Light intro that briefly describes what the how-to will cover and any default Dapr characteristics. Link off to the appropriate concept or overview docs to provide context. -->
|
||||
|
||||
<!--
|
||||
Include a diagram or image, if possible.
|
||||
-->
|
||||
|
||||
<!--
|
||||
If applicable, link to the related quickstart in a shortcode note or alert with text like:
|
||||
If you haven't already, [try out the <topic> quickstart](link) for a quick walk-through on how to use <topic>.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Make sure the how-to includes examples for multiple programming languages, OS, or deployment targets, if applicable.
|
||||
-->
|
||||
|
||||
## <Action or task>
|
||||
|
||||
<!--
|
||||
Unlike quickstarts, do not use "Step 1", "Step 2", etc.
|
||||
-->
|
||||
|
||||
## <Action or task>
|
||||
|
||||
<!--
|
||||
Each H2 step should start with a verb/action word.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Include code snippets where possible.
|
||||
-->
|
||||
|
||||
## Next steps
|
||||
|
||||
<!--
|
||||
Link to related pages and examples. For example, the building block overview, the related tutorial, API reference, etc.
|
||||
-->
|
|
@ -0,0 +1,71 @@
|
|||
---
|
||||
type: docs
|
||||
title: Workflow overview
|
||||
linkTitle: Overview
|
||||
weight: 1000
|
||||
description: #Required; One-sentence description of what to expect in the article
|
||||
---
|
||||
|
||||
<!--
|
||||
Remove all the comments in this template before opening a PR.
|
||||
-->
|
||||
|
||||
<!--
|
||||
H1: The title in the Hugo front-matter serves as the article's markdown H1.
|
||||
-->
|
||||
|
||||
<!-- Introductory paragraph
|
||||
Required. Brief intro that describes the concepts that the article will cover. Link off to the appropriate reference, specs, or how-to guides to provide context. -->
|
||||
|
||||
<!--
|
||||
Include a diagram or image, if possible.
|
||||
-->
|
||||
|
||||
## <Section 1 H2>
|
||||
|
||||
<!--
|
||||
Add your content here.
|
||||
-->
|
||||
|
||||
## <Section 2 H2>
|
||||
|
||||
<!--
|
||||
Each H2 step should start with a noun/descriptive word.
|
||||
-->
|
||||
|
||||
## <Section 3 H2>
|
||||
|
||||
<!--
|
||||
Add your content here.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Include diagrams or images throughout, where applicable.
|
||||
-->
|
||||
|
||||
## Try out <concept>
|
||||
|
||||
<!--
|
||||
If applicable, include a section with links to the related quickstart, how-to guides, or tutorials. -->
|
||||
|
||||
### Quickstarts and tutorials
|
||||
|
||||
Want to put the Dapr <topic> API to the test? Walk through the following quickstart and tutorials to see <topic> in action:
|
||||
|
||||
| Quickstart/tutorial | Description |
|
||||
| ------------------- | ----------- |
|
||||
| [<topic> quickstart](link) | Description of the quickstart. |
|
||||
| [<topic> tutorial](link) | Description of the tutorial. |
|
||||
|
||||
### Start using <topic> directly in your app
|
||||
|
||||
Want to skip the quickstarts? Not a problem. You can try out the <topic> building block directly in your application. After [Dapr is installed](link), you can begin using the <topic> API, starting with [the <topic> how-to guide](link).
|
||||
|
||||
|
||||
-->
|
||||
|
||||
## Next steps
|
||||
|
||||
<!--
|
||||
Link to related pages and examples. For example, the related API spec, related building blocks, etc.
|
||||
-->
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Workflow scenarios"
|
||||
linkTitle: "Workflow scenarios"
|
||||
weight: 4000
|
||||
description: Learn how to invoke the workflow API using either HTTP or gRPC
|
||||
---
|
|
@ -30,4 +30,5 @@ Hit the ground running with our Dapr quickstarts, complete with code samples aim
|
|||
| Actors | Coming soon. |
|
||||
| Observability | Coming soon. |
|
||||
| Configuration | Coming soon. |
|
||||
| Distributed Lock | Coming soon. |
|
||||
| Distributed Lock | Coming soon. |
|
||||
| Workflow | Coming soon. |
|
Loading…
Reference in New Issue