The altis-skeleton from humanmade

Visual improvements to base theme placeholder page

Once the logo and other design patterns are established it'll be good to reflect that to some extent in the base theme. This is a placeholder issue - actual tasks and mockups will come later.

Update PHP version in composer.json to 7.4.13

Roles and responsibilities definition

[copied from P2 Post]

Setting expectations and clear definition of responsibilities can make a lot of difference setting the team for success.

As we scale up, it’s important to clarify such expectations, and to balance responsibilities to avoid putting too much on leadership, so we can avoid burn-outs from one-side, but also as important; to avoid the bus factor adding stress to leadership or causing downtime in case of unavailability.

I had a quick workshop with @rob to discuss how can we go about it, we used the draft from Ingenuity’s role narratives document as a starting point. There are some similarities, as product team structure is similar to that of a project, but the scope is definitely bigger with more roles and capacity, and slightly different way of running things, eg: releases.

So we're creating an epic to track different roles in a piecemeal fashion, to distribute and track the efforts efficiently.

The document lives at https://docs.google.com/document/d/1zRvzn5BPTgBe2tSTjTthRospmkLnCBwNfpjEHPRMV4s/edit#heading=h.76b349jdr2hv .

Could not find package altis/skeleton with stability stable.

I was just going through the developer documentation to setup a new Altis project locally and after running composer create-project altis/skeleton altis I received the following error:

[InvalidArgumentException]                                    
  Could not find package altis/skeleton with stability stable.

Add wpackagist by default

Should the WordPress Packagist repo be added to composer.json by default? It makes it easier for users to add dependencies for WordPress plugins (and themes) that aren't on Packagist.

"repositories": [
	{
		"type": "composer",
		"url": "https://wpackagist.org"
	}
]

The skeleton still references local-chassis

Describe the bug
The composer.json file still references altis/local-chassis. It should not

Do we have a way to use beta/nightly build of Altis from skeleton

Before I open a feature request, I like to know if there is a way to setup a skeleton project but use Altis latest nightly build by default?

Enhance Codeception command with configuration options

Codeception command introduced in #242 could use some configuration parameters to customize the default configuration introduced by the zero-config setup, eg:

Allow specifying multiple test directories.
Specifying path to a custom database dump file.
Specifying a custom domain name for the test site.
Specifying a custom default browser.
...

It'd be nice to go through the current generated default config and decide which options can be useful to make available via the Altis config in composer.json.

Use absolute path to theme directory if possible

In Chassis (and IIRC in Local Server) we can access the actual paths on the parent filesystem, so we should use these in the demo theme.

Include .config directory?

Should we include a .config/load.php out of the box to encourage best practices for manual configuration? We can then also include it in the composer.json out of the box.

@joehoyle ?

Engineering roles: Application

Include WordPress Packagist (wpackagist) by default

The documentation on using third-party plugins instructs the developer to add the wpackagist repository to their project so they can add plugins from the WordPress.org plugin directory as dependencies.

I've recently abandoned my johnbillion/query-monitor package on Packagist in favour of wpackagist-plugin/query-monitor on WordPress Packagist, because I need to remove the built CSS and JS files from the source repo on GitHub. Packagist works by fetching the release zip file from GitHub, with no way to override it, which means the built assets will be missing. This is why I'm now recommending to use wpackagist-plugin/query-monitor as that way the complete built plugin gets pulled in as a dependency.

The repositories property in composer.json does not get inherited from dependencies, so it needs to be added in the top level composer.json in order to function. With johnbillion/query-monitor abandoned, altis/dev-tools will need to switch to wpackagist-plugin/query-monitor, which means the top level composer.json needs to use wpackagist by default.

Aside from the above issue, I think it's valuable for developers to have wpackagist included as a repository anyway, as it saves a manual step.

Provide some samples for different kinds of Codeception tests

Spun from https://github.com/humanmade/product-dev/issues/848

It'd be nice to have some sample tests for the different kinds of Codeception tests for developers. And maybe explore some sort of an API reference to all the modules/helpers available in Altis implementation of Codeception ( ie: wp-browser modules, and any custom helpers that Altis introduced ).

Support roles

Add support for ngrok

Fails to remove Elastic packages ( uploaded or manual )

`composer.json` `3.0.0-beta1` tag points to `altis/altis: dev-master`

I noticed on the weekend that the 3.0.0-beta1 packagist tag points to altis/altis: dev-master instead of altis/altis: 3.0.0-beta1

https://packagist.org/packages/altis/skeleton#3.0.0-beta1

Remove backport github action

Not sure how I managed to reintroduce this. I don't actually remember intentionally adding this either which isn't great. It's a mistake at any rate as we're using the app to provide this service instead. The Tibdex action is opinionated with regards to using rebase / squash merges.

Skeleton does not set PHP 8.1 as default

A change to make PHP 8.1 the default got accidentally reverted.

Acceptance criteria

Composer.json must set PHP version to 8.1

Ready

Is the title clear?
Is the description clear and detailed enough?
Are acceptance criteria listed?
Have any (potential) dependencies been identified?
Is an estimate/timebox assigned?
Is a priority label assigned?
Is this ticket added to an epic? (Optional)

humanmade / altis-skeleton Goto Github PK

altis-skeleton's People

Contributors

Stargazers

Watchers

Forkers

altis-skeleton's Issues

Acceptance criteria

Ready

Recommend Projects

Recommend Topics

Recommend Org