ARISS Website Redesign & Integration
Budget: $5,000 – $10,000 USD
Overview:
This project is to update Amateur Radio on the International Space Station (ARISS) Website/ ARISS lets students worldwide experience the excitement of talking directly with crew members of the International Space Station, inspiring them to pursue interests in careers in science, technology, engineering and math, and engaging them with radio science technology through amateur radio. The ARISS program
was created and is managed by an international consortium of amateur radio
organizations and space agencies. ARISS-USA is a 501.c.3 organization.
Project Goals:
Phase 1: To redesign the ARISS.org family of webpages, resulting in ease of
navigation, consolidation of material (write once, publish many places),
consolidation of back-end hosting.
Phase 2: Integrate existing functionality (Operations site), develop new
features (Educators site) and global sites (Europe, Canada, Asia) into the
platform infrastructure.
Proposal Requirements:
• Identify costs per phase
• Publish Phase 1 by March 30, 2025
Websites in scope:
A. Phase 1. ARISS.org ARISS-USA.org
B. Phase 2. ARISS Ops site on AMSAT.org (private), ARISS SSTV
Gallery (https://www.spaceflightsoftware.com/ARISS_SSTV/), ARISS
Europe (https://www.ariss-eu.org/), live.ariss.org, ARISS Engineering
site, future education site. Additional sites TBD.
Functionality:
A. Terms:
“Must” - required for minimum completion of proposal.
“Should” - expected to be included unless significant barriers impact
completion.
“May” - can be included as practical but have the option to move to a
later phase of the project.
B. Infrastructure / Back end
a. ARISS.org, ARISS-USA.org must be hosted by the same
infrastructure and use the same content management system
(CMS) at the end of Phase 1. These are public sites.
b. ARISS Operations site (URL to be provided to successful
proposal) must be integrated at the end of Phase 2. This is a
private site to be password protected with individual access
levels (moderator, editor, user).
c. ARISS Educator Site (New) must be integrated by the end of
Phase 2. This is a private site to be password protected with
individual access levels (moderator, editor, user).
d. ARISS SSTV Gallery
(https://www.spaceflightsoftware.com/ARISS_SSTV/) should be
integrated by the end of phase 2. This is a public site with a
private moderator back-end.
e. ARISS-EU.org and additional international sites may be
integrated by the end of phase 2. These are public sites.
f. The site must use a common CMS, such as WordPress.
i. CMS consideration should be placed on ease of volunteer
use. Most will not be highly technical in web languages or
HTML.
ii. ARISS currently uses a combination of WordPress and
Weebly. Weebly should not be considered for this project.
iii. Consideration should be made for future plugins to allow
dynamic updating of sites. Those plug-ins might include AI
or other tools and elements.
g. The site must allow for additional URL’s and expansion.
i. Example: ARISS may wish to spin off Lunar Gateway
discussions into a future AREx site.
h. The site must include a modern analytics dashboard / suite to
allow for usage data and tuning of content.
i. Main metrics should be visible from a single page.
ii. Some metrics views should be able to be delegated to
editors.
iii. Example: Feature Heat Maps and Click-Through paths
iv. Google Analytics integration compatible
i. The site must allow for regular updates of security protocols and
software to protect user data and prevent cyber threats.
j. The site must use a proven authentication method such as
Microsoft Authenticator, Google Authenticator, or RSA. This
applies to administrators and editor level access.
i. New users need to create a login and password and be
validated (e-mail reply with code, prevent hacking and
updating passwords if user forgets)
C. Web Design / Front End
a. Terms: “The Site” refers to the ARISS.org and ARISS-USA.org
public sites unless otherwise indicated.
b. An overview of the multiple site-flows will be included later in
this document.
c. Phase 1
i. A modern design with simple-to-use integration must be
provided.
ii. The site must be compatible with top
desktop/tablet/mobile web browsers. Google Chrome,
Safari, Microsoft Edge currently are identified.
iii. The site must have clear and consistent “streamlined”
navigation for easy access to key sections.
1. This includes clear call-to-action areas like
“participate” or “learn more about ARISS”
2. The navigation should integrate links to ARISS social
media sites.
iv. The site must allow for material to be composed once and
published across multiple URL’s
1. The site must have an approval workflow between
administrators, editors and writers that may be
delegated before publishing.
2. Example: A paragraph referencing a NASA STEM
program must appear on ARISS.org and ARISSUSA.org without being re-written or published
multiple times.
3. The site should offer simple composition tools for
editors.
v. The site must allow for “on the fly” language translation to
accommodate the worldwide nature of ARISS.
1. Example: Content will likely be produced in English
which is the “language” of the ISS. Functionality
should exist on page to allow the content to be
translated to other languages.
2. Translations should be offered for Spanish, French,
Italian, Russian, and Japanese
vi. The site must be search engine optimized
vii. The site must have a robust on-site search as part of its
navigation
viii. The site must be GPDR/PII compliant and comply with
additional global regulations. This includes Cookie usage /
storage data.
ix. The site must be compliant with the Web 2 WCAG
guidelines (https://www.w3.org/WAI/standardsguidelines/wcag/) for accessibility.
x. The site should geotarget information based on a user's
chosen or IP detected region.
1. Example: A user accessing from Germany should see
information regarding ARISS-EU processes while
someone from Cleveland should see ARISS-USA
related material.
xi. The site should allow regional partners to be featured.
1. Example: NASA in the US, ESA in Europe.
2. Example: ARRL in the US, RAC in Canada
3. Other content should be available, just not prioritized
/ featured.
xii. During the transition, the site must maintain and support
the content level currently in place. This is a “do no harm”
approach to integrating existing content.
1. Integrate existing content
xiii. The site should allow for additional content such as import
of social media feeds, news articles and other features.
xiv. The site must allow for e-commerce functionality as it
relates to gathering donations.
xv. The site should allow for e-commerce integration as it
relates to merchandise sales or event ticketing. This could
be integration with a site like Shopify.
xvi. The site must allow for use of common web languages
including the latest HTML version, as well as Java Script,
python, PhP, Ruby, C#, Go, Swift. This should be aligned
with C.C.ii above to ensure browser support.
Responses to ARISS Website Phase 1 RFP are due by November 10, 2024, by 5 PM EST USA.
This project is to update Amateur Radio on the International Space Station (ARISS) Website/ ARISS lets students worldwide experience the excitement of talking directly with crew members of the International Space Station, inspiring them to pursue interests in careers in science, technology, engineering and math, and engaging them with radio science technology through amateur radio. The ARISS program
was created and is managed by an international consortium of amateur radio
organizations and space agencies. ARISS-USA is a 501.c.3 organization.
Project Goals:
Phase 1: To redesign the ARISS.org family of webpages, resulting in ease of
navigation, consolidation of material (write once, publish many places),
consolidation of back-end hosting.
Phase 2: Integrate existing functionality (Operations site), develop new
features (Educators site) and global sites (Europe, Canada, Asia) into the
platform infrastructure.
Proposal Requirements:
• Identify costs per phase
• Publish Phase 1 by March 30, 2025
Websites in scope:
A. Phase 1. ARISS.org ARISS-USA.org
B. Phase 2. ARISS Ops site on AMSAT.org (private), ARISS SSTV
Gallery (https://www.spaceflightsoftware.com/ARISS_SSTV/), ARISS
Europe (https://www.ariss-eu.org/), live.ariss.org, ARISS Engineering
site, future education site. Additional sites TBD.
Functionality:
A. Terms:
“Must” - required for minimum completion of proposal.
“Should” - expected to be included unless significant barriers impact
completion.
“May” - can be included as practical but have the option to move to a
later phase of the project.
B. Infrastructure / Back end
a. ARISS.org, ARISS-USA.org must be hosted by the same
infrastructure and use the same content management system
(CMS) at the end of Phase 1. These are public sites.
b. ARISS Operations site (URL to be provided to successful
proposal) must be integrated at the end of Phase 2. This is a
private site to be password protected with individual access
levels (moderator, editor, user).
c. ARISS Educator Site (New) must be integrated by the end of
Phase 2. This is a private site to be password protected with
individual access levels (moderator, editor, user).
d. ARISS SSTV Gallery
(https://www.spaceflightsoftware.com/ARISS_SSTV/) should be
integrated by the end of phase 2. This is a public site with a
private moderator back-end.
e. ARISS-EU.org and additional international sites may be
integrated by the end of phase 2. These are public sites.
f. The site must use a common CMS, such as WordPress.
i. CMS consideration should be placed on ease of volunteer
use. Most will not be highly technical in web languages or
HTML.
ii. ARISS currently uses a combination of WordPress and
Weebly. Weebly should not be considered for this project.
iii. Consideration should be made for future plugins to allow
dynamic updating of sites. Those plug-ins might include AI
or other tools and elements.
g. The site must allow for additional URL’s and expansion.
i. Example: ARISS may wish to spin off Lunar Gateway
discussions into a future AREx site.
h. The site must include a modern analytics dashboard / suite to
allow for usage data and tuning of content.
i. Main metrics should be visible from a single page.
ii. Some metrics views should be able to be delegated to
editors.
iii. Example: Feature Heat Maps and Click-Through paths
iv. Google Analytics integration compatible
i. The site must allow for regular updates of security protocols and
software to protect user data and prevent cyber threats.
j. The site must use a proven authentication method such as
Microsoft Authenticator, Google Authenticator, or RSA. This
applies to administrators and editor level access.
i. New users need to create a login and password and be
validated (e-mail reply with code, prevent hacking and
updating passwords if user forgets)
C. Web Design / Front End
a. Terms: “The Site” refers to the ARISS.org and ARISS-USA.org
public sites unless otherwise indicated.
b. An overview of the multiple site-flows will be included later in
this document.
c. Phase 1
i. A modern design with simple-to-use integration must be
provided.
ii. The site must be compatible with top
desktop/tablet/mobile web browsers. Google Chrome,
Safari, Microsoft Edge currently are identified.
iii. The site must have clear and consistent “streamlined”
navigation for easy access to key sections.
1. This includes clear call-to-action areas like
“participate” or “learn more about ARISS”
2. The navigation should integrate links to ARISS social
media sites.
iv. The site must allow for material to be composed once and
published across multiple URL’s
1. The site must have an approval workflow between
administrators, editors and writers that may be
delegated before publishing.
2. Example: A paragraph referencing a NASA STEM
program must appear on ARISS.org and ARISSUSA.org without being re-written or published
multiple times.
3. The site should offer simple composition tools for
editors.
v. The site must allow for “on the fly” language translation to
accommodate the worldwide nature of ARISS.
1. Example: Content will likely be produced in English
which is the “language” of the ISS. Functionality
should exist on page to allow the content to be
translated to other languages.
2. Translations should be offered for Spanish, French,
Italian, Russian, and Japanese
vi. The site must be search engine optimized
vii. The site must have a robust on-site search as part of its
navigation
viii. The site must be GPDR/PII compliant and comply with
additional global regulations. This includes Cookie usage /
storage data.
ix. The site must be compliant with the Web 2 WCAG
guidelines (https://www.w3.org/WAI/standardsguidelines/wcag/) for accessibility.
x. The site should geotarget information based on a user's
chosen or IP detected region.
1. Example: A user accessing from Germany should see
information regarding ARISS-EU processes while
someone from Cleveland should see ARISS-USA
related material.
xi. The site should allow regional partners to be featured.
1. Example: NASA in the US, ESA in Europe.
2. Example: ARRL in the US, RAC in Canada
3. Other content should be available, just not prioritized
/ featured.
xii. During the transition, the site must maintain and support
the content level currently in place. This is a “do no harm”
approach to integrating existing content.
1. Integrate existing content
xiii. The site should allow for additional content such as import
of social media feeds, news articles and other features.
xiv. The site must allow for e-commerce functionality as it
relates to gathering donations.
xv. The site should allow for e-commerce integration as it
relates to merchandise sales or event ticketing. This could
be integration with a site like Shopify.
xvi. The site must allow for use of common web languages
including the latest HTML version, as well as Java Script,
python, PhP, Ruby, C#, Go, Swift. This should be aligned
with C.C.ii above to ensure browser support.
Responses to ARISS Website Phase 1 RFP are due by November 10, 2024, by 5 PM EST USA.