besteadfast/carbon

Steadfast's starter project - Craft CMS, Vite, and DDEV

carbon's Issues

Set `@webroot` alias so we can clear caches on the CLI

Pull typography styles into Redactor automatically

Check on using Capsize in our typography system

Switch to using ESM for Tailwind & Carbon config file

Currently we're using CJS (CommonJS) for our Tailwind config and carbon config file (currently named stallion.cjs, #48). This is because Tailwind didn't support ESM previously. But in a newer version of Tailwind, ESM is now supported. So, let's upgrade Tailwind and then convert over to ESM.

Show which things are "components" in Figma and whether they are built

Fix issues with starting and stopping projects from the Docker GUI

Currently, if you use the Docker GUI to start/stop projects, they don't unmount correctly (or something) so if you restart your computer they all try to start and everything falls apart (dramatization, but yeah)

What the heck do we do about Buttons? (and other UI components)

Add icons volume by default

One thought on this: we probably need to have the icons volume be automatically re-indexed on deploy, so that new icons that are added via Git appear in the CP automatically without needing to re-index via Utilities

Suggestion: move to Vizy for all rich text needs

We currently use Redactor 🤮 for our Rich Text fields, and Vizy for complex text fields (that need non-text blocks). If we're going to leverage Vizy for most projects, I think it makes sense to build all of our Rich Text fields with it as well.

A couple reasons:

1. The UI is nicer
2. The config is simpler
3. If we need to add blocks in the future, there's no migration needed (this is pretty likely to happen)
4. It means we only have one system for all of our text needs, which makes learning and knowledge retention easier.

Questions:

• Is it harder to extend/build on top of?
• Does the cost matter?

Convert frontend build setup to Vite

Set Site Name and System Name to $APP_NAME

This will allow us to change this in the .env file and avoid having to change it in multiple places.

Auto-register Vue components

TLDR

Components in src/js/components should be auto-registered into Vue, so you don't have to manually import each component.

Spec

• Components in src/js/components and all subfolders will be automatically registered
• Component name will match the filename. Button.vue becomes <Button>
  • Note: this will require the developer to make sure they don't name two components exactly the same, which I'm fine with.
• Lazy loading: If some components aren't required on page-load, we should be able to lazy load them. To lazy load a component, you name the file ComponentName.lazy.vue

This also will take care of #25.

Fix Twigpack port moving around

Lazy (async) load components

Instead of registering them all into the full bundle

Add longer timeout to tokens

Store ENVs in 1Password

Rename things

Rename anything named "stallion" to "carbon".

Example: /config/build/stallion.cjs

Add default "Jump to Content" button

Add mailgun to template or setup

Re-evaluate using #appcss importance for Tailwind utilities

Add aria-expanded and aria-haspopup to expanding menus/accordions

For dropdown menus, accordions, or anything else that opens another section in the DOM should have the aria-haspopup and aria-expanded attributes on them.

These attributes tell screen reader users that another section has opened when interacting with typical DOM nodes. The surgery center repos all have this in their main Nav elements that include a dropdown.

Change initial site group to something more generic like "General" or "Default"

Rename "webpack" volume to "node"

Currently the naming of the Docker volume "webpack" seems a bit odd because I'm usually using it for non-webpack tasks like adding dependencies or running our icon builds. I think "node" makes more sense because we're running node commands in that volume.

Add linter(s)

Include user photo volume by default

Maybe even bake in the steadfast avatar for the default user?

Add checks for typography to make sure all required options are included

Add icon picker to Craft

Need a better way for users to select SVG icons through Craft. Verbb has a plugin for this: https://plugins.craftcms.com/icon-picker?craft4

We could also look at a custom solution, but the plugin is probably the easiest route.

Figure out & document how to pull Nucleo icons

Add SEOmatic & Retour, and their base configs

Component previews + design system

Add interact variant

Use DigitalOcean Spaces for assets

Add a basic mobile nav implementation

Add prettier

Update initial timezone to Eastern

Found in project.yaml file.

Make the docker containers accessible to other devices on the same network

Maybe via https://traefik.me/ ?

Add "edit entry" button to layout

Default Cookie Banner

Figure out when to run `composer install` automatically

We currently have this issue a lot.

Where someone adds a Composer or NPM dependency to the project, and then someone else pulls down their work and is missing that dependency.

This goes hand in hand with the issue of when to pull the database, or apply Project Config changes.

Let's discuss!

Add prod & staging variables for swiff.config file

const prod = {
server: {
// TODO: set server options
}
}

const staging = {
server: {
// TODO: set server options
}
}

Set user usernames to email by default