This is a comprehensive Cookiecutter template for generating production-ready Python projects. It is not a running application itself but a project generator that produces applications, libraries, or services based on user-selected features. The template includes sophisticated post-generation hooks that surgically remove unused files and configure dependencies, Docker Compose services, CI/CD workflows, and documentation based on the chosen options. It enforces modern Python practices: uv for package management, Ruff for linting/formatting, mypy for type checking, pytest for testing, and Pydantic Settings for configuration. The generated projects can include FastAPI, Celery, SQLAlchemy, QuasiQueue, aiocache, Jinja2, Typer CLI, Docker, and GitHub Actions. The template itself demonstrates high craftsmanship with clean Jinja2 templating, conditional logic, and a well-organized file structure. It is actively maintained and uses current tooling (uv, Ruff, etc.), indicating low technical drift.
Cookiecutter Data Science (CCDS) is a CLI tool that generates standardized, opinionated project scaffolds for data science work. It wraps the cookiecutter templating engine with custom prompting logic that supports nested configuration choices (e.g., cloud storage options with sub-fields for bucket names), and post-generation hooks that dynamically write dependency files in multiple formats (requirements.txt, pyproject.toml, environment.yml, Pipfile, pixi.toml), configure linting/formatting tools (ruff or flake8+black+isort), set up testing frameworks (pytest/unittest), and scaffold code modules with boilerplate for data processing, feature engineering, modeling, and visualization. The tool is designed to be run via the `ccds` command, which defaults to the DrivenData template repository and the installed version of the template. The codebase demonstrates solid software engineering: it monkey-patches cookiecutter's internals in a controlled way to add functionality (prompting with sub-options, custom context file selection), provides a suite of reusable hook utilities for dependency management and custom config injection, and maintains extensive test coverage across multiple operating systems and environment managers (conda, virtualenv, pipenv, uv, pixi, poetry). The architecture is a thin CLI application that delegates to cookiecutter while extending it through monkey-patching and post-generation hooks. It is not a data research project itself but a tool for creating such projects.
This repository is the official Composer project template for bootstrapping new Sulu CMS applications. It is not a standalone CMS but a pre-configured Symfony 7.4 application skeleton that wires together the Sulu 3.0 bundles (admin, media, security, page, search, article, snippet, etc.) with Doctrine ORM, MySQL, Twig, Messenger, Flysystem, and a React-based admin SPA built via Webpack. The application exposes two runtime contexts through a single kernel: an admin backend under /admin with a JSON API and a website frontend serving Twig templates. Entry points are public/index.php for web requests and bin/console, bin/adminconsole, bin/websiteconsole for CLI operations. The template includes production-oriented infrastructure: HTTP cache layer via SuluHttpCache, FOSHttpCache for proxy caching, 2FA via scheb/2fa, search via CMSIG Seal with Loupe adapter, media handling, and a maintenance mode script that works without framework dependencies. The composer.json defines an extensive lint/test pipeline (PHPStan level max, PHP-CS-Fixer, Rector, Twig CS Fixer, container validation, Doctrine schema validation) and the GitHub Actions workflow tests the template across PHP 8.2-8.5, MySQL 5.7-8.4, and Node.js 20-24, including a create-project test that verifies the template can bootstrap a new project. Because this is a skeleton, the actual application code is minimal (a Kernel class, empty fixtures, and basic Twig templates). Its value lies in the configuration and integration of the Sulu ecosystem, serving as a starting point for multi-lingual, multi-portal CMS websites. The repository is actively maintained with recent commits and a comprehensive CI pipeline.
The Filecoin Community repository serves as a central hub for community documentation, project showcases, and governance. It contains markdown files detailing community processes, calls, polls, and working group activities. The projects directory showcases applications and tools built by the community on Filecoin. The repository provides standardized templates for project submissions, meeting agendas, and notes, facilitating consistent community engagement. While it lacks executable code, it effectively coordinates the Filecoin ecosystem through structured documentation and resource sharing.
This repository is a documentation-only project that describes a conventional directory layout for Go applications. It contains no executable source code, no tests, no CI/CD pipelines, and no functional software of any kind. The entire repository consists of README files (translated into ~20 languages), a placeholder go.mod with a dummy module path, a nearly empty Makefile, and .keep files in empty directories. The go.mod references go 1.19 and contains no dependencies. There are no Go source files anywhere in the repository. The project serves purely as a reference template showing recommended directory structures (cmd/, internal/, pkg/, api/, web/, configs/, scripts/, build/, deployments/, test/, docs/, tools/, examples/, third_party/, githooks/, assets/, website/, init/) for Go projects, with links to real-world examples that follow these conventions. The last commit was in April 2026 but there is essentially nothing to maintain — the content is static documentation that has remained unchanged in substance for years. The README itself acknowledges this is not an official Go team standard but a community-driven collection of common patterns.