CAPipedia Sandbox - User contributions [en]

Main Page

2025-12-23T03:14:33Z

NMcLarty27:

{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

'''TIPS:''' Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.

Search is case-insensitive. The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

'''Search Examples:''' How do I change my password? Use ''"change password"'' in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

Main Page

2025-12-23T02:00:23Z

NMcLarty27:

{{Colored box
| title=Notice
| title-color=#fff
| background-title-color=#ff0000
| background-content-color=#ffcccc
| center=true
| content=
'''Due to ongoing malicious activity impacting {{SITENAME}} performance, only the main page is publicly viewable. In order to access any other content, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account.'''
}}
{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

'''TIPS:''' Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.

Search is case-insensitive. The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

'''Search Examples:''' How do I change my password? Use ''"change password"'' in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

Main Page

2025-08-10T17:25:13Z

NMcLarty27:

Main Page

2025-08-10T17:24:02Z

NMcLarty27:

{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

'''TIPS:''' Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

Category talk:CAP Knowledgebase cleanup

2025-05-21T21:29:53Z

NMcLarty27:

Things to look for in cleaning up the [[:Category:CAP Knowledgebase cleanup|FAQ pages that have been brought over from the CAP Knowledgebase]]:

* Is the question/answer in the correct FAQ page (e.g., flight operations goes in [[Flight Operations FAQ]], emergency services goes in [[Emergency Services FAQ]])
* Is the answer still current and relevant for CAP today
* Does the answer cite official guidance (e.g., regulations, standards, pamphlets) that is valid today
* Are there multiple questions/answers that are similar and could be consolidated into a single question/answer

Things to do while cleaning up FAQ pages:

* Remove double quotations ("") that were brought in during the import
* Remove excerpts of CAP publications from the body of the FAQ answer and replace with a link to the publication (use the template below) and reference to the section. Summarization or context of the publication's content is acceptable, but may increase future workload if publication changes affect the answer.
* Consolidate and/or remove similar or duplicate questions/answers
* Simplify the question to one sentence wherever possible; remove scenario examples that make the question extensive
* Replace links to and references of CAP publications with the template (These will hyperlink to the current CAP publications/forms website and future-proof any changes to the CAP website. In the future, this may hyperlink directly to the current copy of the publication/form):

[[Template:Pub/doc|<nowiki>{{Pub|<insert publication number, with a | between CAPP/CAPR/CAPS/CAPVA and the number>}}</nowiki>]], such as <nowiki>{{Pub|CAPR|10-1}}</nowiki>

or

[[Template:Form/doc|<nowiki>{{Form|<insert form number, with a | between CAPF and the number}}</nowiki>]], such as <nowiki>{{Form|CAPF|2}}</nowiki>

Once a page has been completely reviewed and all information is current and accurate, please remove the {{code | <nowiki>{{CAP Knowledgebase only}}</nowiki>}} template slug from the top of the page.

CAPipedia Sandbox:Updating CAPipedia

2025-05-21T16:15:41Z

NMcLarty27: /* Update local-attributes.sh */

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>sh load-database.sh [new_db_name] [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Update local-attributes.sh ==

# Edit the <code>local-attributes.sh</code> file and change the <code>PROD_DIR</code> to '''capipedia-[new_version]''' and <code>PROD_DB_NAME</code> to the new version's database name

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

Template:Pub

2025-05-21T16:11:05Z

NMcLarty27: Protected "Template:Pub" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

[{{#switch: {{{1}}}
| CAPM = https://www.gocivilairpatrol.com/members/publications/indexes-regulations-and-manuals-1700#:~:text=M{{#invoke:String|replace|{{{2}}}|-|%2D}}
| CAPP = https://www.gocivilairpatrol.com/members/publications/pamphlets-1702#:~:text=P{{#invoke:String|replace|{{{2}}}|-|%2D}}
| CAPR = https://www.gocivilairpatrol.com/members/publications/indexes-regulations-and-manuals-1700#:~:text=R{{#invoke:String|replace|{{{2}}}|-|%2D}}
| CAPS = https://www.gocivilairpatrol.com/members/publications/standards#:~:text=S{{#invoke:String|replace|{{{2}}}|-|%2D}}
| CAPVA = https://www.gocivilairpatrol.com/members/publications/visual-aids#:~:text=VA{{#invoke:String|replace|{{{2}}}|-|%2D}}
| AFH = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| AFI = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| AFMAN = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| AFPAM = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| DAFH = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| DAFI = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| DAFMAN = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| DAFPAM = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
}} {{{1}}} {{{2}}}]

Template:Form

2025-05-21T16:10:51Z

NMcLarty27: Protected "Template:Form" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

[{{#switch: {{{1}}}
| CAPF = https://www.gocivilairpatrol.com/members/publications/forms#:~:text=F{{#invoke:String|replace|{{{2}}}|-|%2D}}
| AF = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| DAF = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| FAA = https://www.faa.gov/forms/index.cfm/go/document.list/?q={{{2}}}
| ICS = https://training.fema.gov/icsresource/icsforms.aspx#:~:text=ICS%20Form%20{{{2}}}
}} {{{1}}} {{#switch: {{{1}}} | AF = Form | DAF = Form | FAA = Form | ICS = Form}} {{{2}}}]

Emergency Services FAQ

2025-05-21T16:09:20Z

NMcLarty27: /* General questions */

{{CAP Knowledgebase only|date=January 2024}}

== General questions ==

=== Where can I find information about General Emergency Services Tasks? ===

You can find General Emergency Services training materials and links online at: Training Material{{dead link}}

=== How do I complete my General Emergency Services (GES) qualification? ===

2-3. Specialty Rating Requirements and Performance Standards. For each specialty rating, SQTRs have been developed to train and qualify members in stages. The most current versions of the task guides for all specialties are found on the NHQ CAP/DOS website.

e. General Emergency Services (GES). To participate in emergency services training or operations, personnel must be current traditional members (not patrons, cadet sponsors, AEMs, or legislative members) having completed level one and cadet protection training (senior members) or achievement one (cadets). Individuals in temporary membership are not eligible for liability coverage under the FECA or FTCA. Individuals in temporary membership status are eligible to accomplish academic training activities, but are not authorized to observe mission base training and operations due to liability issues. In addition, they may not participate in any flight activities (including flight line activities) or ground, urban direction finding team, or CERT field activities. Other than these, there are no prerequisite requirements for GES. The General Emergency Services specialty rating is required of all individuals qualifying in emergency services and will be completed prior to commencing training for any other specialty. This training authorizes members to attend missions, observe activities and perform administrative and general operations support tasks under the direction of qualified staff personnel, essentially as a license to learn. Successful completion of the current CAPT 116, General Emergency Services Questionnaire and OPSEC Training, qualifies the member in the General Emergency Services Specialty Rating. To remain current in the GES specialty all current holders will complete new CAPTs 116 and OPSEC Training within 180 days of issuance of new examinations.

=== Where can I find the ICS activity log? ===

The ICS Activity Log is available here: {{Form|ICS|214}}

=== Can a member who is a Skills Examiner Trainer (SET) sign their off a task on a his/her own SQTR for a new ES rating. For example, John Doe is SET qualified as MRO, MSA. He is not MS qualified. Can he sign off tasks for MS on his own SQTR? ===

No, a member cannot sign off tasks for themselves. A separate qualified supervisor needs to evaluate the task.

=== What operations and emergency services examinations are available online? ===

OPS and ES quizzes and exams are stored in the Learning Management System (LMS) in eSevices.

=== How do you get certificates from FEMA and IS courses to prove course completion for a civilian job? ===

The Federal Emergency Management Agency has a online course to help first responders understand the federal government's National Incident Management System (NIMS). NIMS establishes standard incident management processes, protocols and procedures so that all responders — including those at the federal, state, tribal and local level — can coordinate their responses, share a common focus and place full emphasis on resolving the event.

You can request certificates from FEMA at: https://training.fema.gov/is/crslist.aspx

=== Where can I find information on the National Incident Management System? ===

For more information on NIMS, please click on the following link: NIMS https://www.fema.gov/emergency-managers/nims

=== Does the CAPT 116 test have to be taken online or can it be administered at cadet meetings? ===

The CAPT 116 does not have to be taken online - it can be administered in a paper form at local units. The preferred method of completion is online but if that is not possible, contact the CAP/DO at do@capnhq.gov to request a hard copy of the test.

When the test is taken online the results are automatically stored in the testing system, and completion is automatically forwarded into the national database requiring less administrative support than taking it at a unit meeting using the paper form.

If the test is administered via hard copy, once the test is passed, the Emergency Services Officer or testing officer can enter the completion as a task into Ops Quals under the GES Achievement.

=== Do cadets participate in operational missions? If so, what type of missions? Under what circumstances would a cadet be sent on a mission? ===

Cadets often participate in missions. See guidance below from Section B, Paragraphs 1-10e of {{Pub|CAPR|60-3}}.

e. Use of qualified CAP cadets is encouraged as much as possible on appropriate missions. Cadets should be trained in the various functions of mission operations and support as permitted. Cadets qualify no differently than adult members in emergency services qualifications, and can be properly utilized in age-appropriate scenarios. Additional guidance for employing cadets on missions can be found on the CAP/DOS website at Cadets in Emergency Services.

The above reference to the CAP/DOS website is outdated and will be updated with the next version of {{Pub|CAPR|60-3}}. Please visit the following website to review cadet participate: https://www.gocivilairpatrol.com/programs/emergency-services/operations-support/cadets-in-emergency-services

=== Are Cadets authorized to wear specialty track badges? If so, what are the requirements for earning these badges? ===
Cadets can earn and wear certain specialty badges although they do not receive the technician rating until they complete the requirements as senior members. There are some positions which have age limitations which would prohibit cadets from holding certain jobs. Badges presently available for cadets include Emergency Services, Communications and History.

Also please see {{Pub|CAPR|35-6}}, {{Pub|CAPR|60-3}}, {{Pub|CAPR|210-1}}, {{Pub|CAPP|223}}

=== Are there any CAP regulations regarding recall rosters? ===
Yes. {{Pub|CAPR|60-3}} requires CAP wings to establish and maintain an alerting system to be used throughout the wing to provide immediate response on a limited basis at all times and full-scale operations as soon as possible. It does not mandate a particular form or method for the recall roster such as a telephone recall or electronic notification, but does require the established alerting system to be used throughout the wing.

=== On my 101 card it says that I am SET qualified. What exactly is my function as a skills evaluator. What am I qualified to do? ===
As a qualified evaluator you may certify CAP members training in those areas under your supervision.

For more information please refer to {{Pub|CAPR|60-3}}, para 2-2.

=== Where can I find information on the AF Rescue Coordination Center (AFRCC)? ===
As the United States' inland search and rescue (SAR) coordinator, the Air Force Rescue Coordination Center (AFRCC) serves as the single agency responsible for coordinating on-land federal SAR activities in the 48 contiguous United States, Mexico and Canada.

The AFRCC is located under the 1st AF (AFNORTH) at Tyndall Air Force Base, FL. and operates 24 hours a day, seven days a week. The center directly ties in to the Federal Aviation Administration's alerting system and the U.S. Mission Control Center. In addition to the Search and Rescue Satellite Aided Tracking information, the AFRCC computer system contains resource files that list federal and state organizations, which can conduct or assist in SAR efforts throughout North America. When a distress call is received, the center investigates the request, coordinates with federal, state, and local officials, and determines the type and scope of response necessary. Once verified as an actual distress situation, the AFRCC requests support from the appropriate federal SAR force. This may include Civil Air Patrol, U.S. Coast Guard, or other Department of Defense assets, as needed. State agencies can be contacted for state, local, or civil SAR resource assistance within their jurisdiction. The AFRCC chooses the rescue force based on availability and capability of forces, geographic location, terrain, weather conditions, and urgency of the situation. During ongoing SAR missions, the center serves as the communications hub and provides coordination and assistance to on-scene commanders or mission coordinators in order to recover the mission's objective in the safest and most effective manner possible. AFRCC uses state-of-the-art technology including a network of satellites for monitoring emergency locator transmitter signals. Systems such as these help reduce the critical time required to locate and recover people in distress.

== Air search and rescue ==

=== At a recent meeting, a senior member showed a set of slides for the presentation of the scanner and observer courses. Are they available on the CAP website? ===

There are slides available on the [https://nesa.cap.gov/about/schools/mas NESA website].

=== Must a member become Mission Scanner qualified first before becoming qualified as a Mission Observer? ===

Yes, a member must be MS qualified before they can become a Mission Observer.

=== Where can I find the airborne photographer task guide information of tasks O-2201-2219? ===

For more information on this topic, please click on the following link which will take you to the [https://nesa.cap.gov/about/schools/mas/scanner NESA website].

=== Can a Mission Pilot (MP) Trainee participate in an actual AF Authorized Mission as a MP under the supervision of a qualified MP? ===

Yes. Trainees in a position can work actual or training missions in their specialty under the supervision of someone qualified to sign off on it provided they do not compromise mission safety to accomplish the training. Under current regulations the right seat person in this instance would have to be a Qualified MP and since the example is an actual AF mission, that MP would also have to be a qualified MO.

For more information on this topic please see para 2-2 and 2-3 of {{Pub|CAPR|60-3}}.

=== Where can I find Mission Pilot proficiency flight profiles? ===

Pilot proficiency profiles are provided in two CAP standards: {{Pub|CAPS|71-4}}, AFAM-approved Pilot Proficiency Profiles or {{Pub|CAPS|71-5}} Corporate-approved Pilot Proficiency Profiles. These documents prescribe procedures for use the profiles and documentation of sortie completion.

https://www.gocivilairpatrol.com/members/publications/standards

=== I was unable to find anything on the web site about an Aircraft Survival Kit, and I was wondering if you could send me a list of what is available? ===

The contents of the AIRCRAFT SURVIVAL KIT vary from region to region and season to season. Check with your wing or region for specific requirements.

Listed below is a typical AIRCRAFT SURVIVAL KIT.

AIRCRAFT SURVIVAL KIT- 3 PERSON - 3 DAYS

(1 ea) * USAF Aircrew Survival Manual AFP36-2246, 122 pages, current military
(9 ea) Aqua-Bloc® 8.45 fl. oz. water pack, 1 per day per person
(1 ea) * 5 qt plastic, water storage bag
(1 ea) 8 oz. bag, hard survival candy
(3 ea) food bar, 3600 calories - non-thirst provoking. 5 year storage life, 3 servings per person per day
(1 ea) ACR Firefly Plus strobelight/flashlight, requires 2 AA batteries, included
(3 ea) * space blanket, silver/orange foil, 56""X96"", featherlite & waterproof
(3 ea) emergency sleeping bags manufactured from space blanket foil, windproof & waterproof
(1 ea) * fire starter with 10 fire tabs, works ""one-handed"" in case of injury
(1 ea) * signal mirror, acrylic 3""X5""
(1 ea) * magnetic pocket compass MC1
(1 ea) zipper thermometer
(1 ea) * USAF survival knife, 5"", with leather handle, sheath & sharpening stone
(1 ea) * heavy-duty finger saw with finger rings and 2 blades
(1 ea) * 10"" machete with sheath, belt clip & sharpening stone
(1 ea) snare kit with two self-locking steel snares / (1 ea) * emergency fishing kit, fresh or salt water
(1 ea) * survival whistle ACR/WW3, distinctive high pitch sound
(1 ea) white nylon cord, 50', 500 lb test
(1 ea) water purification tablets, 50 tablets - 6 gal water
(1 ea) first aid minor emergency packet #1 - 25 items
(1 ea) first aid packet #2 - misc. heavy bandages, 41 items
(1 ea) personal hygiene kit c/o 3 toothbrushes, toothpaste, talcum powder, 3 pocket combs, 6 toilet paper, 3 soap and 3 garbage bags
(1 ea) 36 hour canned candle
(1 ea) 18"" X 36"" sheet aluminum foil
(4 ea) AA batteries for strobelight/flashlight, 3-5 year storage life
(3 ea) * plastic survival sunglasses
(3 ea) 40"" X 48"" emergency poncho - orange
(1 ea) *insect repellent stick - 1 oz.
(1 ea) 2' X 6' signal panel - chartreuse & orange with tiedown cords.

All items are stored in a 14"" X 16"" X 6"" USAF survival field pack. Water resistant & airtight, with rubber sealed metal zipper & shoulder straps for emergency backpacking. 24 lbs.

=== Where can I find information on the water survival emergency services specialty qualification listed in {{Pub|CAPR|60-3}}? ===

Water Survival emergency services specialty qualification training listed in {{Pub|CAPR|60-3}} is available on AXIS.

Please login to eServices and go to the upper left hand corner and select menu, in the dropdown, please go to Online Learning then select Learning Management System. The next screen, in the upper middle section, you should see Go To AXIS. Please select that option.

=== What are the specific requirements to be a qualified Mission Observer? ===

For the latest SQTRs see My Operations Qualifications in eServices.

=== What is the recommended procedure on how to use the DF equipment for ELT searches in aircraft? Flight patterns to positively locate targets? Needle interpretations? Suggested altitudes? Use of sensitivity control? ===

The search and rescue patterns and procedures recommended for various types of searches can be found at gocivilairpatrol.com>Programs>Emergency Services>National Emergency Services Academy (NESA)>MAS>NESA MAS. Once on the NESA site, the documents are in the right hand menu.

=== Is the scanner course available online and where can I find details? ===

There is no longer a distance learning course for mission scanner. Training requirements are found in {{Pub|CAPR|60-3}} in the NESA training curriculum.

== Ground search and rescue ==

=== What are the guidelines as far as training cadets in CPR and/or First Aid? Is there any specific organization that CAP wants squadrons to use for this training? What are the requirements to be certified as far as SAR and ES is concerned? ===

Note: Generally the only first aid and CPR training requirements are in the area of emergency services, primarily for ground team members. See below from {{Pub|CAPR|60-3}}.

1-24. Legal Issues of CAP Operational Missions.

f. First Aid and Emergency Medical Care. CAP is not an emergency medical care or paramedic organization and should not advertise itself as such. CAP will not be the primary provider of medical support on missions or training events though qualified personnel can be used to support such activities. The only type of medical aid that should be administered by CAP personnel or by any other person at CAP's request is reasonable treatment deemed necessary to save a life or prevent human suffering. This treatment must be executed by a person qualified to attempt such medical care within their skill level. When first aid or higher medical training is required for qualification in a particular specialty, the expectation is that the qualification course includes both knowledge and practical skills training; first aid courses taken on-line only are not acceptable; though members are not considered employees when supporting operations, courses are expected to meet the National Guidelines for First Aid in Occupational Settings available at https://www.osha.gov/Publications/OSHA3317first-aid.pdf or ASTM F 2171-02(2009), Standard Guide for Defining the Performance of First Aid Providers in Occupational Settings. CAP medical personnel are not provided supplemental malpractice insurance coverage, and any care provided is at the members own risk. Though medical supplies and equipment are not normally provided to responders, any reasonable supplies used on training or actual missions may be submitted for reimbursement as long as sufficient justification is provided.

We do not require them to take a specific organization’s courses or get specific certificates - there really are a variety of options across the country. Our intention is for personnel to meet and document completion of some basic standards. See the attached file below which should give you an idea as to what we are looking for when asked if we would consider a course equivalent. There are many courses and organizations that provide training to meet these requirements.

There is not a national program for CAP to get CPR and First Aid for free. Some units and wings have made arrangements locally with the American Heart Association, American Red Cross, National Safety Council, or other providers though. This is typically done by having members become instructors so that they can provide training at minimal cost if any. Some communities also offer free training like this to the public and CAP members can often take advantage of it, but again, there is no national program at this time.

Also see OSHA Best Practices Guide: Fundamentals of a Workplace First-Aid Program

NOTE: {{Pub|CAPR|60-3}} is currently going through a revision that will clarify the First Aid training. In the meantime, CAP doesn't create in house first aid classes; we can’t take on that liability. However, members that are approved instructors for other organizations like ARC, AHA, NSC, ASHI, ECSI, MFA, etc. can teach those programs under that hat to our members. There are also many personnel that are able to line up training from military bases that will provide credit…self aid and buddy care for example. For credit, the member needs documentation of completion, so roster signed off by the instructor, etc. would work.

=== Are online-only first aid and CPR classes be acceptable for completing the requirement for ES qualifications? ===
No. {{Pub|CAPR|60-3}} is clear on this point (ref page 18, paragraph 1-24f): "When first aid or higher medical training is required for qualification in a particular specialty, the expectation is that the qualification course includes both knowledge and practical skills training; first aid courses taken online only are not acceptable; though members are not considered employees when supporting operations, courses are expected to meet the National Guidelines for First Aid in Occupational Settings available at https://www.osha.gov/Publications/OSHA3317first-aid.pdf or ASTM F 2171-02 (2009), Standard Guide for defining the Performance of First Aid Providers in Occupational Settings."

=== Is there minimum number of members required on a ground or urban DF team? ===

Yes. Ground teams will not be released without a qualified ground team leader and at least three qualified ground team members or supervised trainees. Urban DF teams will not be released with less than two personnel and CERTs will not be dispatched with less than three personnel. For more information, see {{Pub|CAPR|60-3}}, para 1-17.

=== How does one meet the requirements for award of an Emergency Services (ES) Qualification Badge and/or patch? ===

Paragraphs 3 and 4 of {{Pub|CAPR|35-6}} covers the requirements for award of Emergency Services (ES) Qualification Badge and the CAP Emergency Services Patch.

=== Are squadrons required to maintain emergency services qualification files such as copies of SQTRs on its senior members other than what is in e-services? ===

See documentation requirements in Paragraph 1-5c of {{Pub|CAPR|60-3}}.

=== What are the requirements for someone to train CAP members in their ground team member level 3 tasks? Do they just have to be GTM3 qualified and have their SQTR completed? ===

They need to be a qualified evaluator in accordance with {{Pub|CAPR|60-3}}, paragraph 2-2 to sign off on tasks. That does not prevent other members from supervising them on missions or providing other instruction, but the tasks need to be signed off by a qualified evaluator. For ground team members that would be a member qualified to the same level or higher or other specialties that can sign off. For example a Ground Branch director could sign off on tasks done remotely if they can verify accomplishment, but they don't have to. See {{Pub|CAPR|60-3}}.

Additionally, some wings have chosen to limit their list of evaluators further via approved supplement, so you may want to check with your wing to be sure that has not been done.

=== Where can I download the task guides Urban DF and Ground Team Member? ===

These are available at: https://nesa.cap.gov/about/schools/gsar

=== Where can I find the specific requirements for the Ground Team Qualification Badge? ===

Paragraph 5 of {{Pub|CAPR|35-6}} covers the requirements for award of Ground Team Badges.

5. Requirements for Award of the Ground Team Badges:
a. Basic Ground Team Badge: Be qualified as a CAP ground team member IAW {{Pub|CAPR|60-3}}.
b. Senior Ground Team Badge:
(1) Be qualified as a CAP ground team leader IAW {{Pub|CAPR|60-3}} or
(2) Be qualified as a CAP ground team member – level one
c. Master Ground Team Badge. Be qualified as a CAP ground branch director IAW {{Pub|CAPR|60-3}}.

=== What are the CAP policies on knives both at CAP meetings and during CAP emergency services missions? ===

Sheath knives may be worn during your participation on emergency services missions, but there are some limits and some knife types are prohibited. Swiss Army knives, Leatherman or Gerber multipurpose type tools are recommended. Always check to make sure you are compliant with local laws.

The following guidance comes from GROUND & URBAN DIRECTION FINDING TEAM TASKS

e. Restrictions on Knives: You may only wear a sheath knife if authorized by your team leader. Sheath knives cannot have a blade longer than 6” or a total length of greater than 11”. The sheath must adequately secure the knife and protect the wearer from the blade. If authorized, sheath knives will be worn only on the pistol belt or carried inside the pack. The following knife types are not authorized: boot knives, butterfly knives, switch blades, double edged knives, “Rambo” style survival knives, or knives with retracting sheaths. Machetes or hatchets can only be carried by senior members when needed for that specific sortie. No knives may be visible when the member is performing crash sight surveillance duty.
Knives may also be used for some aerospace education constructions. The regulation that governs cadet participation at CAP meetings, CAPR 52_16, is silent on the subject, but there is typically no on-going need for cadets to bring knives to regular CAP meetings.

Also see guidance below Paragraph 2 of {{Pub|CAPR|900-3}}.
2. Other Dangerous Weapons. Other than as provided for in paragraph 1 above, members engaged in CAP activities are prohibited from possessing or using weapons as defined by local state statutes as ""dangerous.""

=== Can cadets who are qualified ground team leaders, but under 18, train others as ground team leaders? ===

Cadets cannot become qualified ground team leaders if they are under 18. They can qualify through ground team member level one which has overlapping tasks with the ground team leader specialty, and could train personnel on those tasks, but could not supervise a ground team leader on a mission.

=== I would like to have a list of field gear items for a SAR-EX/SAR. What should be in the 24/72 hour pack? ===

Contents may vary from region to region based on weather and other conditions. Check with your wing for specific requirements. A sample list at Attachment B of the NESA policies and procedures at the following link: Packing lists.{{dead link}}

=== If a member's ES ground team qualifications expire are they still authorized to wear the ES patch and Ground team badge? ===

Just like the Air Force, once the Emergency Services (ES) or ground team badges are earned, they can be worn forever.

=== Point of Distribution Course (PODC) ===

The requirement for Point of Distribution course (PODC) credit has been changed to allow credit for the online FEMA ""IS-26: Guide to Points of Distribution Course"". This removes the requirement for both the in-residence course and the online course. The FEMA course can be accessed at: https://training.fema.gov/is/courseoverview.aspx?code=is-26 . Until we have a place holder in the Emergency Services upload documents in Ops Quals, members should load the certificate as “Other” and identify the certificate as there IS-26 PODC completion they should then enter their completion date on the PODC SQTR for approval.

For those members that previously completed the course in residence training the unit can enter their training completion date and approve the completion. We highly encourage these members to complete the IS-26 course.

=== Once a NIMS course is completed online (e.g., IS-800) how does it get entered on my SQTR in eServices? ===
See procedures below from National Incident Management System (NIMS)
Personnel completing IS-100, IS-200, IS-700, and IS-800 online must upload a copy of the course certificate in ""Ops Quals"" in eServices. Unfortunately, completion of these courses cannot be automatically loaded into Ops Qualifications in eServices as this is not supported by DHS.
To upload a document follow the steps below:
1) Log into eServices
2) Go to ""Operations Qualifications"" under Operations
3) Click on ""Entry/View Worksheet""
4) Enter your CAP ID
5) Select ""View/Upload Documents"" right below your name at the top of the screen.
6) Select the document you would like to upload from the drop down menu.
7) Browse for the document on your computer and upload.
After the training/document is validated, you will see credit in the training areas.

== Incident command post and staging area staff ==

=== Should you walk backwards while marshalling an aircraft? Any references? ===
Individuals need to be taught where to stand when directing aircraft so they will not have to move backward. One of the Flight Line Marshaller’s responsibilities is to be responsible for the safety of assistants and trainees by verifying they know where to stand when directing aircraft, so they will not have to move backward.

See below from Aircrew & Flightline Tasks:

'''O-3001 Discuss Flight Line Marshaller’s Responsibilities'''
2. You are responsible for the safety of your assistants and trainees, assuring they are properly trained
a. Verify they know where to stand when directing aircraft, so they will not have to move backward.
b. Verify they know the proper hand and arm signals to direct the aircraft.
c. Verify that they know how to communicate with you and you with the Flight Line Supervisor for instructions.

'''O-3009 Perform Aircraft Taxi Procedures'''
2. CAP personnel marshalling aircraft must position themselves to meet the following requirements
a. Never position yourself in the path of an oncoming aircraft
b. Never position yourself in a location where any part of an aircraft will pass over you
c. Never walk backwards on the ramp
d. Never run on the ramp
e. Always marshal aircraft entering a congested ramp under CAP control
f. Always get enough personnel to control aircraft movement without compromising safety
g. Always position yourself where you can maintain direct eye contact with the pilot-in-command (ten feet to the pilot’s left of the left wing tip and far enough in front of the aircraft to allow for a turn in front of you is ideal)
h. Always hand the aircraft off to the next marshaller before the pilot losses sight of you.
3. Careful planning of the number of resources and their position can accomplish this with ease. Suggested marshaller positioning is shown on the following diagrams for departing (fig. 1) and arriving (fig. 2) aircraft.

You can also take the ""Aircraft Ground Handling"" Course on Learning Management System to learn more about aircraft movement. "

=== Where can I find the requirements to be a flight line marshaller? ===
For Flight Line Marshaller (FLM) requirements see My Operations Qualifications under eServices. Also refer to Para 2-3 of {{Pub|CAPR|60-3}}.
The following link will take you to the SQTRs in Ops Quals. The SQTR outlines all the training requirements for FLM: Flight Line Marshaller SQTR
There is not a minimum age for Flight Line Marshaller.

=== Where can I find the hand signals used on the flight line for marshalling aircraft? I'm trying to train several new cadets on the hand signals. ===
See Chapter 2 of AIR FORCE MANUAL 11-218 AIRCRAFT OPERATIONS AND MOVEMENT ON THE GROUND (Large PDF File)

This instruction implements AFPD 11-2, Flight Rules and Procedures. It prescribes rules for the operation, movement, and control of aircraft on the ground. This instruction applies to ground operations of all USAF aircraft operating in an aircraft apron/ramp and movement area at any airfield, whether military, civilian, or foreign. This instruction does not apply to specialized maintenance procedures normally conducted away from aircraft apron/ramp and movement areas, such as engine runs conducted in approved sound suppressors. This instruction applies to all personnel operating USAF aircraft on the ground, whether military, civilian, or contractor.

=== What type of training and supervision is required for CAP members to marshall aircraft at an airshow? ===
CAP members may not direct parking of aircraft at air shows unless they have received training on aircraft marshalling and have a flight line authorization on CAPF 101 or CAPF 101T. A fully certified flight line marshaller (FLM) should be present to supervise all members in trainee status.

In addition, from {{Pub|CAPR|900-5}}, the following rules must be followed.

b. Permitted Activities. CAP units and members may assist with an air show sponsored and conducted wholly by agencies and organizations other than CAP. Prior permission to assist or participate in any air show must be obtained from the General Counsel at National Headquarters. No such advance permission is required if the CAP assistance or participation in an air show is limited to the following:
(1) CAP members may be used as guides or to provide directions or information.
(2) CAP units may setup a recruiting booth and/or a concession stand selling food and drinks on the premises of an air show, providing that CAP is not in any way acting as a sponsor.
(3) CAP members may be used around parked or static display aircraft for guidance, information or direction.

=== I am aware that CAP Regulations do not allow aircrew to use night vision goggles, but is there a regulation prohibiting use among Ground Teams? ===
No. CAP ground resources may use night vision devices in support of SAR/DR operations while on foot or as passengers in vehicles. Use of night vision devices by drivers during motor vehicle operations is prohibited.

Night vision devices may not be used by the pilot flying CAP aircraft. However, night vision devices may be used by scanners and observers who have completed nationally approved training in the use of this equipment. Only nationally approved night vision devices are authorized for use.

=== Is there a requirement to wear a safety vest with ABUs during ground team activities? ===
Safety vests rules have changed. The policy can be found in {{Pub|CAPR|160-1}} in section 3.6. titled "Personal Protective Equipment (PPE)".

== Incident management teams ==

=== What is the criteria for award of the incident commander's badge? ===
Incident Commander Badge. A three-level specialty insignia was approved for those members qualifying as Incident Commanders under {{Pub|CAPR|60-3}}. The senior badge is worn by members earning the IC-2 rating and the master badge by those earning the IC-1 rating. The badge is worn in the same position as the Ground Team Badge and other specialty insignia. A cloth version is available for wear on the BDU and field uniforms

=== Could you clarify the eligibility of Mission Base staff to earn the "Find" ribbon in support of the Ground Team? ===

Credit towards FIND ribbons is normally given to the aircrew and/or ground team that located the objective; however, a search force including incident staff and other aircrews and teams involved may be credited with a FIND.

See criteria from {{Pub|CAPR|60-3}}, para 1-27 and 1-28

== National Emergency Services Academy (NESA) ==

=== How does a Chaplain become a Mission Chaplain? ===

Training requirements for mission chaplains can be found on the Mission Task Guide at: Mission Base Task Guide.

The requirements to train or qualify in these specialties can be found in the SQTRs in OPS QUALS in eServices, and additional information can be found in the Mission Base Task Guide above.

=== Where can I find information on the National Emergency Services Academy and Ground Search and Rescue School? ===

NESA began as NGSAR (National Ground Search And Rescue School) at the Miller School in Virginia in 1996 with 42 students and staff. GSAR is still with us today as a part of the larger National Emergency Services Academy. Now headquartered at Camp Atterbury, Indiana, NESA is CAP's largest National Special Activity, training 300-500 CAP Emergency Services operators from around the nation every summer. More information can be found at the following link: http://nesa.cap.gov/

=== Where can I find a copy of the "Mission Aircrew Reference Text?" ===

The text is available on the National Emergency Services Academy web site at: NESA

== Counterdrug ==

=== When can a CAP member participate in counterdrug operations? ===

Before CAP members may participate in counterdrug operations, they must be a senior member, at least 21 years of age, with at least 2 years membership in CAP. Time spent as a cadet may be used to satisfy this two year requirement. For additional requirements please see {{Pub|CAPR|60-6}}.

2-2. Counterdrug Membership Requirements and Currency.

The authorization to participate in the counterdrug program is a privilege, not a right. Wing CD members participate in the CD program at the discretion of the wing commander as well as the customer. Region CD staff members participate in the CD program at the discretion of the region commander as well as the customer. Every CAP member having access to or knowledge of actual CAP counterdrug missions and mission results must be a qualified CD member

a. Appointment. The wing and region commanders select CAP members to participate in their counterdrug program. CAP members will be selected based on the reasonable certainty that the member is of good character and well motivated. They must be an appropriate representative of Civil Air Patrol in duties subject to high profile scrutiny by law enforcement agencies, Civil Air Patrol and Air Force senior commanders, news media and the general public. The following requirements must be met and maintained before the member may participate:
1) Be ES mission qualified and current in a specialty that has an application with the CD program.
2) Be a senior member, at least 21 years of age, with at least 2 years membership in CAP. Time spent as a cadet may be used to satisfy this requirement.

