This repository is a community-maintained static directory of remote-friendly tech companies, built with Eleventy v3 and deployed on Netlify. The core dataset consists of ~850+ Markdown files with YAML frontmatter, each representing a company profile with fields like remote policy, tech stack, region, and size. The site transforms this data into an accessible, searchable web interface with tagging, filtering, and SEO optimizations. While primarily a data curation project, it incorporates sophisticated build tooling: design tokens drive Tailwind CSS, custom WebC components provide UI patterns, and a CI pipeline validates contributions and checks for link rot. The repository is hybrid — it is both a curated dataset (data_research) and a static site application (application) — but its primary value lies in the maintained, validated collection of remote work opportunities.
code-server is a production-grade application that runs Visual Studio Code on a remote server, making it accessible via any modern web browser. It is not a research or data pipeline project; it is a full-stack web application with a Node.js/Express backend, WebSocket support, and extensive CLI tooling. The system authenticates users via password (argon2 hashing) or custom auth, manages VS Code server processes as child processes, and provides proxying for local services (path-based and domain-based). It includes a Helm chart for Kubernetes deployment, Docker images for multiple Linux distributions, and an install script for various platforms. The architecture is a monolith with a parent/child process wrapper for graceful restarts and signal handling, and it relies on external dependencies such as VS Code itself (as a submodule with quilt patches), Express, ws, httpolyglot, and argon2. Key entry points include src/node/entry.ts (CLI parsing and server startup), src/node/main.ts (server creation), and src/node/app.ts (Express app and WebSocket router setup). The codebase is heavily patched (27+ .diff files) to adapt VS Code for remote use, adding features like base path support, custom marketplace, telemetry, logout, and iframe integration. While the patching approach is fragile and tightly coupled to VS Code's internal APIs, the core server infrastructure and many utility modules are well-architected and reusable.
This repository operates as a static website (remotein.jp) that curates and displays a list of Japanese tech companies offering remote work. The core data source is two markdown tables in README.md (Japanese) and README.en.md (English). A Ruby script (`docs/upsert_data_by_readme.rb`) parses these tables, extracts company details (name, description, full-remote flag), generates Jekyll posts with front-matter and redirects, and produces bilingual search index JSON files. Jekyll builds the site using a custom theme with responsive design, dark mode, JSON-LD structured data for SEO, and client-side search via Simple-Jekyll-Search. The site is deployed via GitHub Pages with CI/CD through GitHub Actions. The architecture is a content pipeline: manual edits to README → script → Jekyll build → static hosting. There is no server-side logic or dynamic API. The repository is primarily a curation and presentation tool, not a software application in the traditional sense, but its automated data ingestion and site generation pipeline demonstrate solid engineering practices.
This repository is a curated list of established remote-first tech companies that hire globally. It is a static markdown file with a table of companies, their tech stacks, compensation indicators, and job links. The list is maintained via pull requests and includes criteria for inclusion (50+ employees, global hiring, tech roles). It serves as a resource for job seekers looking for remote positions. There is no software code, pipelines, or data processing; it is purely a documentation/list project.
This repository is a curated 'awesome list' of resources for remote work, including job boards, articles, books, tools, and companies with remote-friendly cultures. It contains no executable code, APIs, or data pipelines. The entire content is static Markdown files (README.md and translations) organized into categories. The only automated process is a GitHub Actions workflow that checks for broken links in the main README using the awesome_bot gem. The repository serves as a reference directory, not a software application. It is widely starred and forked, indicating community value, but offers no reusable software components or data assets.