Download the PHP package dopamine/flatcms-skeleton without Composer

On this page you can find all versions of the php package dopamine/flatcms-skeleton. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of dopamine/flatcms-skeleton

Informations about the package flatcms-skeleton

Dopamine FlatCMS site

Create a site, start DDEV, and open the panel:

--no-install and --ignore-platform-req=php keep the host PHP out of the picture: DDEV's post-start hook runs composer install inside the container, where PHP 8.4 and all required extensions exist.

The engine lives in vendor/dopamine/flatcms. Site-owned files live here:

A new site opens on its own first-run page — three placeholder components this skeleton copied into theme/components/, a placeholder that says where you are and points at the docs. Replace it: clone the demo theme over theme/, or write your own components here. Once you do, every component on the site is yours outright and there is nothing in vendor/ left to override.

CSS and JS are served as content-hashed bundle files under /assets/ — written on demand, cached forever by the browser, and replaced by a new URL whenever a byte changes, so there is nothing to purge and no build step to run. In the release layout they land in shared/assets/ automatically (derived from VAR_PATH; PUBLIC_ASSETS_PATH overrides); php-fpm must be able to write there. If they cannot be written, every page falls back to inlining its CSS/JS — slower, never broken.

Styling, cheapest first: add rules to theme/assets/css/site.css (emitted last, wins the cascade) → edit the component's own .css, which sits beside its template → change the template. Nothing here receives engine updates, because nothing here comes from the engine.

The <head> is the one exception — it is engine-owned (@flatcms/head.twig) so every site keeps receiving head improvements. Three rules:

Never edit files in vendor/; Composer updates replace them.

Interface strings and languages

Every string the engine shows — the panel, the 404, the contact form's labels and refusals — comes from a catalogue keyed by language. ADMIN_LOCALE picks the panel's; a visitor gets the language of the page they are on.

To reword one of them, or add a string of your own, create lang/<locale>.php here with only the keys you care about:

Your file is merged over the engine's, key by key. Everything you do not mention still resolves from the engine — including keys a later release adds — so there is nothing to keep in sync and no reason to copy the whole catalogue.

A component's own labels need no catalogue at all: an unknown key renders as itself, so label: Επιλέξτε αυτοκίνητο straight in schema.yml just works. Use a key only when the string has to exist in more than one language, and prefix your keys (car.label, not form.car) so a future engine string cannot collide with yours.

A public language is two things, not one: an entry in config.php's locales, and a lang/<locale>.php. With only the first, the pages are translated but the engine's own strings — the send button, validation messages, the 404 — stay English.

bin/doctor reports a catalogue that has fallen behind the source language.

Production requirements

Setup steps for all three are in the engine README's "Cloudflare setup" section (vendor/dopamine/flatcms/README.md).

nginx.conf.example and apache.conf.example in this directory are web server virtual hosts — nothing here reads them. Copy one to the server's config directory (/etc/nginx/sites-available/, /etc/apache2/sites-available/) and edit the certificate path and the php-fpm socket; the domain and deploy root are already filled in. DDEV writes its own vhost, so locally you need neither file.

Run the health check from the site root with:

The bin/ wrappers also expose deploy, rollback, backup, restore drill, form retry, and retention jobs while keeping their implementation in the versioned engine package.

For a private VCS package, add the engine and skeleton repositories to your global or project Composer configuration before running create-project.

All versions of flatcms-skeleton with dependencies

PHP Build Version
Package Version
Requires php Version >=8.4
dopamine/flatcms Version ^3.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package dopamine/flatcms-skeleton contains the following files

Loading the files please wait ...