b. The applicant must complete a CAPF 83, CAP Counterdrug Application, and submit it for review to the wing CDO for wing personnel or region CDD for region staff. Only the most current version of the CAPF 83 will be accepted. This form is a two-sided form, printed on the front and back of a single sheet of paper. Ensure the member has filled in all parts of every box on both sides. The wing CDO reviews, signs and forwards the CAPFs 83 to the wing commander to review member eligibility and for signature. The region CDD reviews, signs and forwards region CAPFs 83 to the region commander to review member eligibility and for signature. The customers require the wing or region commander to be actively involved in the counterdrug application and review process and require a wing or region commander signature on all CAPFs 83. Wing and region commanders will not delegate signatory responsibility for the CAPFs 83. When wing or region commanders submit their own individual CAPF 83, they will sign on the line for the applicant as well as the line for the wing/region commander. The wing CDO will review the wing commander’s CAPF 83 for completeness and sign on the line for the wing CDO. The region CDD will review the region commander’s CAPF 83 for completeness and sign on the line for region CDD. The wing CDO and region CDD submit their CAPFs 83, with original signatures and printed as a two-sided, single-sheet document, to the NHQ CAP Chief, Confidential Screening (NHQ/PMM) for processing.

c. Screening. NHQ CAP/LMMC verifies the applicant’s CAP membership and the completeness of the member information on the CAPF 83, enters the pertinent information into the CD database, and forwards it to the appropriate federal agencies for background screening. If a screening agency disapproves member participation, the individual will not be allowed to participate in the CD program. NHQ CPA/LMMC will notify the appropriate wing CDO (or region CDD for a region staff member) and the member if the screening agency disapproves member participation. The screening agency does not provide the reason they decline the participation. Once the screening agency disapproves counterdrug program participation, the member has no right to appeal and the decision of the agency is final.

