Conversation
Interactive terminal UI at /dev that introduces Appwrite's backend services through a boot sequence animation and navigable menu. Products are explained inline with SDK examples, easter eggs reward curious developers, and only docs/signup link externally. Made-with: Cursor
Greptile SummaryThis PR adds a standalone interactive terminal-style landing page at Key issues found:
Confidence Score: 4/5
Important Files Changed
Reviews (1): Last reviewed commit: "Add /dev terminal-style landing page" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| function processCmd(v){ | ||
| var low=v.toLowerCase(); | ||
| if(state==='menu'){ | ||
| for(var i=0;i<MAIN_MENU.length;i++){if(low===MAIN_MENU[i].k){doMain(MAIN_MENU[i]);return}} | ||
| } |
There was a problem hiding this comment.
When a user types 2, 3, or 4 directly into the terminal input and presses Enter, the prompt is removed (line 160 in handleInput) and is never restored.
The execution path is:
handleInputremoves the prompt row (inputEl.parentElement.remove())processCmdmatches the number inMAIN_MENUat line 168 and callsdoMain()thenreturns immediatelydoMainfor'docs'and'signup'only callswindow.open(...)— it does not calladdPrompt()processCmdexits early, so theaddPrompt()calls further down (lines 174, 178, 183, 192) are never reached
The user is left in 'menu' state with the menu items still visible but no input field. They can only recover via keyboard shortcuts (1 → products, then Escape → goHome() which calls drawMainMenu() → addPrompt()), which is not obvious.
Note: this bug does not affect keyboard shortcuts (pressing 2/3/4 without input focused goes through the global keydown listener at line 298 which calls doMain directly without touching the prompt).
The fix is to call addPrompt() inside doMain for the 'docs' and 'signup' branches:
| function processCmd(v){ | |
| var low=v.toLowerCase(); | |
| if(state==='menu'){ | |
| for(var i=0;i<MAIN_MENU.length;i++){if(low===MAIN_MENU[i].k){doMain(MAIN_MENU[i]);return}} | |
| } | |
| function doMain(m){ | |
| if(m.a==='products'){showProductList();return} | |
| if(m.a==='docs'){window.open('/docs','_blank');addPrompt();return} | |
| if(m.a==='signup'){window.open('https://cloud.appwrite.io','_blank');addPrompt();return} | |
| } |
| logo.src='/images/logos/logo.svg';logo.alt='Appwrite'; | ||
| logo.style.cssText='width:1.8em;height:1.8em;'; | ||
| var txt=document.createElement('div'); | ||
| txt.innerHTML='<div style="color:'+PK+';font-size:1.05em;font-weight:bold;letter-spacing:.05em;">APPWRITE</div><div style="color:#666;font-size:.72rem;">v1.6.0 \\u00b7 open-source backend \\u00b7 appwrite.io</div>'; |
There was a problem hiding this comment.
v1.6.0 is hardcoded here and again at line 340. This will become inaccurate as Appwrite releases new versions, making the terminal landing page feel dated. Consider either deriving the version dynamically (e.g. from a shared constant or package manifest) or omitting the specific patch version in favour of a major/minor string that changes less frequently.
| function handleInput(e){ | ||
| if(e.key==='Enter'){ | ||
| e.preventDefault(); | ||
| var v=inputEl.value.trim(); | ||
| inputEl.value=''; | ||
| if(!v)return; | ||
| ln(PROMPT+v,WH); | ||
| if(inputEl.parentElement)inputEl.parentElement.remove(); | ||
| processCmd(v); | ||
| } | ||
| } |
There was a problem hiding this comment.
The global keydown listener at line 295 exits early whenever the focused element is an INPUT, so pressing the back-navigation key while typing has no effect. The PR's test plan specifically calls out "Press Escape to navigate back through the hierarchy", but this only works when focus is outside the input.
Adding an extra key-check branch inside handleInput — before the Enter handler — would handle back-navigation consistently regardless of focus state.
WalkthroughThis change introduces a new terminal feature to the application. The first modification adds a new Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes 🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
src/routes/dev/+server.ts (3)
40-44: Consider adding basic accessibility attributes.The terminal UI lacks ARIA attributes (
role,aria-label,aria-live) which would help screen reader users. Given this is a novelty developer page, this is low priority but worth noting for inclusivity.♻️ Optional accessibility improvements
-<div id="out"></div> +<div id="out" role="log" aria-label="Terminal output" aria-live="polite"></div>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/dev/`+server.ts around lines 40 - 44, Add basic ARIA attributes to the terminal DOM elements to improve accessibility: add role and aria-label to the main container with id "root" or "win" (e.g., role="application" or "region" and a descriptive aria-label), mark the output area with id "out" as a live region (aria-live="polite" or "assertive") so screen readers announce updates, and ensure the title bar with id "bar" has an appropriate role or aria-label (or aria-hidden if decorative). Also consider adding tabindex="0" to the interactive container (id "win" or "out") to allow keyboard focus and navigation.
78-83: Menu items 3 and 4 have duplicate actions.Both "Start building" and "Sign up free" map to the same
'signup'action, which openscloud.appwrite.io. If intentional for different user intents, consider differentiating the labels or combining into a single entry.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/dev/`+server.ts around lines 78 - 83, MAIN_MENU contains two entries (items with k:'3' and k:'4') that both set a:'signup' causing duplicate actions; update the array to either remove one of them, combine them into a single entry, or change one entry's action to the intended unique route/action (e.g., 'start' or 'signupPromo') and adjust any consumers that rely on MAIN_MENU to handle the new action name; locate the MAIN_MENU definition and edit the objects for keys '3' and '4' to ensure each menu item has a distinct action or is consolidated into one.
281-281: Extract hardcoded version string to a constant.The version "v1.6.0" is duplicated at lines 281 and 340. Extract to a constant to simplify future updates.
♻️ Proposed fix to extract version constant
var PK='#fd366e',GR='#777',WH='#d4d4d4',DIM='#555'; var state='boot',menuBox=null,inputEl=null; var PROMPT='visitor@appwrite-cloud ~ % '; +var VERSION='v1.6.0';Then update line 281:
-txt.innerHTML='<div style="color:'+PK+';font-size:1.05em;font-weight:bold;letter-spacing:.05em;">APPWRITE</div><div style="color:`#666`;font-size:.72rem;">v1.6.0 \\u00b7 open-source backend \\u00b7 appwrite.io</div>'; +txt.innerHTML='<div style="color:'+PK+';font-size:1.05em;font-weight:bold;letter-spacing:.05em;">APPWRITE</div><div style="color:`#666`;font-size:.72rem;">'+VERSION+' \\u00b7 open-source backend \\u00b7 appwrite.io</div>';And line 340:
-ln('appwrite v1.6.0 \\u2014 open-source backend. all batteries included.',WH); +ln('appwrite '+VERSION+' \\u2014 open-source backend. all batteries included.',WH);Also applies to: 340-340
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/dev/`+server.ts at line 281, The hardcoded version string "v1.6.0" is duplicated; extract it to a single constant (e.g., APPWRITE_VERSION) and replace both inline occurrences so updates are centralized: add a top-level const APPWRITE_VERSION = 'v1.6.0' near the other module constants and change the two places that build the HTML (the txt.innerHTML assignment and the other occurrence referenced in the review) to interpolate/concatenate APPWRITE_VERSION instead of the literal.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/routes/dev/`+server.ts:
- Around line 224-264: showProductDetail can be re-entered during its async
animation causing duplicate DOM output; add a re-entry guard (e.g., a
module-scoped boolean like isAnimating or use the existing state var) at the top
of showProductDetail that early-returns if an animation is in progress, set the
flag before any awaits/animations and clear it at the end (and on any early exit
paths), and ensure back/cancel handlers also clear the flag so consecutive calls
are serialized/prevented; reference the function showProductDetail, the state
variable, and DOM cleanup points (menuBox, inputEl, o.appendChild) when
implementing the guard.
---
Nitpick comments:
In `@src/routes/dev/`+server.ts:
- Around line 40-44: Add basic ARIA attributes to the terminal DOM elements to
improve accessibility: add role and aria-label to the main container with id
"root" or "win" (e.g., role="application" or "region" and a descriptive
aria-label), mark the output area with id "out" as a live region
(aria-live="polite" or "assertive") so screen readers announce updates, and
ensure the title bar with id "bar" has an appropriate role or aria-label (or
aria-hidden if decorative). Also consider adding tabindex="0" to the interactive
container (id "win" or "out") to allow keyboard focus and navigation.
- Around line 78-83: MAIN_MENU contains two entries (items with k:'3' and k:'4')
that both set a:'signup' causing duplicate actions; update the array to either
remove one of them, combine them into a single entry, or change one entry's
action to the intended unique route/action (e.g., 'start' or 'signupPromo') and
adjust any consumers that rely on MAIN_MENU to handle the new action name;
locate the MAIN_MENU definition and edit the objects for keys '3' and '4' to
ensure each menu item has a distinct action or is consolidated into one.
- Line 281: The hardcoded version string "v1.6.0" is duplicated; extract it to a
single constant (e.g., APPWRITE_VERSION) and replace both inline occurrences so
updates are centralized: add a top-level const APPWRITE_VERSION = 'v1.6.0' near
the other module constants and change the two places that build the HTML (the
txt.innerHTML assignment and the other occurrence referenced in the review) to
interpolate/concatenate APPWRITE_VERSION instead of the literal.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 88346a5e-6e68-4860-8ff1-5dfd4c5e077f
📒 Files selected for processing (1)
src/routes/dev/+server.ts
| async function showProductDetail(idx){ | ||
| state='detail'; | ||
| if(menuBox)menuBox.remove(); | ||
| if(inputEl&&inputEl.parentElement)inputEl.parentElement.remove(); | ||
| var s=SVC[idx]; | ||
|
|
||
| ln('',WH); | ||
| var cmdText=PROMPT+'appwrite explain '+s.n; | ||
| var cmdDiv=el('div','color:'+WH+';white-space:pre-wrap;min-height:1em',''); | ||
| o.appendChild(cmdDiv); | ||
| for(var i=1;i<=cmdText.length;i++){ | ||
| cmdDiv.textContent=cmdText.slice(0,i); | ||
| scr(); | ||
| await w(18) | ||
| } | ||
| await w(300); | ||
|
|
||
| ln('',WH); | ||
| ln(s.n.toUpperCase(),PK); | ||
| ln('',WH); | ||
| ln(s.why,WH); | ||
| ln('',WH); | ||
| ln(' '+s.tl,'#888'); | ||
| ln('',WH); | ||
|
|
||
| var btns=document.createElement('div'); | ||
| var docsBtn=document.createElement('a'); | ||
| docsBtn.className='cta';docsBtn.textContent='read the docs'; | ||
| docsBtn.href=s.doc;docsBtn.target='_blank'; | ||
| var signBtn=document.createElement('a'); | ||
| signBtn.className='cta cta-primary';signBtn.textContent='start building'; | ||
| signBtn.href='https://cloud.appwrite.io';signBtn.target='_blank'; | ||
| btns.appendChild(signBtn);btns.appendChild(docsBtn); | ||
| o.appendChild(btns); | ||
|
|
||
| ln('',WH); | ||
| var back=el('div','color:#555;font-size:.72rem;cursor:pointer;margin-top:.25em','\\u2190 esc back to products \\u00b7 \\u2190\\u2190 esc esc back to menu'); | ||
| back.onclick=function(){showProductList()}; | ||
| o.appendChild(back); | ||
| scr() | ||
| } |
There was a problem hiding this comment.
Potential race condition during async animation.
If showProductDetail() is invoked rapidly (e.g., user clicks multiple products quickly), concurrent executions could render duplicate content since there's no guard preventing re-entry while the animation is in progress.
Consider adding a flag to skip or abort if already animating:
🛡️ Proposed fix to guard against concurrent executions
var state='boot',menuBox=null,inputEl=null;
+var animating=false;
var PROMPT='visitor@appwrite-cloud ~ % '; async function showProductDetail(idx){
+if(animating)return;
+animating=true;
state='detail';
if(menuBox)menuBox.remove();
if(inputEl&&inputEl.parentElement)inputEl.parentElement.remove();
var s=SVC[idx];
// ... rest of function ...
o.appendChild(back);
+animating=false;
scr()
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/routes/dev/`+server.ts around lines 224 - 264, showProductDetail can be
re-entered during its async animation causing duplicate DOM output; add a
re-entry guard (e.g., a module-scoped boolean like isAnimating or use the
existing state var) at the top of showProductDetail that early-returns if an
animation is in progress, set the flag before any awaits/animations and clear it
at the end (and on any early exit paths), and ensure back/cancel handlers also
clear the flag so consecutive calls are serialized/prevented; reference the
function showProductDetail, the state variable, and DOM cleanup points (menuBox,
inputEl, o.appendChild) when implementing the guard.
Rename route from /dev to /terminal. Add content negotiation so LLMs requesting text/markdown get a warm, structured overview of Appwrite with product details and SDK examples. Add noscript fallback, OG/Twitter meta tags, JSON-LD schemas, and register the page in llms-config.ts. Made-with: Cursor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
src/routes/terminal/+server.ts (1)
15-17: Consider adding cache-control header for consistency.The markdown response includes
cache-control: public, max-age=3600but the HTML response has no caching headers. For consistency and to reduce server load, consider adding the same cache policy.♻️ Proposed fix
return new Response(HTML, { - headers: { 'content-type': 'text/html; charset=utf-8' } + headers: { + 'content-type': 'text/html; charset=utf-8', + 'cache-control': 'public, max-age=3600' + } });🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/terminal/`+server.ts around lines 15 - 17, The HTML response created with new Response(HTML, { headers: { 'content-type': 'text/html; charset=utf-8' } }) lacks caching headers; add the same cache policy used for the markdown response by including a 'cache-control': 'public, max-age=3600' header alongside 'content-type' so the HTML response (the Response constructed with HTML) is cached consistently.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/routes/llms-config.ts`:
- Around line 16-21: The new page object for '/terminal' in llms-config.ts is
missing the required fullContent property used by the llms-full.txt handler (it
accesses SPECIAL_PAGES and page.fullContent); add a fullContent string to the
'/terminal' entry that contains the full markdown/text block expected by the
exporter (matching structure used by other SPECIAL_PAGES entries) so
page.fullContent is defined when llms-full.txt iterates SPECIAL_PAGES.
- Around line 15-16: There is a syntax error in the array literal of LLM
configuration objects: the two adjacent object literals are missing a separating
comma. Fix it by inserting a comma after the closing brace of the first object
(i.e., between "}" and the following "{") in the LLMs configuration array so the
objects are valid array elements; you can also add a trailing comma for
consistency.
---
Nitpick comments:
In `@src/routes/terminal/`+server.ts:
- Around line 15-17: The HTML response created with new Response(HTML, {
headers: { 'content-type': 'text/html; charset=utf-8' } }) lacks caching
headers; add the same cache policy used for the markdown response by including a
'cache-control': 'public, max-age=3600' header alongside 'content-type' so the
HTML response (the Response constructed with HTML) is cached consistently.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4b67b49c-3397-452b-b00d-f62aa41c2c68
📒 Files selected for processing (2)
src/routes/llms-config.tssrc/routes/terminal/+server.ts
| } | ||
| // Add more special pages here as needed | ||
| { |
There was a problem hiding this comment.
Syntax error: missing comma between array elements.
The static analysis correctly identifies a missing comma after the first object (line 15) and before the second object (line 16). This will cause a parse error.
🐛 Proposed fix
'Browse integrations by category including AI, Deployments, Messaging, Auth, Payments, Logging, MCP, Databases, Search, Sites, and Storage.'
- }
+ },
{📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| } | |
| // Add more special pages here as needed | |
| { | |
| }, | |
| { |
🧰 Tools
🪛 Biome (2.4.7)
[error] 16-16: expected , but instead found {
(parse)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/routes/llms-config.ts` around lines 15 - 16, There is a syntax error in
the array literal of LLM configuration objects: the two adjacent object literals
are missing a separating comma. Fix it by inserting a comma after the closing
brace of the first object (i.e., between "}" and the following "{") in the LLMs
configuration array so the objects are valid array elements; you can also add a
trailing comma for consistency.
| { | ||
| href: '/terminal', | ||
| title: 'Appwrite Terminal', | ||
| description: | ||
| 'Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting. Includes product explanations, SDK examples, and developer easter eggs.' | ||
| } |
There was a problem hiding this comment.
Missing fullContent field required by llms-full.txt handler.
The context snippet from src/routes/llms-full.txt/+server.ts shows that it iterates over SPECIAL_PAGES and accesses page.fullContent to build markdown blocks. The new /terminal entry lacks this field, which will result in undefined being interpolated into the output.
🛠️ Proposed fix — add fullContent field
{
href: '/terminal',
title: 'Appwrite Terminal',
description:
- 'Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting. Includes product explanations, SDK examples, and developer easter eggs.'
+ 'Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting. Includes product explanations, SDK examples, and developer easter eggs.',
+ fullContent: `Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting.
+
+Products: Auth (authentication with OAuth, magic links, MFA), Databases (document database with REST/GraphQL), Storage (file storage with transforms), Functions (serverless in multiple runtimes), Messaging (push, email, SMS), Realtime (WebSocket subscriptions), and Hosting (static/SSR deployment).
+
+Includes SDK code examples and links to documentation for each product.`
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| { | |
| href: '/terminal', | |
| title: 'Appwrite Terminal', | |
| description: | |
| 'Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting. Includes product explanations, SDK examples, and developer easter eggs.' | |
| } | |
| { | |
| href: '/terminal', | |
| title: 'Appwrite Terminal', | |
| description: | |
| 'Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting. Includes product explanations, SDK examples, and developer easter eggs.', | |
| fullContent: `Interactive terminal-style overview of Appwrite — an open-source backend with auth, databases, storage, functions, realtime, messaging, and hosting. | |
| Products: Auth (authentication with OAuth, magic links, MFA), Databases (document database with REST/GraphQL), Storage (file storage with transforms), Functions (serverless in multiple runtimes), Messaging (push, email, SMS), Realtime (WebSocket subscriptions), and Hosting (static/SSR deployment). | |
| Includes SDK code examples and links to documentation for each product.` | |
| } |
🧰 Tools
🪛 Biome (2.4.7)
[error] 16-16: expected , but instead found {
(parse)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/routes/llms-config.ts` around lines 16 - 21, The new page object for
'/terminal' in llms-config.ts is missing the required fullContent property used
by the llms-full.txt handler (it accesses SPECIAL_PAGES and page.fullContent);
add a fullContent string to the '/terminal' entry that contains the full
markdown/text block expected by the exporter (matching structure used by other
SPECIAL_PAGES entries) so page.fullContent is defined when llms-full.txt
iterates SPECIAL_PAGES.
1 participant
Summary
/devroute serving an interactive terminal UI that introduces Appwrite's backend servicesappwrite initloading all 7 services (auth, databases, storage, functions, messaging, realtime, hosting)vim,sudo rm -rf /,git push --force,whoami, etc.) and natural language commands+server.tsTest plan
/devand watch the boot animation complete1— verify product list appearsvim,whoami,sudo rm -rf /,helpauth) and press Enter — verify it shows that product's detailMade with Cursor
Summary by CodeRabbit
/terminal. The terminal supports service and documentation browsing with intelligent content formatting, delivering responses in both HTML and markdown formats depending on client preferences, with server-side caching enabled.