WP-NOW: Open browser with blueprint landingPage instead of absoluteUrl

[sejas]

• Related to: The theme directory "twentytwentyfour" does not exist. wordpress-playground#1240

What?

Open blueprint landingPage when defined instead of absoluteUrl.

Why?

It improves the UX of some use cases, for example https://github.com/adamziel/playground-docs-workflow/tree/trunk/wp-content

How?

It adds a new property to WpNowOptions object

Testing Instructions

• Run npx nx run wp-now:build
• Create a blueprint with a landing page:

{
	"landingPage": "/wp-admin/edit.php?post_type=post",
	"features": {
		"networking": true
	},
	"steps": [
		{
			"step": "login",
			"username": "admin",
			"password": "password"
		}
	]
}

• Run node dist/packages/wp-now/cli.js start --blueprint=b.json
• Observe the browser opens the landingPage in wp-admin instead of the homepage.

respect-landing-page.mp4

cc: @flexseth

[flexseth]

• Related to: The theme directory "twentytwentyfour" does not exist. wordpress-playground#1240

Thanks for looking at this @sejas - adding it to the list of items to test out!