simai / docara
Simple static sites with Laravel's Blade. based on tightenco/jigsaw
Installs: 177
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 0
Forks: 0
Open Issues: 0
pkg:composer/simai/docara
Requires
- php: ^8.2
- elaborate-code/jigsaw-localization: ^1.1
- illuminate/collections: ^11.0 || ^12.0
- illuminate/console: ^11.0 || ^12.0
- illuminate/container: ^11.0 || ^12.0
- illuminate/filesystem: ^11.0 || ^12.0
- illuminate/support: ^11.0 || ^12.0
- illuminate/view: ^11.0 || ^12.0
- league/commonmark: ^2.4
- michelf/php-markdown: ^2.0
- mnapoli/front-yaml: ^2.0
- nunomaduro/collision: ^8.1
- ramsey/uuid: ^4.9
- samdark/sitemap: ^2.4.1
- spatie/laravel-ignition: ^2.4
- symfony/console: ^6.0 || ^7.0
- symfony/error-handler: ^6.0 || ^7.0
- symfony/finder: ^6.0 || ^7.0
- symfony/intl: ^7.3
- symfony/process: ^6.0 || ^7.0
- symfony/var-dumper: ^6.0 || ^7.0
- symfony/yaml: ^6.0 || ^7.0
- vlucas/phpdotenv: ^5.6
Requires (Dev)
- laravel/pint: ^1.16
- mockery/mockery: ^1.6
- phpunit/phpunit: ^11.0.6
- dev-main
- v1.1.12
- v1.1.11
- v1.1.10
- v1.1.9
- v1.1.8
- v1.1.7
- v1.1.6
- v1.1.5
- v1.1.4
- v1.1.3
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.42
- v1.0.41
- v1.0.40
- v1.0.39
- v1.0.38
- v1.0.37
- v1.0.36
- v1.0.35
- v1.0.34
- v1.0.33
- v1.0.32
- v1.0.31
- v1.0.30
- v1.0.29
- v1.0.28
- v1.0.27
- v1.0.26
- v1.0.25
- v1.0.24
- v1.0.23
- v1.0.22
- v1.0.21
- v1.0.20
- v1.0.19
- v1.0.18
- v1.0.17
- v1.0.16
- v1.0.15
- v1.0.14
- v1.0.13
- v1.0.12
- v1.0.11
- v1.0.10
- v1.0.9
- v1.0.8
- v1.0.7
- v1.0.6
- v1.0.5
- v1.0.4
- v1.0.3
- v1.0.2
- v1.0.1
- v1.0.0
This package is auto-updated.
Last update: 2025-12-25 07:53:48 UTC
README
Quick start to install Docara via Composer and initialize a project.
Install the framework
composer require simai/docara
Configure .env
Create .env in your project root (example):
AZURE_KEY=<AZURE_KEY>
AZURE_REGION=<AZURE_REGION>
AZURE_ENDPOINT=https://api.cognitive.microsofttranslator.com
DOCS_DIR=docs
Initialize a new project
From an empty project directory:
php vendor/bin/docara init
This will:
- copy the base template (stubs),
- copy bundled
source/_core, - copy template configs from
_core, - run frontend dependency install (
npm/yarn installin the project root). - If you changed files in
source/_core, init/update will detect your edits (whitespace-insensitive) and leave those files untouched.
Run
- Development/watch (if defined in your template):
yarn run watchornpm run watch - Build:
yarn run prod/npm run prod(or your template’s build script) - Translate test:
php vendor/bin/docara translate --test - Update existing project in-place (no delete/archive, keeps
source/_core):php vendor/bin/docara init --update - If you already have your own docs in
source/docs, they won’t be overwritten; otherwise stubs/docs are copied. - If you already have
config.phpin the project root, it will be preserved during init/update.
CLI commands
php vendor/bin/docara init [--update] [--force-core-configs] [--force-core-files] [preset]
Initializes or updates the project.--force-core-configsoverwrites template configs from_coreeven if you changed them (by default changed files are skipped).--force-core-filesoverwrites the entire_coretree from stubs (ignoring your edits), but files that are already tracked in your git repo are never overwritten, even with this flag.php vendor/bin/docara build [env]— build the site for the given environment.php vendor/bin/docara translate [--test]— translate docs (requires AZURE_*),--testfor a dry run.
Structure
source/— your site source.source/_core/— Docara/Jigsaw core (bundled and copied on init).stubs/— template stubs used duringdocara init.build_*— build outputs.
Lint
- PHP:
vendor/bin/pint --test - Markdown:
npx markdownlint-cli2 "**/*.md" "!vendor" "!node_modules" "!build_*" "!dist" "!public"
Customize the logo
- Replace the SVG at
source/_core/_assets/img/logo.svg(and, if you use the wide mark,source/_core/_assets/img/icon_and_text_logo.svg) with your own asset. - If you prefer a different markup (e.g., PNG, text), edit
source/_core/_components/header/logo.blade.php; it is now a regular file in your repo, not a submodule. - Rebuild assets (
yarn prod/npm run prodor your preset’s build) so the new logo is emitted toassets/build. - Commit/push as usual—
source/_coreis just files, so the logo change lives in your repository.
License
MIT