- About
- What's included
- Required dependencies
- File structure
- Quick start a new project on t3kit base
- Start with t3kit local development
- Create your custom theme based on t3kit to extend the functionality
- Local development tools
- Changelog
- Documentation
- t3kit Roadmap
- Versioning
- t3kit project structure
- Contributing to t3kit
- Code of Conduct
- Support
- Security Policy
t3kit-starter is a bunch of tools, configs, and best practices which should help you to kickstart new projects on a t3kit basis
- Project folder structure
- Composer configuration
- t3kit and TYPO3 project dependencies
- TYPO3 global configurations
- TYPO3 context configurations
- Custom site configurations
- Local development environment based on Docker
- Starter database
- Tests
- Code guidelines
- Git
- Composer >= v2.1.8
- Docker >= v20.10.8
- Docker Compose >= v2.0.0
- Node.js >= v16.12.0
- NPM >= v8.0.0
- nproxy >= v3.0.0
t3kit-starter/
├── .github/ # github actions
├── .localconf/
│ ├── community/ # community configuration for t3kit, not supported by t3kit team
│ ├── db/ # t3kit database manipulation - Setup/Restore/Pack
│ └── docker/ # t3kit local development config based on Docker
├── config/
└── public/
├── typo3conf/
│ ├── AdditionalConfiguration.php
│ ├── LocalConfiguration.php
│ └── PackageStates.php
└── fileadmin/
We are open to any additional configuration on top of the t3kit. To add it just follow two rules below:
- It always should be inside
.localconf/community/
folder - t3kit team will not support it
If there no needs to use t3kit starter database or Docker configuration for local development, then just delete folder .localconf
from the root of your project rm -r .localconf
-
Start with
composer create-project
composer create-project --no-dev --no-scripts --remove-vcs t3kit/t3kit-starter my-new-project v11.0.0-beta.2
-
Or use as a template in GitHub (recommended). If you are using GitHub to store your future project, then you can just clone t3kit-starter as a template to your new project repository with
Use this template
green button in t3kit organization in the t3kit-starter repository.
-
Check that nginx-proxy started
-
git clone [email protected]:t3kit/t3kit-starter.git
- Clone the repository -
composer env
- Configure local development environment variables*Note: To continue with Docker based local development you need to create an environment
.env
file for your project based on an examplelocal.env
. You can create.env
file by running:composer env
as described above orcp .localconf/local.env .env
.- Check all environment variables in
.env
file and change them if it needed - OS-specific settings in
.env
file- Linux
- Uncomment
USER_ID
var and set up your host user id to make the shared folder writable. (Skip this step if you are a Mac user)
- Uncomment
- Linux
- Check all environment variables in
-
composer i
- Install composer dependencies, or runcomposer ci
if you don't have PHP v8 as your main local environment -
npm install
- Install npm dependencies -
npm run dev
- Build development assests for themes -
docker compose up -d
- Start all Docker services for a local development environment -
Setup t3kit starter database
composer dbup
-
Open
t3kit11.t3.localhost
in browser Google Chrome -
Open TYPO3 BE
t3kit11.t3.localhost/typo3
---> [user:admin
, password:admin1234
] -
Open TYPO3 Install tool
t3kit11.t3.localhost/typo3/install.php
---> [password:admin1234
]
public/typo3conf/ext/theme_newcustomproject
in this folder you can find an example of TYPO3 extension that can be a good starting point for extending the default t3kit theme. With this "subtheme" extension, you can change the design and add the necessary content elements while maintaining the main features of t3kit, and the ability to easily upgrade to newer versions of TYPO3 and t3kit.
-
Define a
name
for your new theme. For example, let's take the namemega
-
Create a new extension based on
theme_newcustomproject
cp -r public/typo3conf/ext/theme_newcustomproject public/typo3conf/ext/theme_mega
Note: Change the
mega
part inpublic/typo3conf/ext/theme_mega
to your real project neme -
Rename
newcustomproject
to your project name. In our example, we are usingmega
as a project name.- Mac
grep -rl 'newcustomproject' public/typo3conf/ext/theme_mega | xargs sed -i '' 's/newcustomproject/mega/g'
- Linux
grep -rl 'newcustomproject' public/typo3conf/ext/theme_mega | xargs sed -i 's/newcustomproject/mega/g'
Note: Change the mega
part in **/ext/theme_mega
and s/newcustomproject/mega/g
to your real project neme
-
Activate
theme_mega
extension- add new repository to root
composer.json
"repositories": [ { "type": "path", "url": "public/typo3conf/ext/theme_mega" } ],
- Install a new
theme_mega
extension
composer co require typo3-local/theme_mega npm install npm run dev
- add new repository to root
-
Enable
theme_mega
for the siteSite Management -> Sites -> Site Theme
- Setup t3kit db:
composer dbup
- Restore t3kit db:
composer dbre
- Pack (save) t3kit db:
composer dbp
docker run --name pma -d -e PMA_ARBITRARY=1 --restart=unless-stopped --network nproxy -p 8083:80 phpmyadmin/phpmyadmin
For all t3kit projects, we need just a one nginx-proxy
started as a separate Docker container. Based on Automated Nginx Reverse Proxy for Docker
git clone [email protected]:t3kit/t3kit-dockerhub.git
cd t3kit-dockerhub/nproxy
docker compose up -d
These platforms are not officially supported by the t3kit team.