Installation

connetation/t3wtk-sitepackage is distributed as a starter template, not a versioned package you keep upgrading. Every project is expected to diverge from it immediately (branding, theme overrides, project-specific forms and SEO wiring), so the intended workflow is clone it once into your new project, then make it your own — not require a fixed version and pull updates forever.

Use it as a starter template (recommended for new projects)

Clone the sitepackage repository into your new project's packages/ directory (the conventional location for project-local, path-based TYPO3 extensions, as opposed to vendor/, which holds Composer-registry packages):
```
git clone https://github.com/connetation/t3wtk-sitepackage.git packages/<your-site-key>
```
Copied!
Then detach it from the template's git history so your project tracks its own history from here on, not the template's:
```
rm -rf packages/<your-site-key>/.git
```
Copied!
Register it as a Composer path repository in your project's root composer.json, and require it by name:
```
{
    "repositories": [
        { "type": "path", "url": "packages/*" }
    ],
    "require": {
        "connetation/t3wtk-sitepackage": "*"
    }
}
```
Copied!
Composer symlinks (or copies, depending on "symlink" setting) path repositories into vendor/, so the extension still loads normally — you're just no longer pulling it from a registry.
(Optional, recommended once you start customizing) Rename it so it's unambiguously this project's sitepackage rather than a generic connetation/t3wtk-sitepackage. This avoids confusion if the same developer ever works on two projects side by side. Update:
- composer.json — name and extra.typo3/cms.extension-key
- ext_emconf.php — title/description
- Configuration/Sets/Sitepackage/config.yaml — the Set name (and every site's dependencies entry that references it)
- PHP namespace Connetation\T3wtkSitepackage in every class under Classes/, in Configuration/Services.yaml, and the autoload.psr-4 entry in composer.json
- The extension key conn_t3wtk_sitepackage referenced in: ext_localconf.php, Configuration/Sets/Sitepackage/setup.typoscript, Configuration/Sets/Sitepackage/settings.definitions.yaml, Configuration/Form/Sitepackage/config.yaml, Configuration/CsSeo/config.yaml, Resources/Private/Forms/Contact.form.yaml, Resources/Private/Language/*.xlf, and Resources/Private/Scss/_theme.scss (comments only)
- Delete Classes/Upgrades/RenameExtensionKeyInFlexFormUpdate.php — it only migrates installations of this package's own older keys
If you'd rather keep the shared name for now and rename later, that's fine too — nothing breaks by leaving it as connetation/t3wtk-sitepackage for a single project.
Activate the Site Set in your TYPO3 site configuration (config/sites/<site>/config.yaml):
```
dependencies:
  - connetation/t3wtk-sitepackage
```
Copied!
connetation/t3wtk-base, connetation/t3wtk-elements, clickstorm/cs-seo and baschte/content-animations are hard requirements of connetation/t3wtk-sitepackage — they're declared in its own composer.json (Composer installs them automatically) and its Set (Configuration/Sets/Sitepackage) declares their Sets (plus typo3/email) as dependencies, so you never need to list them yourself; they load automatically whenever connetation/t3wtk-sitepackage does.

Build the assets and you're set to go:

cd packages/<your-site-key>
npm install
npm run build

Alternative: install a fixed version from a Composer registry

If you specifically want a project to stay centrally updated from a shared upstream sitepackage (uncommon — most projects should fork via the template workflow above), it can also be installed like a normal Composer package from Packagist:

composer require connetation/t3wtk-sitepackage

Classic mode (non-Composer) installations can install the extension conn_t3wtk_sitepackage from the TYPO3 Extension Repository.

Be aware this couples your project to upstream releases of a package whose entire purpose is to hold project-specific customizations — the two tend to conflict as soon as you start editing theme/form/SEO config locally.

First steps on a new project

Whichever install path you used, before going live replace the placeholder values shipped in the reference contact form:

Resources/Private/Forms/Contact.form.yaml — the sender and recipient addresses default to noreply@example.com / contact@example.com, and the confirmation page pageUid defaults to 1. Both are explicitly marked with a TODO (per project) comment in the file — update them for the real project before the form goes live.