five-for-the-future/plugins/wporg-5ftf/views/inputs-pledge-new-misc.php

<?php
namespace WordPressDotOrg\FiveForTheFuture\View;

/** @var array $data */
/** @var bool  $readonly */
?>

<div class="form-field form-field__agree">
	<input
		type="checkbox"
		id="5ftf-pledge-agreement"
		name="pledge-agreement"
		required
		<?php checked( $data['pledge-agreement'] ); ?>
	/>
	<label for="5ftf-pledge-agreement">
		<?php
		printf(
			wp_kses_post( __( 'I understand and agree to the <a href="%s">expectations for inclusion</a> in the Five for the Future acknowledgement program.', 'wporg-5ftf' ) ),
			esc_url( get_permalink( get_page_by_path( 'expectations' ) ) ) // TODO Change this URL?
		);
		?>
	</label>
</div>
Plugin: Refactor to use as foundation for planned pledge workflows (#23) This starts to address several items in the roadmap, but probably doesn't fully address any of them. It takes the plugin code that was written several months ago, before the scope of this project was fully sorted out, and refactors it to be a starting point for the roadmap. * Adds template files for form inputs that can be used to both create new pledges and manage existing pledges * Does some validation and sanitization work on form submissions * Adds a custom post status for deactivated pledges 2019-10-04 22:35:02 +03:00			`<?php`
			`namespace WordPressDotOrg\FiveForTheFuture\View;`

			`/** @var array $data */`
Create Pledge: Make form functional (#31) This broadly enables & styles the pledge forms across the frontend and wp-admin. - Switches field `readonly` control to a variable called `$readonly` - Create `PledgeMeta\get_pledge_meta()` which will fetch data from `$_POST`, a pledge post, or defaults. - Add Number of Employees field - Update form content to match mockup: - fields now have help text - success message uses content from mockup - logo field is moved to the "org info" section - Style form in theme, add some similar styles to the admin Fixes #7, fixes #28 2019-10-09 01:29:35 +03:00			`/** @var bool $readonly */`
Plugin: Refactor to use as foundation for planned pledge workflows (#23) This starts to address several items in the roadmap, but probably doesn't fully address any of them. It takes the plugin code that was written several months ago, before the scope of this project was fully sorted out, and refactors it to be a starting point for the roadmap. * Adds template files for form inputs that can be used to both create new pledges and manage existing pledges * Does some validation and sanitization work on form submissions * Adds a custom post status for deactivated pledges 2019-10-04 22:35:02 +03:00			`?>`

Create Pledge: Make form functional (#31) This broadly enables & styles the pledge forms across the frontend and wp-admin. - Switches field `readonly` control to a variable called `$readonly` - Create `PledgeMeta\get_pledge_meta()` which will fetch data from `$_POST`, a pledge post, or defaults. - Add Number of Employees field - Update form content to match mockup: - fields now have help text - success message uses content from mockup - logo field is moved to the "org info" section - Style form in theme, add some similar styles to the admin Fixes #7, fixes #28 2019-10-09 01:29:35 +03:00			`<div class="form-field form-field__agree">`
Plugin: Refactor to use as foundation for planned pledge workflows (#23) This starts to address several items in the roadmap, but probably doesn't fully address any of them. It takes the plugin code that was written several months ago, before the scope of this project was fully sorted out, and refactors it to be a starting point for the roadmap. * Adds template files for form inputs that can be used to both create new pledges and manage existing pledges * Does some validation and sanitization work on form submissions * Adds a custom post status for deactivated pledges 2019-10-04 22:35:02 +03:00			`<input`
			`type="checkbox"`
New Pledge: Validate submitted form values and generate a draft pledge post (#35) Ensures that a submission to the new pledge form has: * A unique email address compared to existing pledges * A unique domain in the URL, compared to existing pledges * Has at least one valid contributor listed Error messages when one or more of these conditions isn't met are descriptive so that the submitter can correct the issue. Fixes #15 2019-10-19 02:56:21 +03:00			`id="5ftf-pledge-agreement"`
			`name="pledge-agreement"`
Plugin: Refactor to use as foundation for planned pledge workflows (#23) This starts to address several items in the roadmap, but probably doesn't fully address any of them. It takes the plugin code that was written several months ago, before the scope of this project was fully sorted out, and refactors it to be a starting point for the roadmap. * Adds template files for form inputs that can be used to both create new pledges and manage existing pledges * Does some validation and sanitization work on form submissions * Adds a custom post status for deactivated pledges 2019-10-04 22:35:02 +03:00			`required`
New Pledge: Validate submitted form values and generate a draft pledge post (#35) Ensures that a submission to the new pledge form has: * A unique email address compared to existing pledges * A unique domain in the URL, compared to existing pledges * Has at least one valid contributor listed Error messages when one or more of these conditions isn't met are descriptive so that the submitter can correct the issue. Fixes #15 2019-10-19 02:56:21 +03:00			`<?php checked( $data['pledge-agreement'] ); ?>`
Plugin: Refactor to use as foundation for planned pledge workflows (#23) This starts to address several items in the roadmap, but probably doesn't fully address any of them. It takes the plugin code that was written several months ago, before the scope of this project was fully sorted out, and refactors it to be a starting point for the roadmap. * Adds template files for form inputs that can be used to both create new pledges and manage existing pledges * Does some validation and sanitization work on form submissions * Adds a custom post status for deactivated pledges 2019-10-04 22:35:02 +03:00			`/>`
New Pledge: Validate submitted form values and generate a draft pledge post (#35) Ensures that a submission to the new pledge form has: * A unique email address compared to existing pledges * A unique domain in the URL, compared to existing pledges * Has at least one valid contributor listed Error messages when one or more of these conditions isn't met are descriptive so that the submitter can correct the issue. Fixes #15 2019-10-19 02:56:21 +03:00			`<label for="5ftf-pledge-agreement">`
Pledge Form: Use agreement text as label content This calls more attention to the agreement text, and correctly associates it with the input for screen reader users. 2019-10-29 02:09:38 +02:00			`<?php`
			`printf(`
Pledge Form: Use slightly more screen reader friendly link text 2019-10-29 02:10:53 +02:00			`wp_kses_post( __( 'I understand and agree to the <a href="%s">expectations for inclusion</a> in the Five for the Future acknowledgement program.', 'wporg-5ftf' ) ),`
Pledge Form: Use agreement text as label content This calls more attention to the agreement text, and correctly associates it with the input for screen reader users. 2019-10-29 02:09:38 +02:00			`esc_url( get_permalink( get_page_by_path( 'expectations' ) ) ) // TODO Change this URL?`
			`);`
			`?>`
Plugin: Refactor to use as foundation for planned pledge workflows (#23) This starts to address several items in the roadmap, but probably doesn't fully address any of them. It takes the plugin code that was written several months ago, before the scope of this project was fully sorted out, and refactors it to be a starting point for the roadmap. * Adds template files for form inputs that can be used to both create new pledges and manage existing pledges * Does some validation and sanitization work on form submissions * Adds a custom post status for deactivated pledges 2019-10-04 22:35:02 +03:00			`</label>`
			`</div>`