d. Orientation. The member must complete the National Counterdrug Orientation course. The member may not complete the National Counterdrug Orientation course until after the screening process has been completed.

=== What is the status of the CAP National Counterdrug Refresher Training Course? ===

{{Update|section|date=2018}}

See {{Pub|CAPR|60-6}} Paragraph 2-2e.(2) below for details of the National Counterdrug Refresher Training course.

2-2. Counterdrug Membership Requirements and Currency.

e. Currency.

2) Counterdrug members must complete the National Counterdrug Refresher Training course at least once every 2 years. The National Counterdrug Refresher Training course is an online course available anytime. If an individual does not complete a National Counterdrug Refresher Training course within the 2-year time frame, the member will be suspended from participation in the counterdrug program. The suspended member may participate in CD activities only after completing the course.
https://tests.capnhq.gov/ops/cd_dl/test_page.cfm?Message=Ok NOTE: training is only available to those qualified to take the course.

A new course is planned to be released early in the Spring of 2018.

=== Where can I find information on the CAP Counterdrug Operations program? ===

Guidance on the counterdrug program is covered in {{Pub|CAPR|60-6}}.

[[Category:FAQ]]
[[Category:Operations FAQ]]

Template:Form

2025-05-21T16:08:54Z

NMcLarty27:

Template:Form

