Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

ChatGPT education plugins: What changes for developers - #3153

Merged
atharvadeosthale merged 8 commits into
mainfrom
chatgpt-education-plugins-what-changes-for-developers
Aug 12, 2026
Merged

atharvadeosthale merged 8 commits into
mainfrom
chatgpt-education-plugins-what-changes-for-developers

Conversation

@aishwaripahwa12

Copy link
Copy Markdown
Contributor

Latest blog

@appwrite

appwrite Bot commented Aug 6, 2026 •

Copy link
Copy Markdown

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
聽website
69d7f2670014e24571ca
Ready Ready View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
聽website
68496a17000f03d62013
Queued Queued View Logs Preview URL QR Code


Tip

MCP server integration brings LLM superpowers to Claude Desktop and Cursor IDE

@greptile-apps

greptile-apps Bot commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds a new article about ChatGPT education plugins and their implications for EdTech developers.

  • Adds the Markdoc post, including metadata, FAQs, comparisons, architecture guidance, and resource links.
  • Adds the optimized AVIF cover asset and its corresponding optimization-cache entry.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
src/routes/blog/post/chatgpt-education-plugins-what-changes-for-developers/+page.markdoc Adds a complete blog post with valid listing metadata, educational-plugin analysis, Appwrite guidance, and resource links.
static/images/blog/chatgpt-education-plugins-what-changes-for-developers/cover.avif Adds the cover image referenced by the post frontmatter.
.optimize-cache.json Adds the corresponding cover-image optimization cache entry; the differing extension is intentional under repository rules.

Reviews (2): Last reviewed commit: "Apply suggestion from @aishwaripahwa12" | Re-trigger Greptile

| What the workflow needs | Backend primitive | Why it matters here |
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Teacher, student, and admin accounts with district-level roles | [Auth](/docs/products/auth) and [Teams](/docs/products/auth/teams) | A district is a team, a class is a team, and roles decide who can trigger which agentic action |
| Rosters, standards mappings, assignments, progress data | [Databases](/docs/products/databases) with [document-level permissions](/docs/products/databases/permissions) | A student record should be readable only by that student and the roles you explicitly grant |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should not be using documents and collections anymore.


Three rules worth applying regardless of which backend you pick:

* **Put permissions on the data, not the UI.** Document-level rules survive an agent calling your API directly. A hidden button does not.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

@atharvadeosthale
atharvadeosthale merged commit ddc06b4 into main Aug 12, 2026
7 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants