search

build-on-aws / content

Content repository for Community.aws
https://community.aws
Creative Commons Attribution Share Alike 4.0 International
48 stars 164 forks source link

Building a Amplify Flutter for Web Page using a Serverless CDK Backend in Typescript with AppSync Merged APIs #537

Closed Lock128 closed 11 months ago

Lock128 commented 1 year ago

What is the title of the content you're proposing?

Building a Amplify Flutter for Web Page using a Serverless CDK Backend in Typescript with AppSync Merged APIs

Describe your content, including takeaways for the reader, in three to four sentences.

I would love to contribute a post that gives a "starting point" for building out an application that looks similar to our community builders speaker directory - see the overview post we had here: https://dev.to/aws-builders/presenting-aws-speakers-directory-an-ai-hackathon-project-19je As part of this post, we would take a deeper look into the architeture and how to integrate with Amplify SDK for Flutter as well as. the Serverless, AppSync backed backend.

What theme is your content related to?

Web development, Serverless

When can you provide your first draft of content by?

End of july/mid august

What are 2-3 links to previous written content you have published?

My personal blog is at lockhead.info, but i cross-post to https://dev.to/lockhead and the community builders ORG there

buildon-publication-bot[bot] commented 1 year ago

Thank you for your submission! We will review it shortly!

bketelsen commented 1 year ago

Great topic, we'd love to see it.

bketelsen commented 1 year ago

Thank you for your interest in the BuildOn.AWS Community Authoring Pilot.

Step 1: Read the Author Quick Start Guide – note that in the publishing process listed on that page we’ve already done steps 0, 1, and 2. Step 2: Write your first draft – you’ll need to create a fork of the content repository, create a new git branch for your article, then submit a pull request with your first draft. The linked guide has all the details. Step 3: Submit your Pull Request – our team will get a notification that your article is ready for review and it will be added to our editorial queue. We’ll check the syntax of the markdown and other technical details, and we’ll read the article to make sure it meets our publication guidelines. After your submit the pull request, you’ll get a link to a preview version of the article so you can check it for formatting and other errors. The link will come in a comment to your pull request. Don’t share this link, it’s not the final publication link, just a place for you to review what you’ve written before it’s published. Step 4: Publication! – when the review is completed, we’ll merge the pull request and the publication will be live in just a few moments.

Our team will be on standby to answer any questions you have along the way. Here are some resources that may be helpful:

FAQ Code of Conduct Quick Start Guide

Please reach out if you have any questions or anything is unclear. You’re the first to go through this process, so you might find gaps in our documentation or bumps in the process… let us know so we can fix it!

Lock128 commented 1 year ago

I am late with the deliverable here - will get back to you with a new planned date.