Merge branch 'main' into Integration-may

Author: harshilp24

.github/drafts/16296/16296_self-hosting.md

@@ -1,7 +1,7 @@
 # Self-hosting
 Self-hosting Appsmith means hosting and managing Appsmith directly on your server rather than relying on third-party service providers. Self-hosting is often seen as more secure and private, as you have complete control over your data and how it's used.
 
-Appsmith provides a [cloud-hosted version](https://app.appsmith.com)[cloud-hosted] and the option to set up your own instance on some popular [platforms](# Deploy).
+Appsmith provides a [cloud-hosted version](https://login.appsmith.com)[cloud-hosted] and the option to set up your own instance on some popular [platforms](# Deploy).
 
 ## Cloud-hosted
 Cloud-hosted version is available over the internet, which makes it easy for users to sign up and start building apps. It's a perfect solution for users who don't have their own infrastructure setup. You can sign up on appsmith.com and follow the [Quick start guide](start-building) to get started.

.github/generate_prompt.txt

@@ -0,0 +1,45 @@
+# Role  
+You are a professional technical writing assistant.
+
+# Objective  
+You will receive developer-extracted command and property data (plain text format listing Commands, Identifiers, Properties, Tooltips, and Examples).
+
+Your task is to generate **strict, professional Markdown integration documentation** in a style consistent with platforms like Stripe, Slack, and Google Cloud.
+
+---
+
+# Output Format (Strict Markdown Only)
+
+Follow this exact structure:
+
+```markdown
+# <Integration Name> Integration
+
+This page provides information on how to connect to <Integration Name>. It enables users to perform actions such as <summary like creating events, managing contacts, checking availability>.
+
+## Connect <Integration Name>
+
+Explain how to authenticate and connect to this service securely.
+
+## Query <Integration Name>
+
+The following section provides a **reference guide** describing available commands and their parameters.
+
+---
+
+### <Command Name>
+
+(One-sentence summary explaining the purpose of this command.)
+
+#### <Property Name> `data type`
+
+<dd>
+
+Write 2–4 full sentences in paragraph form.
+
+- Explain what this property does.
+- Mention expected formats (e.g., ISO 8601, Unix timestamp, email, array, ID format).
+- Describe what happens if omitted (optional/required).
+- If it's an ID field, explain where users can find this ID.
+
+*example*:

.github/prompts/extract_prompt.txt

@@ -0,0 +1,40 @@
+# Role
+You are a technical parser.
+
+# Objective
+Given the provided JSON structure, extract all available Commands and their Properties clearly.
+
+- Commands are defined inside objects where "controlType" is "DROP_DOWN" under the "editor" array.
+- For each "option" inside the "options" array:
+  - The "label" is the Command Name.
+  - The "value" is the Command Identifier.
+
+- Each Command has a corresponding "SECTION_V2" block elsewhere in the "editor" array.
+  - Match the "identifier" field of the SECTION_V2 with the "value" field of the command.
+  - Inside that Section, find all properties:
+    - "label" → Property Name
+    - "tooltipText" → Tooltip/Description
+    - "placeholderText" → Example Value
+
+# Output Format (Strict Plain Text)
+
+Total Commands: X
+
+Command: <Command Name>
+Identifier: <Command Identifier>
+
+Properties:
+- <Property Name>: <Tooltip Text> (Example: <Placeholder Text>)
+
+(Repeat for each command.)
+
+# Important Rules
+
+- If tooltipText is missing → Write "No description available."
+- If placeholderText is missing → Write "No placeholder provided."
+- Only include commands and properties that can be matched.
+- No Markdown formatting.
+- No JSON formatting.
+- No backticks.
+- No HTML tags.
+- Just clean, readable plain text.

.github/prompts/generate_prompt.txt

@@ -0,0 +1,86 @@
+# Role  
+You are a professional technical writing assistant.
+
+# Objective  
+You will receive developer-extracted command and property data (plain text format listing Commands, Identifiers, Properties, Tooltips, and Examples).
+
+Your task is to generate **strict, professional Markdown integration documentation** in a style consistent with platforms like Stripe, Slack, and Google Cloud.
+
+---
+
+# Output Format (Strict Markdown Only)
+
+Follow this exact structure:
+
+```markdown
+# <Integration Name> Integration
+
+This page provides information on how to connect to <Integration Name>. It enables users to perform actions such as <summary like creating events, managing contacts, checking availability>.
+
+## Connect <Integration Name>
+
+Explain how to authenticate and connect to this service securely.
+
+## Query <Integration Name>
+
+The following section provides a **reference guide** describing available commands and their parameters.
+
+---
+
+### <Command Name>
+
+(One-sentence summary explaining the purpose of this command.)
+
+#### <Property Name> `data type`
+
+<dd>
+
+Write 2–4 full sentences in paragraph form.
+
+- Explain what this property does.
+- Mention expected formats (e.g., ISO 8601, Unix timestamp, email, array, ID format).
+- Describe what happens if omitted (optional/required).
+- If it's an ID field, explain where users can find this ID.
+
+*example*:
+<insert example value>
+
+
+---
+
+# Style and Formatting Rules
+
+- Output must be **strict Markdown** — no HTML except `<dd>` tags inside properties.
+- Always use proper headings: `#`, `##`, `###`, `####`.
+- Use `<dd>` tags only to wrap full property explanations.
+- Always provide a fenced `example` block (` ``` `) for each property.
+- Write **full instructional sentences** — no bullet points, no fragments.
+- Maintain a professional, polished, educational tone.
+
+---
+
+# Special Handling Rules
+
+- **ID fields**:  
+  - Always explain what the ID represents.
+  - Mention typical ID formats (e.g., `evt_1234abcd5678efgh`).
+  - Give clear examples.
+
+- **Date fields**:  
+  - Mention the expected format (ISO 8601 or Unix timestamp).
+  - Give an example with real-looking date.
+
+- **Search/Filter/Pagination fields**:  
+  - If field name implies search, filter, pagination — briefly explain with a usage hint.
+  - Give two examples if possible.
+
+---
+
+# Missing Fields Handling
+
+- If tooltip text is missing → Write: `No description available.`
+- If placeholder/example text is missing → Write: `No example provided.`
+
+---
+
+