• PHP tests via Pest + Craft Pest

Description

• Add tailwind forms to base setup https://github.com/tailwindlabs/tailwindcss-typography

• Change sr-only to skip-link and update the styling to something basic

.skip-link {
    @apply absolute left-0 p-4 text-white bg-black -top-16;
    z-index: 100;

    &:focus {
      @apply top-0 outline-none outline-blue-500;
    }
  }

• Git hooks
• PHP
  • ECS
  • PHPstan
• FE
  • Prettier
  • eslint

Describe the solution you'd like

Appropriate issue templates for the different types of issue we encounter during specification and build

https://github.com/craftcms/generator/

• TW
• webpack mix

Tom to refine this Issue with direction for Jasmine.

From a Slack chat:

it would be really helpful to have an HTML sampler template in Craft, with html for all the things we always need (buttons, prose etc)

would then help to validate the TW config against that

kinda like the styleguide pages I built for Relias but TW driven, and with fewer code examples b/c we have the TW docs

We end up building the same thing again and again:

• Pages structure
• Blog
• Promos
• Testimonials
• Asset volumes for Images + Files

etc etc

We should have a long-lived branch with project config + skeleton templating for this stuff

We shouldn't be able to excuse not writing tests because there is no harness set up...

Must have

• Javascript unit tests - (use https://vitest.dev/ ?)
• GH actions for running tests

Could have

• Visual regression testing via https://percy.io/ + GH actions

https://craftcms.com/docs/4.x/config/app.html#mailer

<?php
# config/app.php
use craft\helpers\App;

$isDev = App::env('CRAFT_ENVIRONMENT') === 'dev';
$useMailhog = Craft::$app->getConfig()->getGeneral()->devMode;

return [
    'components' => [
        'mailer' => function() {
            // Get the default component config:
            $config = App::mailerConfig();

            if ($useMailhog) {
                $adapter = craft\helpers\MailerHelper::createTransportAdapter(
                    craft\mail\transportadapters\Smtp::class,
                    [
                        'host' => App::env('MAILHOG_HOST'),
                        'port' => App::env('MAILHOG_PORT'),
                    ]
                );

                // Override the transport:
                $config['transport'] = $adapter->defineTransport();
            }

            // Return the initialized component:
            return Craft::createObject($config);
        },
    ],
];

• minimal
• secure
• encourage best practice

• Once zaengle/base-eslint-configuration#4 is complete
• Add that config as a dependency and consume it as a preset in .eslintrc

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Is an estimate required before development starts?

Is a visual design required? If so has it been approved and provided?

Additional context
Add any other context or screenshots about the feature request here.

• Default
• Content model
• FE UI component
• Template integration
• Custom PHP / business logic
• Config / env changes

Mix is dead, long live Vite!

Must support:

• TW + postcss + autoprefixer
• JS builds
• SVG sprites
• Live reload

Should support:

• Lint all the things!
• @ alias for src/assets/js

See also #15