Deliver blog: Kabanero Developer Experience: Codewind and Appsody come together in your IDE

[nateziemann]

In support of the Kabanero August 26th release, we are creating a blog series, leading up to the Sept events starting Sept 9th.

Title: Kabanero Developer Experience:  Codewind and Appsody come together in your IDE

show how codewind and appsody are now one integrated IDE experience. How you can use Codewind and not have to install Appsody separate or drive Appsody from CLI unless developer specifically wants the CLI experience.

Describe all the integrations for appsody that have been delivered, how you no longer need to install and configure multiple tools.

Describe how you can see Appsody templates either in the Kabanero public collection hub or the appsody hub. Desribe how you can drive everything from the Appsody CLI from within Codewind.

Above are just a bunch of ideas for author to organize and flush out a good blog flow.

[nateziemann]

Author assigned:
Reviewer assigned:
Target: Week of Sept 4-6

@dianak2016 this should get assigned to Rob T to assign an author. He is not in our github board and should get invited to drive Kabanero Developer Experience items in our boards.

[rtaniwa]

@nateziemann here is a quick rough draft of how I see this getting laid out. Please note this is all I have so far...so lots of work for me to get this done by the end of next week. But wanted feedback on if this captures your intention:

### Blog text
• Introduction to cloud native development challenges and how Kabanero helps stitch technologies together to make the journey to cloud native development easier
• High level overview (one paragraph or so) of key value props of Appsody
• High level overview (one paragraph or so) of the key value props of Codewind

### Video
Use video for showing the integrated experience and flow:

1. Start with a vanilla VS Code install (and possibly Eclipse as well…or talk to how the experience is the same)
2. Show installation of the Codewind extension via the marketplace, or from directly within the IDE
3. Once installation is complete, activate download of Codewind container and mention that there is a one time download of the container that supports the back end services
4. Select menu option to create a new project to highlight the Appsody projects (do we mention this is essentially appsody list?)
5. Create a Node project using the Appsody Node.js and Express template (possibly talk about how this is driving the appsody commands init and run)
6. Show app building, and started states
7. Right click on the application, and show various menu options
8. Open the application
9. Open the app into the workspace, and navigate to app.js and make and edit
10. Show that application changes take place instantaneously
11. Show application overview page
12. Show performance dashboard
13. Run load
14. Restart in debug
15. Make a code change and then launch to hit the break point
16. Re-run load?
17. Show performance dashboard again?
18. Show logs
19. Do we want to show the ability to point Codewind to the Kabanero hub (if so, we should likely remove the Appsody hub to avoid overflow of duplicate templates) – would require manual editing of the file to add a Kabanero repo of collections

Other possible highlights:
• Show Appsody commands in the command palette?
• Open a shell?

[erpenbach]

@rtaniwa I think this is a inclusive list of things that will show off much of the experience with Codewind and Appsody. We may want to consider multiple videos to make more consumable such as under 2 minutes. This might also help with staging the release of the content and get the first blog and video out sooner.

[alohr51]

Is there a blog available that needs to go out for this?

[rtaniwa]

Not yet. Hopefully I can put it together, along with a video, for next week.

[marikaj123]

Is ID review needed for this issue?

[jantley-ibm]

For ID review please assign @j-c-berger