Problem/Motivation

Its not obvious what we need to do to create a .devpanel folder. There isn't clear documentation, it changes often and there are some quirks that arn't obvious, as well as multiple approaches to doing similar things that are experimental.

Proposed resolution

  • - It would be cool to make an AI Skill for creating the .Devpanel folder, this would mean everyone who is building things for devpanel and drupalforge might find it easier to get started when they are vibe coding generally which will force people to keep this updated (compared to traditional documentation).
  • - This would be a good as a combination of skills, links to official documentation but also some build scripts (for example, maybe we can have scripts that copy ddev configuration and puts it in a devpanel version).
  • - There are some quirks such as init.sh doesn't run everytime the site is restarted in DevPanel. The only one is custom_package_installer.sh, so to get it to install cron and create a crontab we had to put the stuff in there.

Ultimately, I'd like to start with an existing Drupal CMS site, using DDEV and then add this skill, run it and then it will just work with drupalforge and devpanel.

Some of this will be automated scripts though.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

yautja_cetanu created an issue. See original summary.

yautja_cetanu’s picture

Issue summary: View changes