
Weekend Creative Challenge: Cloud Poem Studio
Cloud Poem Studio is a playful web app that turns a mood, a place, and a colour into a short four-line poem. I built the live frontend with HTML, CSS, JavaScript, and GitHub Pages.
Weekend Creative Challenge: Cloud Poem Studio
A Small Place to Make a Little Sky
For this weekend challenge, I wanted to build something gentle, playful, and small enough that somebody could enjoy it in less than a minute.
That idea became Cloud Poem Studio: a tiny web app that creates a four-line poem from three simple choices. A visitor chooses a feeling, writes a place, picks a colour, and receives a short piece of creative writing.
The app is not designed to solve a big problem. Instead, it is meant to create a brief pause. I like the idea that a person can open the page between tasks, choose “quiet longing” and “a rain-washed city,” and leave with a tiny poem that did not exist a moment earlier.
I wanted the experience to feel more like receiving a postcard than filling out a form. That guided both the design and the feature set: warm colours, large expressive type, one small interaction, and no account or signup.
What Cloud Poem Studio Does
Cloud Poem Studio asks for three ingredients:
- A mood, such as soft wonder, bright mischief, or slow peace
- A place, such as a quiet beach, a city, or a room at home
- A colour to weave into the poem
After selecting the ingredients, the visitor clicks Make a little sky. The app displays a short four-line poem on an illustrated poem card. The visitor can copy the result or make another poem with different ingredients.
The public version includes a browser-based preview generator, so the experience works immediately on the live site. It is intentionally simple and gives the project a reliable starting point while I continue building the AWS-powered version.
How I Built It
I used plain HTML, CSS, and JavaScript for the frontend. I chose this approach because the app has a single screen and a focused interaction. Using simple web technologies helped me concentrate on the design and creative experience instead of spending the weekend configuring a large framework.
The HTML provides the poem controls and the result card. CSS creates the visual identity: a soft paper background, a warm orange poem card, a sun shape, and typography that makes the poem feel central. JavaScript reads the selected mood, place, and colour, then creates and displays the poem. It also includes a Copy poem button.
I hosted the frontend with GitHub Pages. This gave me a public link quickly and made it easy to share the work in progress with other builders.
AWS Architecture I Am Preparing
The repository also includes Terraform and Python code for the next stage of Cloud Poem Studio: connecting the interface to a serverless poem generator.
The planned request flow is:
GitHub Pages website ↓AWS Lambda Function URL ↓AWS Lambda ↓Amazon Bedrock with Amazon Nova Lite ↓A new four-line poem returned to the websiteTerraform defines the Lambda function, IAM permissions, CloudWatch log group, Lambda Function URL, and CORS settings. The Lambda code receives the mood, place, and colour from the browser, creates a concise prompt, and sends it to Amazon Bedrock through the Converse API.
I chose this architecture because it keeps the browser interface simple while leaving the creative generation on the backend. GitHub Pages remains responsible for the visual experience, while Lambda and Bedrock can provide a new poem whenever somebody uses the app.
Challenges and Decisions
The biggest design decision was keeping the scope intentionally narrow. It is easy to imagine adding poem collections, user profiles, saved poems, sharing links, and many themes. For this challenge, I chose to make one creative moment work well first.
Another challenge was building something that already feels complete while leaving room to learn more. The local preview generator means the public demo is usable today. At the same time, the Terraform and Lambda code give the project a clear path toward an AWS-powered version.
I also learned how important it is to describe an architecture honestly. The frontend is live on GitHub Pages today. The AWS resources are prepared in the repository and will be deployed as the next step. Documenting that distinction helps me understand what is complete and what I still need to learn.
What I Learned
This project reminded me that creativity and cloud learning can start with a very small idea. I learned how much atmosphere can be created with a few colours, a focused prompt, and a constraint like four short lines.
I also learned more about the relationship between a static website and a serverless backend. Even before deploying the AWS part, writing the Terraform configuration and Lambda function helped me understand the pieces involved: permissions, logging, a public HTTPS endpoint, CORS, and model invocation.
Most importantly, I learned that publishing an early version is valuable. A small live app gives an idea a real home, makes it easier to receive feedback, and creates momentum for the next stage.
Try Cloud Poem Studio
Cloud Poem Studio is a small beginning, but it has already made me more excited to keep building. My next step is to deploy the Lambda and Amazon Bedrock integration so every visitor can receive a fresh AI-generated little sky. ☁️
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article