Add lemontea to v3 showcase

[MikeLINGxZ]

from wailsapp/awesome-wails#105

Summary by CodeRabbit

• Documentation
  • Added a new community showcase entry for lemontea, a desktop application featuring Wails v3, Go, and React with TypeScript support, demonstrating chat functionality and multi-agent workflow execution capabilities for local desktop integration.

[coderabbitai]

Walkthrough

A new documentation page was added to the community showcase section featuring a project called lemontea built with Wails v3, Go, React, and TypeScript. The entry includes frontmatter metadata and descriptive content with an embedded image reference.

Changes

Cohort / File(s)	Summary
Community Showcase Entry docs/src/content/docs/community/showcase/lemontea.md	New showcase documentation page with project metadata, description, image reference, and details about the lemontea project's tech stack and features.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A new showcase hops into view,
Lemontea's splendid debut!
With Wails and React in their embrace,
Go and TypeScript set the pace,
Community gardens forever grow,
Where talented projects steal the show! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is minimal and incomplete, missing critical sections like motivation, testing details, and checklist items required by the template.	Complete the description with issue reference (Fixes #), type of change selection, testing details, and checklist confirmation for documentation updates.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main change: adding a new showcase entry for the lemontea project to the v3 documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/src/content/docs/community/showcase/lemontea.md (1)

6-6: Use a more descriptive alt text for accessibility.

Line 6 alt text is generic; please describe the screenshot content so screen readers convey useful context.

Suggested tweak

-![lemontea](../../../../assets/showcase-images/lemontea_1.png)
+![Lemontea desktop app screenshot showing the chat and agent workflow interface](../../../../assets/showcase-images/lemontea_1.png)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/src/content/docs/community/showcase/lemontea.md` at line 6, The image
uses a generic alt text "lemontea" (the markdown token "![lemontea](...)") which
is not descriptive for screen readers; update that alt text to a concise,
descriptive phrase that conveys the screenshot content and purpose (for example:
"Lemontea web app homepage showing recipe list and search bar" or similar) by
replacing the "![lemontea]" token with a meaningful description in the image
markdown.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/src/content/docs/community/showcase/lemontea.md`:
- Line 6: The image uses a generic alt text "lemontea" (the markdown token
"![lemontea](...)") which is not descriptive for screen readers; update that alt
text to a concise, descriptive phrase that conveys the screenshot content and
purpose (for example: "Lemontea web app homepage showing recipe list and search
bar" or similar) by replacing the "![lemontea]" token with a meaningful
description in the image markdown.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 41d55674-ccf1-4e16-90f3-e4d7811206bd

📥 Commits

Reviewing files that changed from the base of the PR and between 5d3993c and 178fabe.

⛔ Files ignored due to path filters (1)

• docs/src/assets/showcase-images/lemontea_1.png is excluded by !**/*.png

📒 Files selected for processing (1)

• docs/src/content/docs/community/showcase/lemontea.md

[leaanthony]

✅ Triaged by Wails PR Reviewer

This PR has been reviewed and accepted.

Head Ref OID: 178fabe5b79d5abc04f8745a9364b5222c5a6650

---

This comment serves as a signature that this PR has been triaged. Future runs will skip this PR based on the headRefOid.

[leaanthony]

Thanks for adding lemontea! Two fixes needed before merge:

1. Missing index.mdx entry — the app won't appear in the showcase grid because docs/src/content/docs/community/showcase/index.mdx was not updated. Please add an entry following the same pattern as existing entries (thumbnail, href, title fields).

2. Missing trailing newline — lemontea.md is missing a newline at end of file.

Optional: converting lemontea_1.png to .webp would match the format used by newer showcase entries, but this is not required.

Example: https://github.com/wailsapp/wails/pull/5099/changes

[leaanthony]

Hi @MikeLINGxZ — thanks for the submission! Two things still needed before we can merge:

1. Add an entry to docs/src/content/docs/community/showcase/index.mdx

The showcase grid is populated from this file. Add the following entry before the closing ``]``` (after the Packsmith entry):

     {
       thumbnail: import("../../../../assets/showcase-images/packsmith-logo.webp"),
       href: "/community/showcase/packsmith",
       title: "Packsmith",
     }
+    ,{
+      thumbnail: import("../../../../assets/showcase-images/lemontea_1.png"),
+      href: "/community/showcase/lemontea",
+      title: "lemontea",
+    }
   ]}

2. Add a trailing newline to lemontea.md

The file currently ends without a newline (the diff shows \ No newline at end of file). Just add a blank line at the end of the file.

Once those two are in, this is good to merge!