Merge branch 'main' into docs/add-project

Author: sanjay7178

.github/workflows/main.yaml

@@ -50,6 +50,7 @@ jobs:
         run: |
           poetry check
           poetry install
+          python -m nltk.downloader punkt
 
       - name: Linter
         if: ${{ github.event_name == 'pull_request' }}

conda/dev.yaml

@@ -6,3 +6,4 @@ dependencies:
   - python <3.12
   - pip
   - poetry
+  - nodejs

mkdocs.yml

@@ -16,55 +16,72 @@ theme:
     primary: indigo
 
 extra_css:
-  - css/style.css
-  - css/index.css
+  - css/base.css
+  - css/blog.css
+  - css/code.css
+  - css/content.css
+  - css/footer.css
+  - css/home.css
+  - css/nav.css
+  - css/partners.css
+  - css/search.css
+  - css/team.css
+  - css/tokens.css
+  - css/utilities.css
 
 extra_javascript:
-  - js/bundle.js
-  - js/search.js
-  - js/index.json
+  - js/theme.js
+  - js/osl-search.js
+  - js/vendor/lunr.min.js
+  - js/vendor/lunr.stemmer.support.min.js
+  - js/vendor/lunr.multi.min.js
+  - js/vendor/lunr.es.min.js
+  - js/vendor/lunr.pt.min.js
 
 nav:
   - Blog: "blog/index.md"
   - Projects:
-      - index: "projects/index.md"
+      - Overview: "projects/index.md"
       - Incubation: "projects/incubation/index.md"
-      - Affiliation:
-          - index: "projects/affiliation/index.md"
+      - Affiliation: "projects/affiliation/index.md"
       - All Projects: "projects/list/index.md"
   - Opportunities:
-      - index: opportunities/index.md
+      - Overview: opportunities/index.md
       - OSS Internship:
-          - index: "opportunities/internships/oss/index.md"
+          - Overview: "opportunities/internships/oss/index.md"
           - Project Ideas: "opportunities/internships/oss/project-ideas/index.md"
-          - Interns Guide: "opportunities/internships/guides/interns/index.md"
-          - Projects Ideas Template: "opportunities/internships/templates/projects-ideas/index.md"
-          - Candidates's Project Proposal Template: "opportunities/internships/templates/candidate-proposal/index.md"
+          - "Contribution Guidelines": "opportunities/guides/contribution/index.md"
+          - "Candidates' Guide": "opportunities/internships/guides/interns/index.md"
+          - "Template: Projects Ideas": "opportunities/internships/templates/projects-ideas/index.md"
+          - "Template: Candidates's Project Proposal": "opportunities/internships/templates/candidate-proposal/index.md"
       - OSS Research Seed Internship:
-          - index: "opportunities/internships/oss-research-seed/index.md"
+          - Overview: "opportunities/internships/oss-research-seed/index.md"
           - Project Ideas: "opportunities/internships/oss-research-seed/project-ideas/index.md"
-          - Interns Guide: "opportunities/internships/guides/interns/index.md"
-          - Projects Ideas Template: "opportunities/internships/templates/projects-ideas/index.md"
-          - Candidates's Project Proposal Template: "opportunities/internships/templates/candidate-proposal/index.md"
+          - "Contribution Guidelines": "opportunities/guides/contribution/index.md"
+          - "Candidates' Guide": "opportunities/internships/guides/interns/index.md"
+          - "Template: Projects Ideas": "opportunities/internships/templates/projects-ideas/index.md"
+          - "Template: Candidates's Project Proposal": "opportunities/internships/templates/candidate-proposal/index.md"
       - Google Summer of Code:
-          - index: "opportunities/gsoc/index.md"
+          - Overview: "opportunities/gsoc/index.md"
           - Project Ideas: "opportunities/gsoc/project-ideas/index.md"
-          - Contributor Guide: "opportunities/gsoc/guides/contributor/index.md"
-          - Project Idea Template: "opportunities/gsoc/templates/project-ideas.md"
-          - Contributor Project Proposal Template: "opportunities/gsoc/templates/contributor-proposal.md"
+          - "Contribution Guidelines": "opportunities/guides/contribution/index.md"
+          - "Candidates' Guide": "opportunities/gsoc/guides/contributor/index.md"
+          - "Template: Project Idea": "opportunities/gsoc/templates/project-ideas.md"
+          - "Template: Candidates Project Proposal": "opportunities/gsoc/templates/contributor-proposal.md"
   - Partnership:
-      - index: "partnership/index.md"
+      - Overview: "partnership/index.md"
       - Partners: "partnership/partners/index.md"
+      - Open Proposals:
+          - Overview: "partnership/open-proposals/index.md"
+          - Community Training: "partnership/open-proposals/community-training/index.md"
   - Learning:
-      - index: learning/index.md
-      - Events:
-          - index: learning/events/index.md
-      - Study Groups:
-          - index: learning/study-groups/index.md
+      - Overview: learning/index.md
+      - Events: learning/events/index.md
+      - Study Groups: learning/study-groups/index.md
   - About:
