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

<?php
namespace WordPressDotOrg\FiveForTheFuture\View;

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

<div class="form-field">
	<label for="5ftf-pledge-contributors">
		<?php esc_html_e( 'Contributor Usernames', 'wordpressorg' ); ?>
	</label>
	<input
		type="text"
		id="5ftf-pledge-contributors"
		name="pledge-contributors"
		value="<?php echo esc_attr( $data['pledge-contributors'] ); ?>"
		required
		aria-describedby="5ftf-pledge-contributors-help"
	/>
	<p id="5ftf-pledge-contributors-help">
		<?php esc_html_e( 'Separate each WordPress.org username with a comma.', 'wordpressorg' ); ?>
	</p>
</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;`

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 array $data */`
			`/** @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			`?>`

			`<div class="form-field">`
			`<label for="5ftf-pledge-contributors">`
Pledge Form: Clarify that we're asking for WordPress.org usernames. 2019-10-25 17:57:33 +03:00			`<?php esc_html_e( 'Contributor Usernames', 'wordpressorg' ); ?>`
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>`
			`<input`
			`type="text"`
			`id="5ftf-pledge-contributors"`
Add a Contributor custom post type (#42) Contributors associated with pledges have a state: they can be confirmed or unconfirmed. They also have some important meta data, namely when they were confirmed. Thus, managing contributor data for pledges is more robust if we treat them as their own post type instead of as a multidimensional array of post meta data. This also reorganizes some of the functions related to pledges so that things are more consistent between the pledge CPT and the contributior CPT. Fixes #11 2019-10-22 01:43:20 +03:00			`name="pledge-contributors"`
			`value="<?php echo esc_attr( $data['pledge-contributors'] ); ?>"`
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`
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			`aria-describedby="5ftf-pledge-contributors-help"`
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			`<p id="5ftf-pledge-contributors-help">`
Pledge Form: Clarify that we're asking for WordPress.org usernames. 2019-10-25 17:57:33 +03:00			`<?php esc_html_e( 'Separate each WordPress.org username with a comma.', 'wordpressorg' ); ?>`
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			`</p>`
			`</div>`