2025-05-21T16:03:54Z

NMcLarty27:

[{{#switch: {{{1}}}
| CAPF = https://www.gocivilairpatrol.com/members/publications/forms#:~:text=F{{#invoke:String|replace|{{{2}}}|-|%2D}}
| AF = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| DAF = https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword={{{1}}}{{{2}}}&isObsolete=false&modID=449&tabID=131
| FAA = https://www.faa.gov/forms/index.cfm/go/document.list/?q={{{2}}}
| ICS = https://training.fema.gov/icsresource/icsforms.aspx#:~:text=ICS Form {{{2}}}
}} {{{1}}} {{#switch: {{{1}}} | AF = Form | DAF = Form | FAA = Form | ICS = Form}} {{{2}}}]

Personnel and membership FAQ

2025-05-21T15:55:11Z

NMcLarty27: /* Where can I find information on the Aerospace Education Member (AEM) Program? */

{{CAP Knowledgebase only|date=April 2024}}

== Membership ==

=== Does a commander have the authority to remove a senior member from active status if they are not completing training or participating in any squadron activities? ===
Unlike cadets, there is no specific requirement for senior members to regularly attend meetings or progress in rank. However, there are provisions for commanders to initiate membership termination or transfer procedures for senior members for habitual failure to complete training requirements, perform duty requirements and for substandard performance of duty over an extended period of time. Commanders might also remove a person from a duty position in the unit for these same reasons. Another possibility for the member who does not complete required training or participate on a regular basis is for the commander to transfer the member from "Active Status" to "Reserve/Patron Status."

See {{Pub|CAPR|35-3}} for more information.

=== Where do I go to renew my CAP membership online? ===
Individuals wishing to renew online must log into eServices. If your membership has already expired and you are within the prescribed renewal period, you will be taken directly to the online renewal site upon logging in. If your membership is current, you will see the normal eServices pages when they log in. If you are eligible to renew online, you will see a Renewal link in the center of the page. Simply click on that line and it will walk you through all the necessary steps.

=== Where can I find information on the Aerospace Education Member (AEM) Program? ===
An important part of CAP's external program is the Aerospace Education Member (AEM) Program. This program is designed primarily for teachers from kindergarten through twelfth grade who want to promote aerospace education in their schools using CAP educational products and resources. For their annual membership dues, AEMs receive a membership certificate, lapel pin, periodic newsletters, special educational products, the opportunity to participate in CAP's School Aerospace Excellence Award Program, etc. Recognizing their budgets are tight, we also have a special annual membership rate for undergraduate student teachers.

For more information, please click on the following link: [https://www.gocivilairpatrol.com/programs/aerospace-education/join-as-an-aem Educators]

=== I have voluntarily resigned from Civil Air Patrol by sending a letter to the Squadron Commander and the Group Commander. Are there any additional forms that I need to fill out? I can not find any reference to this in the regulations. ===
Though we hate to lose a member, we realize circumstances may at times limit members' ability to participate in CAP activities. To submit a voluntary resignation, members should use the {{Form|CAPF|2B}}. For the reason, select "voluntary resignation." You may request a copy of your records from your unit which will be helpful when you hopefully resume your membership in CAP. Thanks for your volunteer spirit and contributions to CAP, and we hope you'll be able to return as a member someday. Meanwhile you might consider participating in some other membership category.

More information can be found in {{Pub|CAPR|35-3}}.

=== Is it possible to join the Civil Air Patrol (CAP) initially as a Patron member? ===
Details on patron membership are in Chapter 4 (see below) of {{Pub|CAPR|39-2}}, but the short answer is Yes, you can initially join as a Patron.

4.2. Patron Members. Individuals applying for patron membership through a local squadron should complete a {{Form|CAPF|12}}, annotated in red across the top "PATRON MEMBER." The previously authorized National Patron category is being phased out. Individuals may no longer join or transfer in to the squadron. All prospective members applying to a local unit must meet the Unit Membership Board as outlined in paragraph 1.5. prior to the approval of the membership application by the unit commander. Upon approval by the unit commander, the applicant will forward the CAPF 12 along with a check or money order to CAP/DP, 105 South Hansell Street, Maxwell AFB AL 36112-6332. (See attachment 1 and the chart posted online at www.CAPR|39-1embers.com/dues for actual dues amount required.) Commanders must validate the individual’s proof of identity and annotate the Form 2a accordingly. Acceptable documents for proof of identity are the same documents required on the Form I-9 for employment eligibility verification. See attachment 2 for a list of these documents. Patron members are not required to submit a FBI fingerprint card; however, they must meet the membership criteria outlined in paragraph 3.2. above. Once the application is processed by National Headquarters, the member will receive a distinctive membership card.
4.2.1. Patron members may:
4.2.1.1. Receive a specially annotated membership card.
4.2.1.2. Receive the Volunteer magazine (when printed).
4.2.1.3. Receive discounts associated with active membership (car rental, etc.).
4.2.1.4. Retain the last CAP grade held prior to entering patron status if transferred to patron status without a break in service.
4.2.1.5. Attend wing and region conferences and the CAP National Conference sponsored by National Headquarters.
4.2.1.6. Attend special unit social events upon invitation by the commander concerned, such as anniversary celebrations, awards banquets, holiday parties, etc.
4.2.1.7. Use Civil Air Patrol ground transportation, but use of Civil Air Patrol air transportation is prohibited.
4.2.1.8. Transfer to active member status upon meeting active member qualifications. (See paragraph 4.2.3.1. below.)
4.2.2. Patron members may not:
4.2.2.1. Wear the CAP uniform.
4.2.2.2. Ride in or fly CAP aircraft. (This includes member-owned aircraft on CAP flight

Individuals can join as a patron member through their local squadron. They will need to submit a {{Form|CAPF|12}} senior member application with PATRON across the top and one year of dues (patrons pay the same amount as seniors).

=== If a cadet joins the National Guard, is it true they must resign from CAP, or can they convert to a Senior Member? ===
They definitely DO NOT have to resign from CAP as CAP has many members who are also active duty service members or members of reserve and guard units. Cadets may have the option of converting to senior membership (active status) or of remaining a cadet under certain conditions.

Please see the following excerpt from {{Pub|CAPR|39-1|39-2}}:

2.5. Upon Joining the Armed Forces. Cadets who join any branch of the active duty Armed Forces (this does not include military service academies) will furnish CAP/DP written notification along with a {{Form|CAPF|12}} and FD Form 258 (see sample at attachment 5), at which time they will be automatically transferred to active membership status. Additional membership dues are not required for the duration of the current membership year; they will be billed as active member renewals. Note: Cadets who join the National Guard or Reserves are not required to become active upon attending "basic training.” Regardless of the wording of the orders, "basic training" is not interpreted by CAP as "extended active duty." However, National Guard or Reserve members who enter "extended active duty" are not eligible to be cadets and must become active members. Individuals who join the Armed Forces under the delayed enlistment program are not required to become active members until such time as they actually report for duty."

=== If the commander is taking termination action against you, what type of appeal do you have and can you still participate in CAP activities during the appeal? ===
Appeal procedures are covered in SECTION D - APPEAL PROCEDURES of {{Pub|CAPR|35-3}}.

A member is automatically considered in suspended status upon notification of membership termination proceedings under {{Pub|CAPR|35-3}}, Membership Termination. The suspension is effective until the termination process is complete including appeal periods. Members in suspended status are prohibited from attending meetings, participating in CAP activities, wearing the CAP uniform or otherwise exercising the privileges of membership. A suspended member must also turn in his/her membership card to the unit commander for the duration of the suspension.

You should also reference {{Pub|CAPR|35-3}}, paragraphs 9 and 10; as well as {{Pub|CAPR|35-1}}, paragrpah 2-2.

== Organization and duty assignments ==

=== What is a CAP flight and how does it fit into the organization? ===
The CAP flight is the smallest separate CAP membership unit authorized and must contain a minimum of eight members, three of whom must be seniors. Flights should be organized only in sparsely populated areas where there are an insufficient number of individuals to constitute a squadron. Note this is a separate unit not the standard flights or elements which make up a squadron.

See {{Pub|CAPR|20-1}} for more details.

=== In a Composite Squadron, what are the qualifications for the Deputy Commander for Cadets? Could an 18 year old high-school senior be appointed to this position if he converts to senior member status? What are the applicable CAP regulations? ===
According to {{Pub|CAPR|30-1}}, CAP Organization, Part III, the Deputy Commander for Cadets is a senior member position, so an 18 year old cadet would have to transfer to senior member status. While the member would not be eligible for CAP officer grade due to age, he or she may be eligible for flight officer grade depending on previous cadet achievements. One should also be mindful of age restrictions for seniors under 21-years of age with regard with chaperoning and escorting duties. The squadron commander should use caution when filing this duty assignment.

=== Is there a term limit for a squadron commander or just a suggested term limit? ===
Yes, there is a term limit. The wing commander appoints group, squadron, and flight commanders. These commanders serve a four-year term of office. Upon completion of the initial term, the Commander may be appointed to subsequent four-year terms with the approval of the Wing and Region commander.

Please see {{Pub|CAPR|20-1}} for more information.

=== What is needed to charter a new CAP unit? ===
For details on chartering a new CAP unit see Paragraph 5 of {{Pub|CAPR|20-3}}.

== Ribbons and awards ==

=== I have a question about the award of unit citation ribbons, and whether there was such a thing as a "temporary" award. Basically, if a new cadet joins a squadron that has one unit citation award, a wing that has 4, and a region that has 2, does he have the right to wear the unit citation award with a silver and bronze clasp? Is he "temporarily" allowed to wear this award, while a member of the unit? Several members quoted several different sections of CAPR 39-3 for me, and I'm not sure how to interpret it. ===
The Unit Citation Ribbon may be worn permanently by all individuals who were members of the unit during any portion of the period of time shown in the National Headquarters Personnel Action announcing the award. New members such as the new cadet mentioned who join after the period of time specified for the award are not eligible to wear the unit citation ribbon previously awarded. Unit awards are intended to be worn by members of the unit who were assigned and contributed to the mission during the period specified in the award. Allowing new members to wear the award "temporarily" while assigned to the unit is not in accordance with the intent of {{Pub|CAPR|39-3}}, "A member must be in good standing at the time of the distinguished act and must meet the criteria established for the award."

=== Can I wear the ribbons I earned as a cadet as a senior member? ===
You can wear some of the ribbons you earned as a cadet as a senior member. A list of these ribbons can be found at Attachment 2 of {{Pub|CAPR|39-3}}.

NOTE: The wording, "only the highest cadet program ribbon will be worn" refers to cadet achievement/milestone awards (Curry through Spaatz). There are a number of other ribbons and awards that may continue to be worn.

=== Where can I find out about earning the community service ribbon? ===
Requirements are found in {{Pub|CAPR|39-3}}, paragrpah 21 (i).

=== Which regulation covers the award of medals and ribbons? ===
{{Pub|CAPR|39-3}}, Award of CAP Medals, Awards and Certificates.

=== Are state ribbons from the National Guard authorized on the CAP uniform? ===
CAP allows wear of decorations,ribbons, and badges earned during service in any branch of the US armed forces but not state decorations. More information is found in {{Pub|CAPR|39-3}} and {{Pub|CAPR|39-1|CAPR|39-1}}.

=== Who is allowed to wear the CAP command badge? ===
Taken from {{Pub|CAPR|39-1|CAPR|39-1}}:

10.2.6. Command Insignia Pin. Wear of this badge is mandatory on USAF-style uniforms and optional with all Corporate-style uniforms for all current and graduated commanders in the rank of lieutenant colonel and below. Commanders (current and graduated) may only wear one commander pin, and current commanders wear the pin appropriate to their current assignment. Members are considered “graduated” after one year in office. This badge is not worn by officers who were members of the Command Council, the CAP Senior Advisory Group, the National Board or the National Executive Committee.

=== Is there guidance on wearing miniature devices like stars on medals and ribbons and normal/large devices? ===
Yes. CAP follows the guidance outlined in {{Pub|DAFI|36-2903}}. Wear regular size devices on regular medals and regular ribbons; miniature devices on miniature ribbons and medals. Wear all the same size devices.

=== What is the protocol for wearing the mini-medals on a civilian formal wear at a formal function ( i.e. an Inaugural Ball)? ===
{{Pub|CAPR|39-1|CAPR|39-1}} restricts members from wearing awards and decorations on civilian clothing. CAP medals and ribbons will be worn only by CAP members for whom they have been authorized and only on those uniforms outlined in {{Pub|CAPR|39-1|CAPR|39-1}}. There are a number of CAP Lapel Pins available from Vanguard which might be worn on civilian formal wear. Miniature medals are mandatory when wearing the AF style mess dress uniform (men and women). Also one miniature medal of choice may be worn on the CAP semiformal blazer uniform.

=== Can I still earn and wear the NRA Marksmanship Badge? ===
Cadets may wear the badge in accord with {{Pub|CAPR|39-1|CAPR|39-1}}. "NRA Marksmanship Badge. Cadets may wear one marksmanship qualification medal/badge earned by completing the requirements of the NRA Marksmanship Qualification Program. Documentation in the cadet’s personnel record which documents program requirement completion in accordance with published NRA guidelines is authority for wear." Senior members may not wear the badge regardless if earned as a cadet.

=== Are CAP members eligible for US Air Force awards like the Air Force Achievement Medal? ===
No not as CAP members. You may wear ribbons earned in the US armed forces on the CAP uniform but CAP members have a separate regulation ({{Pub|CAPR|39-3}}) which describes the medals, ribbons, and certificates that may be awarded to Civil Air Patrol members. It establishes the requirements to qualify for them, explains the administrative procedures involved, and prescribes how the medals and ribbons are worn. CAP members are not members of the armed services and thus are not eligible for Air Force awards such as the achievement medal.

=== Several of the cadets from my squadron attended and competed in the National Cadet Competition. They would like to know if they are eligible to wear the NCSA ribbon, and if so would they only be allowed to wear it during special ceremonies? We were told by a senior member that wearing the NCSA ribbon is only allowed during special events like National Boards or banquets at the end of special activities. Is this true? ===
No. The NCC ribbon and the NCGC ribbon are earned separately from the NCSA ribbon. Once earned none of these ribbons are removed for any type of special events at any level. The senior member is probably mistakenly thinking of certain uniform items which may be approved for wear by the commander in the wing or region but may not be worn to national events or encampments.

Please see {{Pub|CAPR|39-3}} for more information.

== Uniforms ==

=== Where can I find information on proper wear of the CAP uniform? ===
The regulation which covers proper uniform wear for CAP members is {{Pub|CAPR|CAPR|39-1}}.

=== What do I do if the service coat lapel covers the top badge above my ribbons? ===
Most broadly, on the USAF-style service coat, all ribbons, badges and devices worn be adult members must fall below the top notch of the collar on the service coat.

Please see {{Pub|CAPR|CAPR|39-1}}.

=== Is the AF cardigan sweater authorized as an outergarment for outdoor wear? ===
Yes. Will only be worn with the USAF Service Uniform (Class B), Aviator Shirt Uniform or Corporate Working Uniform. With the USAF-style uniform, it may be worn under the lightweight blue jacket, the topcoat and the all-weather coat. With Corporate-style uniforms, it may be worn with any outergarment as long as it does not show beneath the lower edge of the outergarment. Gray epaulets will only be worn if the sweater is worn with the Air-Force-style blue uniform.

See {{Pub|CAPR|CAPR|39-1}}.

=== What color are the gray slacks for seniors? There are many shades of gray. {{Pub|CAPR|39-1|CAPR|39-1}} states a "medium gray...." Is this closer to a charcoal or a heather gray? Would it be the same color gray as the name plates and epaulets? Or slightly darker? ===
MCAPR|39-1 is no longer available. {{Pub|CAPR|CAPR|39-1}} replaced the manual.

Although members wear various shades of gray pants with the blazer combination and aviator shirt, the uniform manual calls for medium gray.

{{Pub|CAPR|CAPR|39-1}}. 4.2.3.3. Trouser. Medium Gray (solid color). Wool, polyester‐wool blend or polyester‐cotton trousers will be worn. Either slim, straight leg or loose fit with or without pleats or cuffs is allowed. 100% cotton, tactical, chinos cotton twill weave trousers, jeans or casual trousers are not authorized with this uniform combination.

=== What footwear is authorized for flight suits? It is the opinion of some that only boots can be worn with AF flight suits. ===
{{Pub|CAPR|CAPR|39-1}}. 8.2.11. Footwear. Black combat boots are worn with the FDU.

=== Can I wear my flight suit going to a SAREX? ===
Yes if the uniform is approved for the activity. Basically, the AF flight suit may be worn during travel to and from activities provided it is not by commercial means and only essential stops are made enroute to and from the duty performance site. Wear of the AF flight suit while shopping or other nonessential activities would be prohibited.

=== I was wondering if I can wear my service dress blue uniform while flying on a commercial airplane? ===
{{Pub|CAPR|CAPR|39-1}}. 1.2.7.1. During Commercial Travel. When traveling in an official capacity on commercial air, in Continental United States (CONUS), Alaska, Hawaii, Puerto Rico and the U.S. Virgin Islands, the Service Dress uniform (Class A), Service uniform (Class B), Corporate Service Dress, Aviator Shirt Uniform or Corporate Working Uniform (polo shirt/gray slacks) may be worn when approved by the individual’s commander. Wear of field/utility, or flight uniforms is not authorized.

For more information, please view {{Pub|CAPR|CAPR|39-1}}.

=== Where can I find instructions on wear of the blue CAP utility and field uniforms? ===
{{Pub|CAPR|CAPR|39-1}}. 5.2.1. Men’s and Women’s Corporate Field Uniform (Dark Blue, BDU Style) (Figure 5.4). Field uniforms are specifically designed to be worn in a field or working environment that involves physical exertion. Field uniform wear is generally restricted to CAP meeting and activities with a field or training focus but may be worn away from activities for short convenience stops and when eating at restaurants where people wear comparable civilian attire. Do not wear field uniforms to eat in restaurants where most diners wear business attire or at establishments that operate primarily to serve alcohol. Do not starch or hot press shoulder patches. Light ironing and center creasing of NCO chevrons is authorized; however, repeated hot pressing or heavy ironing will accelerate the overall wear of the fabric. Females may wear the male version of any of the field uniforms.

{{Pub|CAPR|CAPR|39-1}} for more information.

=== I was wondering if I can wear my cadet dress blues to a school dance or other functions? ===
4.1.3. Men’s Semi-Formal Dress Uniform (Cadet Only). Only cadets can wear the USAF-style semi-formal uniform. Men’s Semi-Formal Dress Uniform is worn for social functions of a semi-formal and/or official nature as prescribed by the commander or equivalent. Semi-formal is the same term used when describing the civilian equivalent. When in semi-formal dress, saluting is not required. Recommend discussing the situation with your unit commander.

For further information, please see {{Pub|CAPR|CAPR|39-1}}.

=== What is the policy on wearing the CAP uniform when visiting military bases? ===
For more information, please see {{Pub|CAPR|CAPR|39-1}} 1.2.6. When to Wear a CAP Uniform.

=== Where can I find pictures of different AF uniform combinations? ===
You can view {{Pub|CAPR|CAPR|39-1}} for photos and graphics of Air Force-style uniform combination as worn by CAP members.

You may also view {{Pub|DAFI|36-2903}}, Dress and Personal Appearance of Air Force Personnel.

=== Are cadets authorized to wear the high polished shoes with the blues or service dress uniform? ===
6.4. Footwear. 6.4.1.2. Low Quarters. Low-quarters are worn with the Mess Dress, Semiformal, Service Dress and Service uniforms (black combat boots and dress boots are also an option with the service dress and service uniform). Shoes will be low quarter, oxford-style, lace-up with a plain rounded toe or a plain rounded-capped toe. Soles will not exceed ½ inch in thickness and the heel will not exceed one inch in height (measured from the inside front of the heel). Shoes will be smooth or scotch-grained leather or manmade material. Shoes will be shined; high gloss or patent finish is optional. {{Pub|CAPR|CAPR|39-1}}

== Miscellaneous ==

=== Where can I find guidance on public displays of affection between cadets? ===
Public displays of affection, such as hand-holding, embracing, or walking arm-in-arm, are inappropriate actions for all members in any CAP uniform. Indiscriminate displays of affection in public detract from the professional image the Civil Air Patrol intends to project. Your decision to join Civil Air Patrol (CAP) reflects a dedication and commitment to support this charitable, benevolent, nonprofit corporation. As a member of an Auxiliary of the United States Air Force, you are expected to follow the traditions, standards, customs and courtesies agreed and accepted by the Air Force and the Civil Air Patrol. These apply to all of us and reflect our pride and professionalism as members of the Civil Air Patrol.

Conduct. General. The Air Force has a very important mission and you, as a member of the Civil Air Patrol, have similar responsibilities for carrying out your mission. You are responsible for carrying out orders, performing specific tasks related to your duties, and living up to the high standards of the Civil Air Patrol. You are also held accountable for your actions, both in the performance of duties and in your personal conduct. If you are a supervisor, you have the responsibility to make sure your subordinates meet the expected standards. You must hold your subordinates accountable and take appropriate corrective actions when they do not fulfill their responsibilities. Civil Air Patrol standards of conduct apply both on and off duty, in your personal behavior, in your treatment of others, and in both military and civilian environments.

Civil Air Patrol Ethics. As a member of the Civil Air Patrol you must practice the highest standards of behavior, obedience, and loyalty-not only in your job, but in your relationship with other people. Your code of ethics must be such that your behavior and motives do not create even the appearance of impropriety. Your commitment to integrity will lead the way for others to follow.

Also see {{Pub|CAPP|151}}, Respect on Display.

=== Must a uniform be worn to drive/ride in a CAP van? If so, by driver and all passengers? ===
There is no specific requirement for senior members to be in uniform while driving or riding in a CAP van unless they are participating in or conducting the cadet program. Note: The wing or region may have established such a requirement.

CAP uniform wear is required by all while participating in or conducting the cadet program or flying in CAP aircraft (corporate and member-owned aircraft used in CAP flight activity). If cadets and seniors working with cadets are traveling in a CAP vehicle while participating in the cadet program, they normally should be in uniform. However, the regulation does allow region or wing commanders, or designees (usually group or unit commanders), to prescribe the type clothing to be worn by members while flying or engaging in organized recreational activities. In this case cadets might be authorized by a commander to ride in CAP vehicles wearing civilian clothes. For example, during a volunteer clean up day or trip to a theme park or unit picnic or other social gathering, all CAP members would likely be in civilian clothes. See {{Pub|CAPR|39-1|CAPR|39-1}}, para 1.2.4 for more detail.

=== What are the rules on wearing sunglasses with the CAP uniform? ===
Conservative sunglasses may be worn with the AF style and CAP distinctive uniforms, except in military formation . Glasses must be free of ornamentation on frames and lenses. (faddish styles and mirrored lenses prohibited). Sunglass cases will not be worn exposed on the uniform.

Please see {{Pub|CAPR|39-1|CAPR|39-1}}, para 6.3.1.2 for more information.

[[Category:FAQ]]

Mission, vision and core values FAQ

2025-05-21T15:53:33Z

NMcLarty27: /* What is the Air Force's vision? */

== Mission and vision ==

=== What is the Air Force's mission? ===
The mission of the United States Air Force is to fly, fight and win - airpower anytime, anywhere.

=== What is the Air Force's vision? ===
Deter and defeat aggression to defend and protect our nation and its interests.

=== What is Civil Air Patrol's combined mission and vision? ===
Volunteers serving America's communities, saving lives, and shaping futures.

== Core values ==

=== What are the Air Force's core values? ===
* Integrity First
* Service Before Self
* Excellence In All We Do

=== What are Civil Air Patrol's core values? ===
* Integrity
* Volunteer Service
* Excellence
* Respect

More information can be found in {{Pub|CAPP|50-2}}, Core Values, as well as in CAP's cadet and senior member educational publications, achievements and courses.

[[Category:FAQ]]

Main Page

2025-05-21T15:44:16Z

NMcLarty27:

{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.office.com/r/k5XJL4KCTy Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

TIPS Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

Main Page

2025-05-21T13:29:39Z

NMcLarty27:

{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

TIPS Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

Main Page

2025-05-20T16:07:56Z

NMcLarty27:

{{Colored box
| title=In Maintenance
| title-color=#fff
| background-title-color=#aa0000
| background-content-color=#ff000055
| center=true
| content=
'''{{SITENAME}} is currently undergoing maintenance to transition to eServices single sign-on. Logins will be unavailable during the transition.'''
}}
{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

TIPS Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

User talk:Johnhughes

2025-05-20T15:25:31Z

NMcLarty27: Mclarty moved page User talk:Johnhughes to User talk:JHughes77: Automatically moved page while renaming the user "Johnhughes" to "JHughes77"

#REDIRECT [[User talk:JHughes77]]

User talk:JHughes77

2025-05-20T15:25:31Z

NMcLarty27: Mclarty moved page User talk:Johnhughes to User talk:JHughes77: Automatically moved page while renaming the user "Johnhughes" to "JHughes77"

'''Welcome to ''CAPipedia''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:DavidDlugiewicz|Lt Col David Dlugiewicz (IT Manager)]] ([[User talk:DavidDlugiewicz|talk]]) 15:25, 21 February 2021 (PST)

User talk:Kevin

2025-05-20T15:25:28Z

NMcLarty27: Mclarty moved page User talk:Kevin to User talk:KKane63: Automatically moved page while renaming the user "Kevin" to "KKane63"

#REDIRECT [[User talk:KKane63]]

User talk:KKane63

2025-05-20T15:25:28Z

NMcLarty27: Mclarty moved page User talk:Kevin to User talk:KKane63: Automatically moved page while renaming the user "Kevin" to "KKane63"

User talk:WitchyHazel

2025-05-20T15:25:28Z

NMcLarty27: Mclarty moved page User talk:WitchyHazel to User talk:ASteuben73: Automatically moved page while renaming the user "WitchyHazel" to "ASteuben73"

#REDIRECT [[User talk:ASteuben73]]

User talk:ASteuben73

2025-05-20T15:25:28Z

NMcLarty27: Mclarty moved page User talk:WitchyHazel to User talk:ASteuben73: Automatically moved page while renaming the user "WitchyHazel" to "ASteuben73"

User:Cdale

2025-05-20T15:25:27Z

NMcLarty27: Mclarty moved page User:Cdale to User:CDale79: Automatically moved page while renaming the user "Cdale" to "CDale79"

#REDIRECT [[User:CDale79]]

User:CDale79

2025-05-20T15:25:27Z

NMcLarty27: Mclarty moved page User:Cdale to User:CDale79: Automatically moved page while renaming the user "Cdale" to "CDale79"

== Capt Charles Dale ==

=== Contact Information ===
charles.dale@mawg.cap.gov

User:Jmuofficial

2025-05-20T15:25:25Z

NMcLarty27: Mclarty moved page User:Jmuofficial to User:JMoranUrena19: Automatically moved page while renaming the user "Jmuofficial" to "JMoranUrena19"

#REDIRECT [[User:JMoranUrena19]]

User:JMoranUrena19

2025-05-20T15:25:25Z

NMcLarty27: Mclarty moved page User:Jmuofficial to User:JMoranUrena19: Automatically moved page while renaming the user "Jmuofficial" to "JMoranUrena19"

== Jose Moran Urena ==

===== About Me =====
I am C/SrA Moran Urena, a member of the [[Civil Air Patrol|Civil Air Patrol (CAP)]], serving in the Westchester Cadet Squadron 1 (NER-NY-048), under the Northeast Region. My journey in CAP reflects my passion for aviation, leadership, and public service. I am committed to upholding the core values of Integrity, Volunteer Service, Excellence, and Respect.

===== Civil Air Patrol Involvement =====
As a member of Westchester Cadet Squadron 1, I actively participate in the cadet program, learning essential skills such as aerospace education, emergency services, and leadership development. My goal is to advance through the ranks, acquire new knowledge, and contribute to the Civil Air Patrol’s mission of serving the community and nation.

===== CAPipedia Involvement =====
I’ve made the [[Squadrons]] page in CAPipedia, as well as updated the [[CAPipedia:Terms of Service|Terms of Service]]. I also created the article of [[wikipedia:Regena_M._Aye_(Civil_Air_Patrol)|Maj. Gen. Regena M. Aye]] in Wikipedia.

===== Aviation Enthusiast =====
My interest in aviation extends beyond CAP. I am an active VATSIM pilot (CID 1769468), applying the same discipline and focus from my flying simulations to my real-world CAP training. I am also fascinated by aviation safety, recently conducting an in-depth analysis of the [[wikipedia:Voepass_Flight_2283|Voepass Linhas Aéreas Flight 2283]] incident, where I concluded that ice buildup played a critical role in the crash.

===== Technical Background =====
In addition to my dedication to CAP, I am a Node.js software developer. I specialize in backend development and web technologies, including Node.js, Express, and RESTful APIs. I enjoy working on innovative projects such as:

* '''Clipzy''': A social media platform built for video editors.
* '''Biteq by Teqquu''': A Bitcoin Lightning API designed for efficient payouts without transaction fees.
* '''2048 Bitcoin''': A game offering rewards in Bitcoin through satoshis.

===== Community Focus =====
I am driven by the potential of technology to improve our world, and I aim to leverage my skills to contribute meaningfully both in CAP and beyond. Whether through developing new applications or serving my squadron, I strive to embody excellence in everything I do.

=== Closing Statements ===
Thank you for taking the time to learn more about me. If you have any questions or would like to contact me, don’t hesitate to reach out on my talk page. EXCELSIOR!

(thanks to ChatGPT for making this)

User talk:TravisCarney

2025-05-20T15:25:24Z

NMcLarty27: Mclarty moved page User talk:TravisCarney to User talk:TCarney14: Automatically moved page while renaming the user "TravisCarney" to "TCarney14"

#REDIRECT [[User talk:TCarney14]]

User talk:TCarney14

2025-05-20T15:25:24Z

NMcLarty27: Mclarty moved page User talk:TravisCarney to User talk:TCarney14: Automatically moved page while renaming the user "TravisCarney" to "TCarney14"

User:Mlawson07

2025-05-20T15:25:20Z

NMcLarty27: Mclarty moved page User:Mlawson07 to User:GLawson23: Automatically moved page while renaming the user "Mlawson07" to "GLawson23"

#REDIRECT [[User:GLawson23]]

User:GLawson23

2025-05-20T15:25:20Z

NMcLarty27: Mclarty moved page User:Mlawson07 to User:GLawson23: Automatically moved page while renaming the user "Mlawson07" to "GLawson23"

National D2R Team Member

User talk:Simsnet

2025-05-20T15:25:17Z

NMcLarty27: Mclarty moved page User talk:Simsnet to User talk:GSims61: Automatically moved page while renaming the user "Simsnet" to "GSims61"

#REDIRECT [[User talk:GSims61]]

User talk:GSims61

2025-05-20T15:25:17Z

NMcLarty27: Mclarty moved page User talk:Simsnet to User talk:GSims61: Automatically moved page while renaming the user "Simsnet" to "GSims61"

Main Page

2025-05-20T15:22:38Z

NMcLarty27:

{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to Civil Air Patrol's technologies and everything else. It is and will always continue to be a work in progress.

To add or edit pages, you will need to [[Special:UserLogin|log in]] with your Civil Air Patrol eServices account. '''Please note:''' if your first and/or last name changes in eServices after your first login to {{SITENAME}}, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form] with your old and new name and CAPID number before attempting to log in. Failure to have the username changed by an administrator will result in a new user account being created during login.

If you have any issues, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

TIPS Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

CAPipedia Sandbox:Updating CAPipedia

2025-04-17T19:09:33Z

NMcLarty27: Protected "CAPipedia:Updating CAPipedia" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>sh load-database.sh [new_db_name] [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Update local-attributes.sh ==

# Edit the <code>local-attributes.sh</code> file and change the PROD_DIR to '''capipedia-[new_version]''' and PROD_DB_NAME to the new version's database name

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-17T19:09:01Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>sh load-database.sh [new_db_name] [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Update local-attributes.sh ==

# Edit the <code>local-attributes.sh</code> file and change the PROD_DIR to '''capipedia-[new_version]''' and PROD_DB_NAME to the new version's database name

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-17T19:03:29Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>sh load-database.sh [new_db_name] [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:20:18Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull</pre><pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:19:07Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
git pull
git checkout REL[minor_version] (e.g., REL1_43)
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
git pull
git checkout REL[version] (e.g., REL1_43)
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:18:44Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
git pull
git checkout REL[minor_version] (e.g., REL1_43)
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
<pre>git pull</pre>
<pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:18:07Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull<br />git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
<pre>git pull</pre>
<pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:17:58Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands: <pre>git pull
git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
<pre>git pull</pre>
<pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:17:40Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
<pre>git pull</pre>
<pre>git checkout REL[minor_version] (e.g., REL1_43)</pre>
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# For each skin and extension that has a Git hash for its version, go to that skin or extension directory and run the following commands:
<pre>git pull</pre>
<pre>git checkout REL[version] (e.g., REL1_43)</pre>
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T16:00:09Z

NMcLarty27:

== Review the upgrading manual document ==

Review https://www.mediawiki.org/wiki/Manual:Upgrading before performing the update to note any special callouts to be considered during the update process.

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T15:45:53Z

NMcLarty27:

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from https://mediawiki.org
# Run this command from the user home directory: <pre>sh refresh-sandbox.sh</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* sandbox.capmembers.wiki</pre>
# From the <code>sandbox.capmembers.wiki</code> directory, run the command: <pre>php maintenance/run.php update</pre>
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[old_version]''' directory
# Return to the user home directory
# Run this command: <pre>sh backup-prod.sh</pre>

== Create a new production site ==

# Duplicate the production folder using the command: <pre>cp -pR capipedia-[old_version] capipedia-[new_version]</pre>
# Replace the distribution files using the command: <pre>cp -pR mediawiki-[version]/* capipedia-[new_version]</pre>
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''MySQL Databases'''
# Create a new database with a database name that matches '''capipedia-[new_version]''' and new username of <code>cap_wiki_root</code> (leave password blank)
# Upload the backup database file to the newly created database by running the command: <pre>mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]</pre>
# Obtain the password from the <code>LocalSettings.php</code> file
# Change the <code>$wgDBname</code> variable in the <code>LocalSettings.php</code> file in the '''capipedia-[new_version]''' directory to the new database name
# From the '''capipedia-[new_version]''' directory, run the command: <pre>php maintenance/run.php update</pre>

== Retarget the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to '''Websites'''/'''Manage Websites'''/'''Settings'''/'''Directories: Modify''' and change the root web directory to '''capipedia-[new_version]'''
# Wait for '''Updating Web Options...''' to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect (version shown on the page matches the distribution) and the page fully loads without errors
# Place production site back in write mode by commenting the <code>$wgReadOnly</code> variable in the <code>LocalSettings.php</code> file of the '''capipedia-[new_version]''' directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Clean up server home directory ==

# Delete the '''mediawiki-[version]''' folder and .gz distribution file
# Delete the '''capipedia-[old_version]_backup''' .gz and .sql files

== Final decommission of old version ==

# After the warranty period (no less than 2 weeks), delete the '''capipedia-[old_version]''' directory and database

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T15:21:41Z

NMcLarty27:

== Test the new version deployment prior to upgrading in production ==

# Download and uncompress the new version's distribution from mediawiki.org
# Run the `refresh-sandbox.sh` script from the user home directory
# Replace the distribution files using the command: `cp -pR mediawiki-[version]/* sandbox.capmembers.wiki`
# From the `sandbox.capmembers.wiki` directory, run the command: `php maintenance/run.php update`
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

== Backup the production site ==

# Place production site in read only mode by uncommenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the old directory
# Return to the user home directory
# Run `backup-prod.sh`

== Create a new production site ==

# Duplicate the production folder using the command: `cp -pR capipedia-[old_version] capipedia-[new_version]`
# Replace the distribution files using the command: `cp -pR mediawiki-[version]/* capipedia-[new_version]`
# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**MySQL Databases**
# Create a new database with a database name that matches the new directory name and new username of `cap_wiki_root`
# Upload the backup database file to the database by running the command: `mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]`
# Change the `$wgDBname` variable in the `LocalSettings.php` file of the new directory to the new database name
# From the new capipedia version directory, run the command: `php maintenance/run.php update`

== Switch the production hostname to the new site ==

# From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**Manage Websites**/**Settings**/**Directories: Modify** and change the root web directory to the new version
# Wait for **Updating Web Options...** to complete
# Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
# Place production site back in write mode by commenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the new directory
# Check that the following operations work as expected:
## Viewing pages
## Editing pages
## Uploading a file

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T15:20:47Z

NMcLarty27:

== Test the new version deployment prior to upgrading in production ==

1. Download and uncompress the new version's distribution from mediawiki.org
2. Run the `refresh-sandbox.sh` script from the user home directory
3. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* sandbox.capmembers.wiki`
4. From the `sandbox.capmembers.wiki` directory, run the command: `php maintenance/run.php update`
5. Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
6. Check that the following operations work as expected:

a. Viewing pages
b. Editing pages
c. Uploading a file

== Backup the production site ==

1. Place production site in read only mode by uncommenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the old directory
2. Return to the user home directory
3. Run `backup-prod.sh`

== Create a new production site ==

1. Duplicate the production folder using the command: `cp -pR capipedia-[old_version] capipedia-[new_version]`
2. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* capipedia-[new_version]`
3. From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**MySQL Databases**
4. Create a new database with a database name that matches the new directory name and new username of `cap_wiki_root`
5. Upload the backup database file to the database by running the command: `mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]`
6. Change the `$wgDBname` variable in the `LocalSettings.php` file of the new directory to the new database name
7. From the new capipedia version directory, run the command: `php maintenance/run.php update`

== Switch the production hostname to the new site ==

1. From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**Manage Websites**/**Settings**/**Directories: Modify** and change the root web directory to the new version
2. Wait for **Updating Web Options...** to complete
3. Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
4. Place production site back in write mode by commenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the new directory
4. Check that the following operations work as expected:

a. Viewing pages
b. Editing pages
c. Uploading a file

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T15:20:19Z

NMcLarty27:

* Test the new version deployment prior to upgrading in production

1. Download and uncompress the new version's distribution from mediawiki.org
2. Run the `refresh-sandbox.sh` script from the user home directory
3. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* sandbox.capmembers.wiki`
4. From the `sandbox.capmembers.wiki` directory, run the command: `php maintenance/run.php update`
5. Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
6. Check that the following operations work as expected:

a. Viewing pages
b. Editing pages
c. Uploading a file

* Backup the production site

1. Place production site in read only mode by uncommenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the old directory
2. Return to the user home directory
3. Run `backup-prod.sh`

* Create a new production site

1. Duplicate the production folder using the command: `cp -pR capipedia-[old_version] capipedia-[new_version]`
2. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* capipedia-[new_version]`
3. From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**MySQL Databases**
4. Create a new database with a database name that matches the new directory name and new username of `cap_wiki_root`
5. Upload the backup database file to the database by running the command: `mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]`
6. Change the `$wgDBname` variable in the `LocalSettings.php` file of the new directory to the new database name
7. From the new capipedia version directory, run the command: `php maintenance/run.php update`

* Switch the production hostname to the new site

1. From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**Manage Websites**/**Settings**/**Directories: Modify** and change the root web directory to the new version
2. Wait for **Updating Web Options...** to complete
3. Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
4. Place production site back in write mode by commenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the new directory
4. Check that the following operations work as expected:

a. Viewing pages
b. Editing pages
c. Uploading a file

CAPipedia Sandbox:Updating CAPipedia

2025-04-16T15:19:28Z

NMcLarty27: Created page with "# Test the new version deployment prior to upgrading in production 1. Download and uncompress the new version's distribution from mediawiki.org 2. Run the `refresh-sandbox.sh` script from the user home directory 3. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* sandbox.capmembers.wiki` 4. From the `sandbox.capmembers.wiki` directory, run the command: `php maintenance/run.php update` 5. Browse to https://sandbox.capmembers.wiki/wiki/Speci..."

# Test the new version deployment prior to upgrading in production

1. Download and uncompress the new version's distribution from mediawiki.org
2. Run the `refresh-sandbox.sh` script from the user home directory
3. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* sandbox.capmembers.wiki`
4. From the `sandbox.capmembers.wiki` directory, run the command: `php maintenance/run.php update`
5. Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
6. Check that the following operations work as expected:

* Viewing pages
* Editing pages
* Uploading a file

# Backup the production site

1. Place production site in read only mode by uncommenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the old directory
2. Return to the user home directory
3. Run `backup-prod.sh`

# Create a new production site

1. Duplicate the production folder using the command: `cp -pR capipedia-[old_version] capipedia-[new_version]`
2. Replace the distribution files using the command: `cp -pR mediawiki-[version]/* capipedia-[new_version]`
3. From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**MySQL Databases**
4. Create a new database with a database name that matches the new directory name and new username of `cap_wiki_root`
5. Upload the backup database file to the database by running the command: `mysql -ucap_wiki_root -p -hmysql.sandbox.capmembers.wiki [new_db_name] < [backup_sql_file]`
6. Change the `$wgDBname` variable in the `LocalSettings.php` file of the new directory to the new database name
7. From the new capipedia version directory, run the command: `php maintenance/run.php update`

# Switch the production hostname to the new site

1. From the [https://panel.dreamhost.com DreamHost Web Panel], browse to **Websites**/**Manage Websites**/**Settings**/**Directories: Modify** and change the root web directory to the new version
2. Wait for **Updating Web Options...** to complete
3. Browse to https://sandbox.capmembers.wiki/wiki/Special:Version and verify the upgrade took effect and the page fully loads without errors
4. Place production site back in write mode by commenting the `$wgReadOnly` variable in the `LocalSettings.php` file of the new directory
4. Check that the following operations work as expected:

* Viewing pages
* Editing pages
* Uploading a file

Main Page

2025-04-09T22:10:55Z

NMcLarty27:

{{Colored box
| title=Welcome to {{SITENAME}}
| center=true
| content=
{{SITENAME}}'s purpose is to benefit members by acting as an encyclopedia and index to [[eServices]], [[WMIRS]] and everything CAP. It is a work in progress.

To add or edit pages, you will need to create an account or log in to your existing account and be a member of Civil Air Patrol. For access to edit, click [[Special:RequestAccount|Request Account]] and fill out the request. In the '''Other Information''' section, enter your CAPID, Region, Wing and Unit. The account will be approved as soon as possible.

If you have any issues, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use {{SITENAME}}
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

TIPS Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}

Main Page

2025-03-30T00:33:16Z

NMcLarty27: Changed protection settings for "Main Page" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

{{Colored box
| title=Welcome to CAPipedia
| center=true
| content=
CAPipedia's purpose is to benefit members by acting as an encyclopedia and index to [[eServices]], [[WMIRS]] and everything CAP. It is a work in progress.

To add or edit pages, you will need to create an account or log in to your existing account and be a member of Civil Air Patrol. For access to edit, click [[Special:RequestAccount|Request Account]] and fill out the request. In the '''Other Information''' section, enter your CAPID, Region, Wing and Unit. The account will be approved as soon as possible.

If you have any issues, please submit a [https://forms.gle/iVjqFSaqnb5fAwZv6 Contact Form].
}}
{{Colored box
| title=Active Projects / Help Needed
| title-color=#fff
| background-title-color=#36c
| background-content-color=#eaf3ff
| content=
* Reviewing migrated content from the CAP Knowledgebase. See the [[Category talk:CAP Knowledgebase cleanup|discussion page for CAP Knowledgebase cleanup]] for more information.
* Adding best practices content to pages in the [[:Category:Functional areas|functional areas category]].
* Adding descriptions and external links to [[:Category:Specialty tracks|specialty track pages]].
}}
{{Flex columns
|1=
{{Colored box
| title=Quick Links
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [https://www.capnhq.gov eServices]
* [[:Category:FAQ|FAQs]] (formerly CAP Knowledgebase)
* [https://www.capnhq.gov/WMIRS/Default.aspx WMIRS]
* [https://staging.capnhq.gov Staging (Test) eServices]
* [https://www.gocivilairpatrol.com Go Civil Air Patrol]
}}
{{Colored box
| title=Getting Started
| flex=0 1 100%
| background-title-color=#cef2e0
| background-content-color=#f5fffa
| content=
* [[CAPipedia Style Guide]]
* [//www.mediawiki.org/wiki/Help:Starting_a_new_page Starting a New Page]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
}}
|2={{Colored box
| title=Latest Updates
| background-title-color=#cedff2
| background-content-color=#f5faff
| content=
* Migrated [[:Category:FAQ|FAQs]] from the CAP Knowledgebase
* Created [[:Category:Specialty tracks|specialty track]] and [[:Category:Functional areas|functional area]] info pages
* Added [[Template:Pub/doc|{{code|<nowiki>{{Pub}}</nowiki>}}]] and [[Template:Form/doc|{{code|<nowiki>{{Form}}</nowiki>}}]] templates to hyperlink to the correct page where the pub/form is listed
}}
}}
{{Colored box
| title=How to Use CAPipedia
| content=
The search box in the upper right hand corner is your avenue to finding information. Use keywords to search. If too many options come back, then you can add more search words. All the pages that match have a link to click on.

TIPS Avoid short and common words This is the most likely cause of an unexpected failed search. If your search terms include a common "stop word" (such as "the", "one", "your", "more", "right", "while", "when", "who", "which", "such", "every", "about", "onto"), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search.
Search is case-insensitive The searches for "fortran", "Fortran" and "FORTRAN" all return the same results.

Search Examples: How do I change my password? You want to type change password in the search box.

[[Special:AllPages|See a list of all pages in the Wiki]]

The search results are always listed below an option to create a page. Don't create a page unless the results you are looking for is not found.
}}
{{Colored box
| title=Recent Changes
| content=
{{Special:RecentChanges/days=5,limit=10,hidebots,hideminor}}
}}