|
|
| Line 1: |
Line 1: |
| {{Under construction|New page to provide details and copy-pastable templates to construct a well-formed Project report page within the Projects section.}} | | {{Under construction|New page to provide details and copy-pastable templates to construct a well-formed Project report page within the Projects section.}} |
|
| |
|
| This page illustrates what makes a thorough page to detail a new project, complete with a copy-pastable template suitable for new pages in the Projects page.
| | ==Goal== |
| | Summarize what the intent of this Project is intended to accomplish. This should include information about an achievable end-goal milestone, rather than an open-ended objective that never ends. (Need to add an example, different than what currently exists in other Projects.) |
|
| |
|
| The top of the page contains the Tenth Fleet Wiki navbar header and the venue header elements. Within the header, you should provide a summary of what the Project is intended to accomplish. Below that is place to list the name of the Project lead. Lastly, the <nowiki></nowiki> tag place the table of contents at the top right edge of the page.
| | ==Scope== |
| | Describe some details regarding what specific aspects are affected by the actions of this Project. (Need to add an example, different than what currently exists in other Projects.) |
|
| |
|
| {{TFW navbar header}}{{Venue header|Orders Project|shortcut=TFW:ORDERS}}
| | ==Method== |
| <div class="tf-board-lead">
| | Describe the method you and/or the team will use to accomplish the Project. You can summarize the entire method/process in a single sentence, which includes the term for each step, then add a 1-2 sentence detail of each step in a list (numbered or unnumbered). (Need to offer, as examples, a few different methods that are commonly used in Projects.) |
| The '''Orders Project''' maintains the ''Tenth Fleet Wiki'' as a complete, verbatim, and searchable record of the organization's directive history – Admiralty Orders, Naval Directives, Bureau of Ships Directives, Fleet Orders, Ship's Orders, and the earliest Tenth Fleet orders – each captured faithfully from its source and enriched with consistent metadata and a standardized lead, ''without ever altering the order text itself''.
| |
|
| |
|
| '''Project lead:''' [[User:MDGarcia|Michael Garcia]] (Lord McCovey Cove).
| | ==Conventions and Rulings== |
| </div>
| | This should provide a summary of newly-encountered issues/hurdles that have presented themselves in the course of completing this Project. Each issue can have it's own bullet point, and should include a summarization of the approach used to achieve success in overcoming that particular hurdle. |
|
| |
|
| | ==Status== |
| | The Project's status should be monitored & maintained periodically (define time frame for periodically: daily, every few days, weekly?) by the Project Lead. |
|
| |
|
| <pre><nowiki>
| | ==Related Projects== |
| {{TFW navbar header}}{{Venue header|Orders Project|shortcut=TFW:ORDERS}}
| | Provide a summary of other Projects that in some way affect the successful completion of this particular Project. Keep in mind, these other Projects have their own lifespan (e.g. Active, Inactive, Completed, or possibly other states not yet considered) and end result. |
| <div class="tf-board-lead">
| |
| <Summary of what the Project is intended to accomplish>
| |
|
| |
|
| '''Project lead:''' [[User:<username>|<first and last name>]] <optional: post-nominal>.
| | ==To Do== |
| </div>
| | This should contain a list of things you know that need to be accomplished within the scope of the project, but have not quite reached that point yet. This is in order to capture notes you may have in your head at that moment, but may forget later. This is also a way to communicate specific tasks or information with others working on this particular Project. Remember, if it's not written down, it doesn't exist! |
| | |
| </nowiki></pre>
| |
| | |
| The next section is to provide details of the intended goal of the Project. (what considerations should be written in this section?)
| |
| | |
| == Goal == | |
| Every directive on record as its own page, that:
| |
| * reproduces the order '''verbatim''' from its source (forum post or attached PDF), never summarized;
| |
| * carries a standardized two-sentence lead identifying the issuing office and summarizing the order, added ''above'' the verbatim text;
| |
| * is tagged with consistent <code><nowiki>{{Order info}}</nowiki></code> metadata (date, issuer, type, status, supersession) for search and cross-referencing.
| |
| | |
| <pre><nowiki>
| |
| == Goal ==
| |
| Every directive on record as its own page, that:
| |
| * reproduces the order '''verbatim''' from its source (forum post or attached PDF), never summarized;
| |
| * carries a standardized two-sentence lead identifying the issuing office and summarizing the order, added ''above'' the verbatim text;
| |
| * is tagged with consistent <code><nowiki>{{Order info}}</nowiki></code> metadata (date, issuer, type, status, supersession) for search and cross-referencing.
| |
| </nowiki></pre>
| |
| | |
| The next section is to provide details of the scope of the Project. (what considerations should be written in this section?)
| |
| | |
| == Scope ==
| |
| All directive types across the organization and its history:
| |
| * '''Admiralty Orders''', '''Naval Directives''', '''Bureau of Ships Directives''', Joint Chiefs and other bureau directives;
| |
| * '''Fleet Orders''' and '''Ship's Orders''' (subordinate to the above);
| |
| * the earliest '''Tenth Fleet orders (2013–2014)''', which predate the forums and were reconstructed from the original member group.
| |
| | |
| <pre><nowiki>
| |
| == Scope ==
| |
| All directive types across the organization and its history:
| |
| * '''Admiralty Orders''', '''Naval Directives''', '''Bureau of Ships Directives''', Joint Chiefs and other bureau directives;
| |
| * '''Fleet Orders''' and '''Ship's Orders''' (subordinate to the above);
| |
| * the earliest '''Tenth Fleet orders (2013–2014)''', which predate the forums and were reconstructed from the original member group.
| |
| </nowiki></pre>
| |
| | |
| The Method section should provide details as to HOW you intend to complete the project.
| |
| | |
| == Method ==
| |
| # '''Capture verbatim.''' Transcribe the order exactly from the source. Newer directives often post a summary blurb with the real order as an attached PDF – extract and reproduce the PDF, not the blurb.
| |
| # '''Add the lead, don't touch the body.''' Prepend the two-sentence lead; the issuer is extrapolated from who held the relevant office on the order's date, the summary is drawn from the order body.
| |
| # '''Tag with metadata.''' Record date, issuer, type, and status in <code><nowiki>{{Order info}}</nowiki></code>. Corrections and context are added as ''new metadata fields'', never by editing the order.
| |
| # '''Mark succession.''' When a later order supersedes an earlier one (a role or command reassigned), set the earlier order's status to ''Superseded'' with a <code>by=</code> pointer – only when a specific superseding order is identified.
| |
| | |
| <pre><nowiki>
| |
| == Method ==
| |
| # '''Capture verbatim.''' Transcribe the order exactly from the source. Newer directives often post a summary blurb with the real order as an attached PDF – extract and reproduce the PDF, not the blurb.
| |
| # '''Add the lead, don't touch the body.''' Prepend the two-sentence lead; the issuer is extrapolated from who held the relevant office on the order's date, the summary is drawn from the order body.
| |
| # '''Tag with metadata.''' Record date, issuer, type, and status in <code><nowiki>{{Order info}}</nowiki></code>. Corrections and context are added as ''new metadata fields'', never by editing the order.
| |
| # '''Mark succession.''' When a later order supersedes an earlier one (a role or command reassigned), set the earlier order's status to ''Superseded'' with a <code>by=</code> pointer – only when a specific superseding order is identified.
| |
| </nowiki></pre>
| |
| | |
| (What considerations for the Conventions and rulings section?)
| |
| | |
| == Conventions and rulings ==
| |
| Decisions adopted for the project, recorded so they are applied consistently:
| |
| * '''The order record is forensic and immutable.''' These pages are used by the [[Bureau of Training|Bureau of Training]] for examinations. '''Order content is never altered''' – not for spelling, not for clarity. All tooling and corrections live in <code><nowiki>{{Order info}}</nowiki></code> fields or the added lead, never in the order text.
| |
| * '''Verbatim, not summarized.''' Content goes in word-for-word. Light formatting (a bold lead sentence, wikilinks, the news template) is allowed; wording is never changed.
| |
| * '''An absent order is not evidence of a change.''' A command, ship, or office only changes when a directive says so – silence in the record proves nothing (this is the same rule the [[TenthFleet:Projects/Ships|Ships]] project relies on).
| |
| * '''Data protection.''' Where a page falls under the wiki's [[TenthFleet:GDPR|data-protection policy]], the command record is preserved while honors lists and rosters are removed; information about children is always redacted. Every redaction cites the policy.
| |
| * '''Link peerages, not people.''' Peerage titles and place-names are wikilinked (markup only, which does not alter the verbatim text); personal names are not.
| |
| | |
| <pre><nowiki>
| |
| == Conventions and rulings ==
| |
| Decisions adopted for the project, recorded so they are applied consistently:
| |
| * '''The order record is forensic and immutable.''' These pages are used by the [[Bureau of Training|Bureau of Training]] for examinations. '''Order content is never altered''' – not for spelling, not for clarity. All tooling and corrections live in <code><nowiki>{{Order info}}</nowiki></code> fields or the added lead, never in the order text.
| |
| * '''Verbatim, not summarized.''' Content goes in word-for-word. Light formatting (a bold lead sentence, wikilinks, the news template) is allowed; wording is never changed.
| |
| * '''An absent order is not evidence of a change.''' A command, ship, or office only changes when a directive says so – silence in the record proves nothing (this is the same rule the [[TenthFleet:Projects/Ships|Ships]] project relies on).
| |
| * '''Data protection.''' Where a page falls under the wiki's [[TenthFleet:GDPR|data-protection policy]], the command record is preserved while honors lists and rosters are removed; information about children is always redacted. Every redaction cites the policy.
| |
| * '''Link peerages, not people.''' Peerage titles and place-names are wikilinked (markup only, which does not alter the verbatim text); personal names are not.
| |
| </nowiki></pre>
| |
| | |
| (How can this become a generic start point in the copy-pastable template?)
| |
| | |
| == Status ==
| |
| {| class="wikitable"
| |
| ! Measure !! Count
| |
| |-
| |
| | Order pages in the [[:Category:Orders|Orders]] namespace || 4,049
| |
| |-
| |
| | [[:Category:BuShips Directives|Bureau of Ships Directives]] || 500
| |
| |-
| |
| | [[:Category:Naval Directives|Naval Directives]] || 247
| |
| |-
| |
| | [[:Category:Admiralty Orders|Admiralty Orders]] || 347
| |
| |}
| |
| An initial batch of order pages that lacked a lead has been brought to the two-sentence standard; roughly 170 single-sentence pages and about a dozen undated pages remain. Supersession tagging and the 2013–2014 backfill are ongoing.
| |
| | |
| <pre><nowiki>
| |
| == Status ==
| |
| {| class="wikitable"
| |
| ! Measure !! Count
| |
| |-
| |
| | Order pages in the [[:Category:Orders|Orders]] namespace || 4,049
| |
| |-
| |
| | [[:Category:BuShips Directives|Bureau of Ships Directives]] || 500
| |
| |-
| |
| | [[:Category:Naval Directives|Naval Directives]] || 247
| |
| |-
| |
| | [[:Category:Admiralty Orders|Admiralty Orders]] || 347
| |
| |}
| |
| An initial batch of order pages that lacked a lead has been brought to the two-sentence standard; roughly 170 single-sentence pages and about a dozen undated pages remain. Supersession tagging and the 2013–2014 backfill are ongoing.
| |
| </nowiki></pre>
| |
| | |
| The Related Projects section should list projects that have some kind of intersectionality.
| |
| | |
| == Related projects ==
| |
| * '''[[TenthFleet:Projects/Ships|Ships]]''' – the two projects meet at [[Bureau of Ships|BuShips]] and the [[:Category:Naval Directives|Naval Directives]]. BuShips Directives establish each hull's commissioning, changes of command, and decommissioning, which drive the ship pages' command histories and their Active/Inactive dispositions; Naval Directives establish fleet, task-group, and echelon assignments. Completing and standardizing the order record here directly improves the accuracy of the ship pages, and gaps found there (unpublished decommissions) surface as citation-needed flags on the affected hulls.
| |
| | |
| <pre><nowiki>
| |
| == Related projects ==
| |
| * '''[[TenthFleet:Projects/Ships|Ships]]''' – the two projects meet at [[Bureau of Ships|BuShips]] and the [[:Category:Naval Directives|Naval Directives]]. BuShips Directives establish each hull's commissioning, changes of command, and decommissioning, which drive the ship pages' command histories and their Active/Inactive dispositions; Naval Directives establish fleet, task-group, and echelon assignments. Completing and standardizing the order record here directly improves the accuracy of the ship pages, and gaps found there (unpublished decommissions) surface as citation-needed flags on the affected hulls.
| |
| </nowiki></pre>
| |
| | |
| The To do list is pretty self-explanatory. This is the space to note which work steps are being worked through.
| |
| | |
| == To do ==
| |
| * Finish the two-sentence lead pass (the remaining single-sentence and undated pages).
| |
| * Continue supersession tagging where a superseding order can be positively identified.
| |
| * Complete the 2013–2014 Tenth Fleet backfill and its year-block index.
| |
| * Reconcile PDF-attachment orders that currently show only the forum summary blurb.
| |
| | |
| <pre><nowiki>
| |
| == To do ==
| |
| * Finish the two-sentence lead pass (the remaining single-sentence and undated pages).
| |
| * Continue supersession tagging where a superseding order can be positively identified.
| |
| * Complete the 2013–2014 Tenth Fleet backfill and its year-block index.
| |
| * Reconcile PDF-attachment orders that currently show only the forum summary blurb.
| |
| </nowiki></pre>
| |
| | |
| The foot of the page is where you should add the Project to the to Category:Projects page with an appropriate sort key (e.g. <nowiki>[[Category:Projects|Ship articles]]</nowiki>)
| |
| | |
| <nowiki>[[Category:Projects|Orders]]</nowiki>
| |
| | |
| <pre><nowiki>
| |
| [[Category:Projects|Ship articles]]
| |
| </nowiki></pre>
| |
| | |
| == Complete Examples ==
| |
| | |
| === Appearance on wiki ===
| |
| Note: This example does not include the <nowiki></nowiki> tag, due to fact-of-life (TOC on page is for the page's TOC at the top right corner.)
| |
| {{TFW navbar header}}{{Venue header|Orders Project|shortcut=TFW:ORDERS}}
| |
| <div class="tf-board-lead">
| |
| The '''Orders Project''' maintains the ''Tenth Fleet Wiki'' as a complete, verbatim, and searchable record of the organization's directive history – Admiralty Orders, Naval Directives, Bureau of Ships Directives, Fleet Orders, Ship's Orders, and the earliest Tenth Fleet orders – each captured faithfully from its source and enriched with consistent metadata and a standardized lead, ''without ever altering the order text itself''.
| |
| | |
| '''Project lead:''' [[User:MDGarcia|Michael Garcia]] (Lord McCovey Cove).
| |
| </div>
| |
| | |
| == Goal ==
| |
| Every directive on record as its own page, that:
| |
| * reproduces the order '''verbatim''' from its source (forum post or attached PDF), never summarized;
| |
| * carries a standardized two-sentence lead identifying the issuing office and summarizing the order, added ''above'' the verbatim text;
| |
| * is tagged with consistent <code><nowiki>{{Order info}}</nowiki></code> metadata (date, issuer, type, status, supersession) for search and cross-referencing.
| |
| | |
| == Scope ==
| |
| All directive types across the organization and its history:
| |
| * '''Admiralty Orders''', '''Naval Directives''', '''Bureau of Ships Directives''', Joint Chiefs and other bureau directives;
| |
| * '''Fleet Orders''' and '''Ship's Orders''' (subordinate to the above);
| |
| * the earliest '''Tenth Fleet orders (2013–2014)''', which predate the forums and were reconstructed from the original member group.
| |
| | |
| == Method ==
| |
| # '''Capture verbatim.''' Transcribe the order exactly from the source. Newer directives often post a summary blurb with the real order as an attached PDF – extract and reproduce the PDF, not the blurb.
| |
| # '''Add the lead, don't touch the body.''' Prepend the two-sentence lead; the issuer is extrapolated from who held the relevant office on the order's date, the summary is drawn from the order body.
| |
| # '''Tag with metadata.''' Record date, issuer, type, and status in <code><nowiki>{{Order info}}</nowiki></code>. Corrections and context are added as ''new metadata fields'', never by editing the order.
| |
| # '''Mark succession.''' When a later order supersedes an earlier one (a role or command reassigned), set the earlier order's status to ''Superseded'' with a <code>by=</code> pointer – only when a specific superseding order is identified.
| |
| | |
| == Conventions and rulings ==
| |
| Decisions adopted for the project, recorded so they are applied consistently:
| |
| * '''The order record is forensic and immutable.''' These pages are used by the [[Bureau of Training|Bureau of Training]] for examinations. '''Order content is never altered''' – not for spelling, not for clarity. All tooling and corrections live in <code><nowiki>{{Order info}}</nowiki></code> fields or the added lead, never in the order text.
| |
| * '''Verbatim, not summarized.''' Content goes in word-for-word. Light formatting (a bold lead sentence, wikilinks, the news template) is allowed; wording is never changed.
| |
| * '''An absent order is not evidence of a change.''' A command, ship, or office only changes when a directive says so – silence in the record proves nothing (this is the same rule the [[TenthFleet:Projects/Ships|Ships]] project relies on).
| |
| * '''Data protection.''' Where a page falls under the wiki's [[TenthFleet:GDPR|data-protection policy]], the command record is preserved while honors lists and rosters are removed; information about children is always redacted. Every redaction cites the policy.
| |
| * '''Link peerages, not people.''' Peerage titles and place-names are wikilinked (markup only, which does not alter the verbatim text); personal names are not.
| |
| | |
| == Status ==
| |
| {| class="wikitable"
| |
| ! Measure !! Count
| |
| |-
| |
| | Order pages in the [[:Category:Orders|Orders]] namespace || 4,049
| |
| |-
| |
| | [[:Category:BuShips Directives|Bureau of Ships Directives]] || 500
| |
| |-
| |
| | [[:Category:Naval Directives|Naval Directives]] || 247
| |
| |-
| |
| | [[:Category:Admiralty Orders|Admiralty Orders]] || 347
| |
| |}
| |
| An initial batch of order pages that lacked a lead has been brought to the two-sentence standard; roughly 170 single-sentence pages and about a dozen undated pages remain. Supersession tagging and the 2013–2014 backfill are ongoing.
| |
| | |
| == Related projects ==
| |
| * '''[[TenthFleet:Projects/Ships|Ships]]''' – the two projects meet at [[Bureau of Ships|BuShips]] and the [[:Category:Naval Directives|Naval Directives]]. BuShips Directives establish each hull's commissioning, changes of command, and decommissioning, which drive the ship pages' command histories and their Active/Inactive dispositions; Naval Directives establish fleet, task-group, and echelon assignments. Completing and standardizing the order record here directly improves the accuracy of the ship pages, and gaps found there (unpublished decommissions) surface as citation-needed flags on the affected hulls.
| |
| | |
| == To do ==
| |
| * Finish the two-sentence lead pass (the remaining single-sentence and undated pages).
| |
| * Continue supersession tagging where a superseding order can be positively identified.
| |
| * Complete the 2013–2014 Tenth Fleet backfill and its year-block index.
| |
| * Reconcile PDF-attachment orders that currently show only the forum summary blurb.
| |
| | |
| === Copy-pastable Template ===
| |
| <pre><nowiki>
| |
| {{TFW navbar header}}{{Venue header|Orders Project|shortcut=TFW:ORDERS}}
| |
| <div class="tf-board-lead">
| |
| The '''Orders Project''' maintains the ''Tenth Fleet Wiki'' as a complete, verbatim, and searchable record of the organization's directive history – Admiralty Orders, Naval Directives, Bureau of Ships Directives, Fleet Orders, Ship's Orders, and the earliest Tenth Fleet orders – each captured faithfully from its source and enriched with consistent metadata and a standardized lead, ''without ever altering the order text itself''.
| |
| | |
| '''Project lead:''' [[User:MDGarcia|Michael Garcia]] (Lord McCovey Cove).
| |
| </div>
| |
| | |
| | |
| == Goal ==
| |
| Every directive on record as its own page, that:
| |
| * reproduces the order '''verbatim''' from its source (forum post or attached PDF), never summarized;
| |
| * carries a standardized two-sentence lead identifying the issuing office and summarizing the order, added ''above'' the verbatim text;
| |
| * is tagged with consistent <code><nowiki>{{Order info}}</nowiki></code> metadata (date, issuer, type, status, supersession) for search and cross-referencing.
| |
| | |
| == Scope ==
| |
| All directive types across the organization and its history:
| |
| * '''Admiralty Orders''', '''Naval Directives''', '''Bureau of Ships Directives''', Joint Chiefs and other bureau directives;
| |
| * '''Fleet Orders''' and '''Ship's Orders''' (subordinate to the above);
| |
| * the earliest '''Tenth Fleet orders (2013–2014)''', which predate the forums and were reconstructed from the original member group.
| |
| | |
| == Method ==
| |
| # '''Capture verbatim.''' Transcribe the order exactly from the source. Newer directives often post a summary blurb with the real order as an attached PDF – extract and reproduce the PDF, not the blurb.
| |
| # '''Add the lead, don't touch the body.''' Prepend the two-sentence lead; the issuer is extrapolated from who held the relevant office on the order's date, the summary is drawn from the order body.
| |
| # '''Tag with metadata.''' Record date, issuer, type, and status in <code><nowiki>{{Order info}}</nowiki></code>. Corrections and context are added as ''new metadata fields'', never by editing the order.
| |
| # '''Mark succession.''' When a later order supersedes an earlier one (a role or command reassigned), set the earlier order's status to ''Superseded'' with a <code>by=</code> pointer – only when a specific superseding order is identified.
| |
| | |
| == Conventions and rulings ==
| |
| Decisions adopted for the project, recorded so they are applied consistently:
| |
| * '''The order record is forensic and immutable.''' These pages are used by the [[Bureau of Training|Bureau of Training]] for examinations. '''Order content is never altered''' – not for spelling, not for clarity. All tooling and corrections live in <code><nowiki>{{Order info}}</nowiki></code> fields or the added lead, never in the order text.
| |
| * '''Verbatim, not summarized.''' Content goes in word-for-word. Light formatting (a bold lead sentence, wikilinks, the news template) is allowed; wording is never changed.
| |
| * '''An absent order is not evidence of a change.''' A command, ship, or office only changes when a directive says so – silence in the record proves nothing (this is the same rule the [[TenthFleet:Projects/Ships|Ships]] project relies on).
| |
| * '''Data protection.''' Where a page falls under the wiki's [[TenthFleet:GDPR|data-protection policy]], the command record is preserved while honors lists and rosters are removed; information about children is always redacted. Every redaction cites the policy.
| |
| * '''Link peerages, not people.''' Peerage titles and place-names are wikilinked (markup only, which does not alter the verbatim text); personal names are not.
| |
| | |
| == Status ==
| |
| {| class="wikitable"
| |
| ! Measure !! Count
| |
| |-
| |
| | Order pages in the [[:Category:Orders|Orders]] namespace || 4,049
| |
| |-
| |
| | [[:Category:BuShips Directives|Bureau of Ships Directives]] || 500
| |
| |-
| |
| | [[:Category:Naval Directives|Naval Directives]] || 247
| |
| |-
| |
| | [[:Category:Admiralty Orders|Admiralty Orders]] || 347
| |
| |}
| |
| An initial batch of order pages that lacked a lead has been brought to the two-sentence standard; roughly 170 single-sentence pages and about a dozen undated pages remain. Supersession tagging and the 2013–2014 backfill are ongoing.
| |
| | |
| == Related projects ==
| |
| * '''[[TenthFleet:Projects/Ships|Ships]]''' – the two projects meet at [[Bureau of Ships|BuShips]] and the [[:Category:Naval Directives|Naval Directives]]. BuShips Directives establish each hull's commissioning, changes of command, and decommissioning, which drive the ship pages' command histories and their Active/Inactive dispositions; Naval Directives establish fleet, task-group, and echelon assignments. Completing and standardizing the order record here directly improves the accuracy of the ship pages, and gaps found there (unpublished decommissions) surface as citation-needed flags on the affected hulls.
| |
| | |
| == To do ==
| |
| * Finish the two-sentence lead pass (the remaining single-sentence and undated pages).
| |
| * Continue supersession tagging where a superseding order can be positively identified.
| |
| * Complete the 2013–2014 Tenth Fleet backfill and its year-block index.
| |
| * Reconcile PDF-attachment orders that currently show only the forum summary blurb.
| |
| | |
| [[Category:Projects|Orders]]
| |
| </nowiki></pre>
| |
🚧 Under constructionThis page is actively being built and is not yet finished. Its layout, dependencies, or wording may be incomplete or change substantially. New page to provide details and copy-pastable templates to construct a well-formed Project report page within the Projects section.It should not be treated as a settled page until this banner is removed.
Goal
Summarize what the intent of this Project is intended to accomplish. This should include information about an achievable end-goal milestone, rather than an open-ended objective that never ends. (Need to add an example, different than what currently exists in other Projects.)
Scope
Describe some details regarding what specific aspects are affected by the actions of this Project. (Need to add an example, different than what currently exists in other Projects.)
Method
Describe the method you and/or the team will use to accomplish the Project. You can summarize the entire method/process in a single sentence, which includes the term for each step, then add a 1-2 sentence detail of each step in a list (numbered or unnumbered). (Need to offer, as examples, a few different methods that are commonly used in Projects.)
Conventions and Rulings
This should provide a summary of newly-encountered issues/hurdles that have presented themselves in the course of completing this Project. Each issue can have it's own bullet point, and should include a summarization of the approach used to achieve success in overcoming that particular hurdle.
Status
The Project's status should be monitored & maintained periodically (define time frame for periodically: daily, every few days, weekly?) by the Project Lead.
Provide a summary of other Projects that in some way affect the successful completion of this particular Project. Keep in mind, these other Projects have their own lifespan (e.g. Active, Inactive, Completed, or possibly other states not yet considered) and end result.
To Do
This should contain a list of things you know that need to be accomplished within the scope of the project, but have not quite reached that point yet. This is in order to capture notes you may have in your head at that moment, but may forget later. This is also a way to communicate specific tasks or information with others working on this particular Project. Remember, if it's not written down, it doesn't exist!