-      - index: "about/index.md"
+      - Overview: "about/index.md"
       - About OSL:
-          - index: "about/index.md"
+          - Overview: "about/index.md"
           - Contact Us: about/contact/index.md
           - Our Formula: "about/formula/index.md"
           - Roadmap: about/roadmap/index.md
@@ -73,7 +90,7 @@ nav:
       - Team: about/team/index.md
       - Fiscal Sponsor: about/fiscal-sponsor/index.md
       - Guidelines:
-          - index: about/guidelines/index.md
+          - Overview: about/guidelines/index.md
           - Articles: about/guidelines/articles/index.md
           - DEI: about/guidelines/dei/index.md
           - Mentoring: about/guidelines/mentoring/index.md
@@ -89,6 +106,7 @@ markdown_extensions:
   - pymdownx.inlinehilite
   - pymdownx.snippets
   - pymdownx.superfences
+  - mdx_truly_sane_lists
 
 plugins:
   - include-markdown:
@@ -128,3 +146,10 @@ plugins:
       enabled: true
       enable_creation_date: false
       type: iso_date
+
+  - search:
+      lang:
+        - en
+        - es
+        - pt
+      prebuild_index: true

pages/blog/language-server-protocol-lsp-how-editors-speak-code/header.png

@@ -0,0 +1,107 @@
+---
+title: "Language Server Protocol (LSP): How Editors Speak Code"
+slug: "language-server-protocol-lsp-how-editors-speak-code"
+date: 2025-08-15
+authors: ["Ansh Arora"]
+tags: ["Makim", "Automation", "Developer Experience"]
+categories: ["Devops", "Dev Tools"]
+description: |
+  The Language Server Protocol (LSP) powers modern code editors like VS Code by 
+  enabling real-time autocompletion, hover info, diagnostics, and more.
+thumbnail: "/header.png"
+template: "blog-post.html"
+---
+
+# Language Server Protocol (LSP): How Editors Speak Code
+
+When you open a code file in VS Code and get real-time suggestions, hover
+tooltips, or error squiggles, have you ever wondered **how** your editor
+understands the language you’re writing in?
+
+This magic isn’t hardcoded per-language into the editor. Instead, it’s often
+powered by something called the **Language Server Protocol (LSP)**.
+
+Let’s dive into what LSP is, why it exists, and how it powers modern development
+environments.
+
+## What is the Language Server Protocol?
+
+The **Language Server Protocol (LSP)** is a standardized way for development
+tools (like VS Code, Vim, or Emacs) to communicate with language-specific
+services (called language servers).
+
+Instead of writing new editor plugins for every language and every editor, **LSP
+decouples the logic**:
+
+- The **editor (client)** handles the UI and editor behavior.
+- The **language server** handles parsing, validation, completions, and other
+  language-specific logic.
+
+They talk to each other via a common JSON-RPC protocol over standard
+input/output, TCP, or WebSockets.
+
+## Why was LSP created?
+
+Before LSP, supporting multiple languages across editors was a mess:
+
+- Each editor needed custom plugins.
+- Each language had to build and maintain these plugins.
+
+This was inefficient and hard to maintain.
+
+**Microsoft introduced LSP in 2016**, alongside VS Code, to fix this
+fragmentation. Now, language authors can focus on building a single LSP server,
+and editors can plug into it easily.
+
+![LSP Languages and Editors](https://code.visualstudio.com/assets/api/language-extensions/language-server-extension-guide/lsp-languages-editors.png)
+
+## Core Features of LSP
+
+Here are some features LSP enables out-of-the-box:
+
+- Autocompletion
+- Go to Definition
+- Hover Information
+- Diagnostics (errors/warnings)
+- Formatting
+- Find References
+- Rename Symbol
+- Signature Help
+
+These features work **consistently across any editor** that supports!
+
+## How Does It Work?
+
+Here's a simplified lifecycle of how an editor (client) talks to a language
+server:
+
+1. **Editor launches the language server.**
+2. **Sends an `initialize` request** to begin communication.
+3. As you edit:
+
+   - Sends `textDocument/didOpen`, `didChange`, or `didSave`.
+   - Receives back diagnostics or suggestions.
+
+4. On hover, completion, or definition jumps:
+
+   - Sends `textDocument/hover`, `completion`, or `definition` requests.
+   - Displays server responses in the UI.
+
+All of this happens over a well-defined set of JSON-RPC messages.
+
+### Anatomy of a Language Server
+
+A language server is just a **program** that:
+
+- Parses the user’s code (possibly building an AST or symbol table).
+- Responds to LSP method calls.
+- Tracks open files and their versions.
+
+## Final Thoughts
+
+The Language Server Protocol has quietly become the **backbone of modern
+developer tooling**. Whether you’re building an IDE, a DSL, or a configuration
+tool, LSP lets you ship a polished editing experience with far less effort.
+
+If you're working on your own language, plugin, or platform, building an LSP
+server is one of the smartest investments you can make.

pages/blog/language-server-protocol-lsp-how-editors-speak-code/index.md

@@ -0,0 +1,103 @@
+---
+title: "Packaging a VS Code Extension Using pnpm and VSCE"
+slug: "packaging-a-vs-code-extension-using-pnpm-and-vsce"
+date: 2025-08-31
+authors: ["Ansh Arora"]
+tags: ["Makim", "Automation", "VSCode", "pnpm", "esbuild"]
+categories: ["Packaging", "Node", "Extensions"]
+description: |
+  A step-by-step guide to packaging and publishing VS Code extensions with pnpm and vsce, 
+  covering how to avoid dependency resolution issues.
+thumbnail: "/header.png"
+template: "blog-post.html"
+---
+
+# Packaging a VS Code Extension Using pnpm and VSCE
+
+VS Code’s `vsce` tool doesn't play nicely with `pnpm` out of the box; here’s a
+proven workaround using bundling and the `--no-dependencies` flag to get things
+running smoothly.
+
+---
+
+## Why pnpm + vsce can be problematic
+
+`vsce` relies on `npm list --production --parseable --depth=99999`, which fails
+under pnpm's symlink-based dependency management, often throwing
+`npm ERR! missing:` errors.  
+([github.com](https://github.com/microsoft/vscode-vsce/issues/421),
+[daydreamer-riri.me](https://daydreamer-riri.me/posts/compatibility-issues-between-vsce-and-pnpm/))
+
+---
+
+## Solution Overview
+
+1. **Bundle your extension** using a bundler such as **esbuild** or **Webpack**
+2. **Use `--no-dependencies`** when running `vsce package` and `vsce publish`
+
+Because all dependencies are bundled, `vsce` no longer needs to resolve them
+from `node_modules`.
+
+---
+
+## Step-by-Step Setup
+
+### 1. Install Tools
+
+```bash
+pnpm add -D @vscode/vsce esbuild
+```
+
+@vscode/vsce` is the CLI for packaging and publishing VSCode extensions. Recent
+versions (e.g., v3.6.0) support npm (≥6) and Yarn (1.x), but don't officially
+support pnpm.
+
+### 2\. Configure `package.json`
+
+Scripts Add build and packaging commands: jsonc Copy code
+
+```json
+{
+  "scripts": {
+    "vscode:prepublish": "pnpm run bundle",
+    "bundle": "esbuild ./src/extension.ts --bundle --outfile=out/main.js --external:vscode --format=cjs --platform=node --minify",
+    "package": "pnpm vsce package --no-dependencies",
+    "publish": "pnpm vsce publish --no-dependencies"
+  }
+}
+```
+
+- `vscode:prepublish`: runs before packaging; bundles source using esbuild
+- `bundle`: compiles `extension.ts` into `out/main.js` and excludes the `vscode`
+  module
+- `package` / `publish`: calls VSCE via pnpm, skipping dependency resolution
+
+### 3\. Why It Works
+
+By bundling dependencies manually, `vsce` doesn’t need to resolve them during
+packaging or publishing. The `--no-dependencies` option avoids pnpm’s symlink
+issues entirely.
+
+## Sample `package.json` Snippet
+
+```json
+{
+  "devDependencies": {
+    "@vscode/vsce": "^3.6.0",
+    "esbuild": "^0.XX.X"
+  },
+  "scripts": {
+    "vscode:prepublish": "pnpm run bundle",
+    "bundle": "esbuild ./src/extension.ts --bundle --outfile=out/main.js --external:vscode --format=cjs --platform=node --minify",
+    "package": "pnpm vsce package --no-dependencies",
+    "publish": "pnpm vsce publish --no-dependencies"
+  }
+}
+```
+
+### **Wrap-Up**
+
+Using **pnpm** with VS Code extensions involves a few extra steps because `vsce`
+doesn’t support pnpm’s dependency structure directly. The ideal workflow: _
+**Bundle your extension first**, then _ **Use `--no-dependencies`** to package
+and publish safely.

pages/blog/packaging-a-vs-code-extension-using-pnpm-and-vsce/header.png

@@ -34,14 +34,18 @@ partners:
     url: https://www.pyopensci.org/
     logo: /images/partners/pyopensci.png
 
-  - name: PyDataStructs
-    url: https://pydatastructs.readthedocs.io/en/stable
-    logo: /images/partners/pydatastructs.png
-
   - name: IGDORE
     url: https://igdore.org/
     logo: /images/partners/IGDORE-logo-200pxx200px.png
 
+  - name: Data Umbrella
+    url: https://dataumbrella.org/
+    logo: /images/partners/dataumbrella.png
+
+  - name: TeleHealthCareAI
+    url: https://telehealthcareai.org/
+    logo: /images/partners/thcai.png
+
 initiatives:
   - title: Community
     description: |