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

Revisit use-cases & advanced-developer-use-cases chapters ambiguity #553

Open
domhanak opened this issue Feb 27, 2024 · 2 comments
Open
Assignees
Labels
serverless-workflow All issue targetting serverless workflow domain

Comments

@domhanak
Copy link
Contributor

The use-cases & advanced-developer-use-cases is a bit counter intuitive as we do not have any other use cases there.
Intention was to have also advanced use case without java and for Administrator persona there in the future.

Goal
Revisit the section to make the chapters more intuitive.

@domhanak domhanak added the serverless-workflow All issue targetting serverless workflow domain label Feb 27, 2024
@domhanak domhanak self-assigned this Feb 27, 2024
@domhanak
Copy link
Contributor Author

Idea for implementation:

  • use-case | Contains signpost for all different personas | non-java dev | java dev | administrator
    -- advanced-developer- use-cases | java dev
    -- advanced-use-cases | non java dev
    -- advanced-administrator-use-case | administrator of cluster

Ofc these need to be populated, with something.

@krisv @ricardozanini

@ricardozanini
Copy link
Member

non java dev we can replace with workflow developer, wdyt?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
serverless-workflow All issue targetting serverless workflow domain
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants