Problem/Motivation

Webships has no site template of its own. The Webships Starter project is empty, so the installer has nothing to offer as its default choice, and the site parts still live in the profile.

Proposed resolution

Build the site template on a new 1.0.x branch, as a standalone recipe of type Site, and make it the default choice of the Webships installer.

  • A web apps gallery with organizations, served through a documented API.
  • JSON:API served from /api, and read-only. Write operations stay a decision for the site owner.
  • OAuth 2.0 with consumers, HTTP Basic authentication, and the OpenAPI documents rendered with Swagger UI at /api-docs.
  • The Drupal core administration theme is the default theme, for the back end and the front end.
  • Search and views for browsing the gallery. Registration is closed: an administrator creates the accounts.

The site template is standalone: it never requires or applies another site template. Only packages from drupal.org.

Remaining tasks

  • ✅ Build the site template on 1.0.x
  • ❌ Move the apps and organizations content model out of the profile and into this recipe, so the profile can become an installer that only lists site templates
  • ❌ Review the merge request
  • ❌ Release 1.0.0

Release notes snippet

Webships Starter 1.0.0: the default Webships site template, a web apps gallery served through a documented API.

AI-Generated: Yes

Comments

rajab natshah created an issue.

  • rajab natshah committed 813f06e5 on 3624372-site-template
    fix: #3624372 Validate the recipe without an inline PHP script

  • rajab natshah committed bfe9f590 on 1.0.x
    feat: #3624372 Build the Webships Starter site template on 1.0.x