SaaS waitlist tutorial blog

[atharvadeosthale]

No description provided.

[greptile-apps]

Greptile Summary

This PR adds a new tutorial blog post walking readers through building a SaaS waitlist landing page with React, Vite, and Appwrite's TablesDB API, along with the associated cover and screenshot images.

• The Appwrite Function event pattern in the "Where to go from here" section reads databases.*.rows.*.create, but the correct TablesDB event path includes the tables segment: databases.*.tables.*.rows.*.create. Any reader who copies this event trigger will end up with a function that never fires.

Confidence Score: 4/5

Safe to merge after correcting the event path; all code examples and API usage are otherwise accurate.

One P1 factual error: the Appwrite Function event path is missing the tables segment and would silently not trigger. Everything else — SDK imports, createRow usage, column types, permissions setup, and env variable conventions — checks out against current Appwrite docs.

src/routes/blog/post/build-saas-waitlist/+page.markdoc — incorrect event path near line 274.

Important Files Changed

Filename	Overview
src/routes/blog/post/build-saas-waitlist/+page.markdoc	New tutorial blog post for building a SaaS waitlist with Appwrite TablesDB; contains one incorrect event path in the "Where to go from here" section.
.optimize-cache.json	Adds image hashes for the seven new blog post images; routine cache update.

_{Reviews (1): Last reviewed commit: "init saas waitlist article" | Re-trigger Greptile}

[greptile-apps]

Incorrect event path for TablesDB row creation

The event pattern databases.*.rows.*.create is wrong for the TablesDB API. According to the Appwrite events documentation, the path for TablesDB includes a tables segment between databases and rows. A function configured with the pattern shown here will never fire.

Suggested change

	Create an [Appwrite Function](/docs/products/functions) that listens for the `databases.*.tables.*.rows.*.create` event on your `entries` table and sends a transactional email through your provider of choice. The user never has to wait for it on the form.

[atharvadeosthale]

Acknowledged, will be fixing this

[adityaoberai]

@atharvadeosthale did we fix this event?