diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
index 5aff6c8b60e2a283846c3042df1a158fd2614999..42ffa68a09a9056885de9a9baa3a94a3c19b7fb1 100644
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -52,4 +52,4 @@ jobs:
           aws-region: us-west-2
       
       - name: Upload to S3
-        run: aws s3 sync ./public/ s3://asc-docs/foundationaldataproducts/ --delete
+        run: aws s3 sync ./public/ s3://asc-docs/planetary-sdi/ --delete
diff --git a/content/PlanetarySDIs/about.md b/content/PlanetarySDIs/about.md
index e4abb6cdd3502fc07bb3affc8405a1ede7d355a3..b2f22b3f99d4a069e33ec488f841a9bb9f3ee744 100644
--- a/content/PlanetarySDIs/about.md
+++ b/content/PlanetarySDIs/about.md
@@ -3,6 +3,4 @@ title: What are Planetary SDIs?
 weight: 1
 ---
 
-High level.
-
-{{ partial "lastmod.html" . }}
\ No newline at end of file
+High level.
\ No newline at end of file
diff --git a/content/europa/_index.md b/content/europa/_index.md
index 81e61eb709cdf900da89536dbc6e32ae59774d92..b35c0e5d9511772867233d04bc97d5efb708137c 100644
--- a/content/europa/_index.md
+++ b/content/europa/_index.md
@@ -1,4 +1,4 @@
 ---
 geekdocCollapseSection: true
-weight: 30
+weight: 2
 ---
\ No newline at end of file
diff --git a/content/europa/data/data_products.md b/content/europa/data/data_products.md
index af41f0bd0dd22e047412f6b2d0ad675d660fa57d..d7435799949842dfd88aa994aba4161ee6e76874 100644
--- a/content/europa/data/data_products.md
+++ b/content/europa/data/data_products.md
@@ -3,4 +3,4 @@ title: ESDI Compliant Data Products
 weight: 31.1
 ---
 
-Governance Docs
\ No newline at end of file
+The ESDI maintains a list of known, compliant data products. We would like to bring additional products into the ESDI.
\ No newline at end of file
diff --git a/content/europa/data/data_services.md b/content/europa/data/data_services.md
index 25c016d0eb5d1629e3434941e49f0d084db022e7..d8a10224f9390939973fa2c2d0c8ddc921421a1a 100644
--- a/content/europa/data/data_services.md
+++ b/content/europa/data/data_services.md
@@ -3,4 +3,6 @@ title: ESDI Compliant Data Services
 weight: 31.1
 ---
 
-Governance Docs
\ No newline at end of file
+What compliant data services exist?
+
+This is right at the edge of a clearinghouse, so maybe we just accept that and instead of trying ot maintain a static list, we just embed a portal right here?
\ No newline at end of file
diff --git a/content/europa/get_involved.md b/content/europa/get_involved.md
index 6b854389f614b80a84d38799264170ff4578529c..bbdc66d1b17b1e53c3f407980e902ed6e03ff71c 100644
--- a/content/europa/get_involved.md
+++ b/content/europa/get_involved.md
@@ -1,6 +1,6 @@
 ---
 title: Get Involved
-weight: 2
+weight: 1
 ---
 
 {{< tabs "esdi_involved_how" >}}
@@ -16,8 +16,14 @@ If you have Europa data or are interested in creating new derived products, this
 If you run a server or a data clearing house and would like to make ESDI compliant data available, this is the place to start.
 {{< /tab >}}
 
-{{< tab "Evangalizers" >}}
+{{< tab "ESDI Evangalizers" >}}
 ## Who is this section for?
 If you are excited about Europa spatial data, metadata, standards, and/or data analysis, **and** you like to communicate with others about how you are using your skills, this is the place to start.
 
+{{< /tabs >}}
+
+{{< tab "Data Users" >}}
+## Who is this section for?
+If you are a data user and you need help using products within the ESDI, this is the place to start.
+
 {{< /tabs >}}
\ No newline at end of file
diff --git a/content/europa/governance/_index.md b/content/europa/governance/_index.md
index 37b2b8c1e3600156527f21c64276f3dc6d2d18d7..b35c0e5d9511772867233d04bc97d5efb708137c 100644
--- a/content/europa/governance/_index.md
+++ b/content/europa/governance/_index.md
@@ -1,4 +1,4 @@
 ---
 geekdocCollapseSection: true
-weight: 1
+weight: 2
 ---
\ No newline at end of file
diff --git a/content/europa/governance/charter.md b/content/europa/governance/charter.md
index 699ca4f0769f94427ea040f7989e9b945eb1f016..d8c68ac618b0d166b6a5156bdd8d0a128c4cd45b 100644
--- a/content/europa/governance/charter.md
+++ b/content/europa/governance/charter.md
@@ -9,11 +9,11 @@ The Europa Spatial Data Infrastructure team will evaluate existing spatial data
 Publish and steward the policy infrastructure necessary to maintain this SDI including this charter, memorandums of understanding to support data release and sharing agreements, and a roadmap map of future development.
 
 Engage with the user community, funding agencies, and NASA Advisory Groups to ensure the efforts of this body maximally align with targeted user community needs.
-    - Publish and steward the policy infrastructure necessary to maintain this SDI, including a charter, governance documentation, memorandums of understanding to support data release and sharing agreements, and a roadmap of future development.
-    - Engage with the user community, funding agencies, and NASA Advisory Groups to ensure the efforts of this body maximally align with targeted user community needs.
-    - Publish an initial set of standards that will define this SDI including standardized vertical and horizontal datums (i.e., the coordinate system), accepted map projections, interoperable data formats, and metadata formats.
-    - Maintain, in conjunction with the Europa community, a living inventory of foundational and framework data products including quantitative (e.g., positional accuracy, resolution, data producer) and qualitative (e.g., fitness-for-use) metadata. This includes setting a standard for metadata to be reported for all data products managed under the Europa SDI organization.
-    - Provide a mechanism to link users, such as data creators (who make the data products), custodians (who manage the data products lifecycle), and data integrators (who provide the data to end users) to create an interconnected user group.
-    - Support (through policies and standards) the development of data discovery and access portals making use of Europa SDI managed data and associated Application Programming Interfaces (APIs).
-    - Ensure the public release of all Europa SDI managed data products and APIs.
-    - Engage with tool developers to ensure support for data and standards included in the Europa SDI.
+- Publish and steward the policy infrastructure necessary to maintain this SDI, including a charter, governance documentation, memorandums of understanding to support data release and sharing agreements, and a roadmap of future development.
+- Engage with the user community, funding agencies, and NASA Advisory Groups to ensure the efforts of this body maximally align with targeted user community needs.
+- Publish an initial set of standards that will define this SDI including standardized vertical and horizontal datums (i.e., the coordinate system), accepted map projections, interoperable data formats, and metadata formats.
+- Maintain, in conjunction with the Europa community, a living inventory of foundational and framework data products including quantitative (e.g., positional accuracy, resolution, data producer) and qualitative (e.g., fitness-for-use) metadata. This includes setting a standard for metadata to be reported for all data products managed under the Europa SDI organization.
+- Provide a mechanism to link users, such as data creators (who make the data products), custodians (who manage the data products lifecycle), and data integrators (who provide the data to end users) to create an interconnected user group.
+- Support (through policies and standards) the development of data discovery and access portals making use of Europa SDI managed data and associated Application Programming Interfaces (APIs).
+- Ensure the public release of all Europa SDI managed data products and APIs.
+- Engage with tool developers to ensure support for data and standards included in the Europa SDI.
diff --git a/content/europa/roadmap.md b/content/europa/roadmap.md
deleted file mode 100644
index 827f61c1e74384064309d72293b4a0a6af9cc800..0000000000000000000000000000000000000000
--- a/content/europa/roadmap.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Road Map
-weight: 2
----
-
-LTP.
\ No newline at end of file
diff --git a/content/europa/standards/cartographic_standards.md b/content/europa/standards/cartographic_standards.md
new file mode 100644
index 0000000000000000000000000000000000000000..7fd82abcd95f9418fbea20cda94d44eeda2e8e91
--- /dev/null
+++ b/content/europa/standards/cartographic_standards.md
@@ -0,0 +1,7 @@
+---
+title: Cartographic Standards
+weight: 51
+---
+
+The ESDI does not currently identify any cartographic standards. The group would welcome proposals to adopt consistent cartographic standards such as standardized cartographic symbology or standardized color ramps for particular data use cases.
+
diff --git a/content/europa/standards/data_formats.md b/content/europa/standards/data_formats.md
new file mode 100644
index 0000000000000000000000000000000000000000..35f9ee3daa8722930bd2c414ef5232e9e2e722cf
--- /dev/null
+++ b/content/europa/standards/data_formats.md
@@ -0,0 +1,15 @@
+---
+title: Data Format Standards
+weight: 60
+---
+
+### Formats for Offline Data Access
+- Data in raster format will be provided as [cloud optimized GeoTiffs](https://www.cogeo.org)(COG), complying with the above projection standards. 
+- Data in vector format will be provided in [OGC GeoPackage format](https://www.geopackage.org) with information stored in decimal degrees (i.e., no map projection applied)
+
+
+### Formats for Online Data Access
+- Data in raster format can be provided as [cloud optimized GeoTiffs](https://www.cogeo.org), complying with the above projection standards. These data will be accessed via their [STAC](https://www.google.com/search?client=safari&rls=en&q=spatio-temporal+asset+catalog&ie=UTF-8&oe=UTF-8) data files.
+- Data in raster format can be provided using OGC compliant WMS service. Said service must encode a proper IAU 2015 projection code.
+- Data in vector format can be served using an OCG compliant WFS or WMTS service using the standards defined above. The server must encode a proper IAU 2015 projection code.
+- The STAC-API specification (a remotely accessible search service) will be used to support metadata query and data discoverability. 
diff --git a/content/europa/standards/data_standards.md b/content/europa/standards/data_standards.md
index ba3afe3f2de43afcc447504e59aa10b8a0eed7d4..eec297c82fb7505e4b7b6b1efe478c028fc61e89 100644
--- a/content/europa/standards/data_standards.md
+++ b/content/europa/standards/data_standards.md
@@ -1,6 +1,20 @@
 ---
-title: Data Interoperability Standards
-weight: 31.1
+title: Spatial Standards
+weight: 50
 ---
 
-Governance Docs
\ No newline at end of file
+### Body Parameters
+- The Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements: 2015 (2018) body parameters will be used. This includes a sphere radius of 1560.8km and rotation parameters as defined in Table 2 (Archinal, et al., 2018).
+
+### Horizontal and Vertical Datum
+- No consistent mean sea level is currently definable for Europa. Therefore, no single vertical datum can be defined. All elevation data are, at this time, assessed for relative, internal, consistency an accuracy as absolute accuracy assessment is not possible without a vertical datum.
+- The origin of horizontal datum to be used is defined by the IAU as 182˚ East longitude, 0˚ planetocentric latitude. For maximum usability, we encourage data creators to register data sets (either rigorously or using rubber sheeting techniques; with appropriate documentation) to the Schenk/USGS basemap.
+
+### Map Projections
+- Data are provided in a simple cylindrical (equirectangular) map projection.
+- Data are orthorectified to a sphere using the IAU mean radius => 1560.8 km (sphere)
+- Data are made available in a 0 – 360 Positive East coordinate system with a center longitude of 180 degrees and use planetocentric latitude. 
+- For observational data, pixel scale or resolution should be maintained at native scale, (i.e., do not up sample or down sample data.)
+- For derived data (e.g., DTMs), data should be made available at a reasonable resolution that avoids extrapolation of information.
+- Data for large spatial scale (e.g., 1:24000), small spatial extent maps, (e.g. landing sites) can be provided in an orthographic projection centered on image.
+- Data for polar areas (latitudes > 55˚ North or South) should use an orthographic projection centered on site or a polar stereographic projection centered at the pole
diff --git a/content/europa/standards/metadata_standards.md b/content/europa/standards/metadata_standards.md
new file mode 100644
index 0000000000000000000000000000000000000000..3876878eb233287890c1741337f7306bd57dec3a
--- /dev/null
+++ b/content/europa/standards/metadata_standards.md
@@ -0,0 +1,16 @@
+---
+title: Metadata Standards
+weight: 70
+---
+
+### Metadata Content
+- Data will have qualitative process and usability information available in text format that describes (1) a description of the data set, (2) the process used to create the data, (3) the available assets or files within a data set, (4) the accuracy, errors, and identification of known issues with the data set, (5) the qualitative usability of the data set (as mediated by the data provider or steward), (6) textual description of the proposed update cadence for this data set, and (7) optionally textual links to other data sets of potential interest to users of this data set.
+- 
+### Accuracy Descriptions
+- Accuracy should be described using the [ISO 19157:2013 standard](https://wiki.icaci.org/index.php?title=ISO_19157:2013_Geographic_information_-_Data_quality). 
+
+### File Formats
+- Data will have an FGDC compliant XML metadata file. This file is to be as compliant as possible and should use the planetary domain extension.
+- Data will have a Spatio-Temporal Asset Catalog (STAC) metadata JSON file.
+- Data should have a provenance file that minimally describes the creation of the data. When possible, the provenance file will support complete reproduction of a derived data product by replicating commands provided to processing tools.
+
diff --git a/content/europa/standards/spatial_standards.md b/content/europa/standards/spatial_standards.md
deleted file mode 100644
index 6bfcda18fa8bd716403de7cc76e8ead327f3a943..0000000000000000000000000000000000000000
--- a/content/europa/standards/spatial_standards.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Spatial Standards
-weight: 31.0
----
-
-Governance Docs
\ No newline at end of file
diff --git a/content/europa/strategy/_index.md b/content/europa/strategy/_index.md
new file mode 100644
index 0000000000000000000000000000000000000000..61d398a053b9a01da21965530c12bbfcfd95fdc3
--- /dev/null
+++ b/content/europa/strategy/_index.md
@@ -0,0 +1,5 @@
+---
+title: "Strategy & Roadmap"
+geekdocCollapseSection: true
+weight: 10
+---
\ No newline at end of file
diff --git a/content/europa/strategy/roadmap.md b/content/europa/strategy/roadmap.md
new file mode 100644
index 0000000000000000000000000000000000000000..cd09861be20da7b71f8d7809aae549e57a7b4c84
--- /dev/null
+++ b/content/europa/strategy/roadmap.md
@@ -0,0 +1,164 @@
+---
+title: "Roadmap"
+weight: 2
+---
+
+## Performance Indicators
+Several performance indicators will be measured over the time period from 2022 to 2025 to gauge the effectiveness of the implementation of the Europa SDI Strategic Plan, as well as the effectiveness of the Europa SDI itself. These efforts will be measured, assessed and tracked annually over the 2022-2025 timeframe with regular reports publicly available.
+ 
+Performance indicators will include qualitative or quantitative metrics on: 
+- Relevance of Europa SDI reference and thematic data to users 
+- The use of the Europa SDI Geoportal, web services, and metadata 
+- User satisfaction of reference and thematic data and services 
+- Known applications based on the Europa SDI and their relevance 
+- Europa SDI policies and standards influence on the development of other NASA SDIs and/or other relevant management policies
+
+## Objectives and Anticipated Outcomes
+
+This plan contains information regarding how the strategic objectives will be implemented within the Europa SDI including the anticipated outcomes, approach, and a table of actions including a general timeline. 
+ 
+### Objective 1
+Publish and steward the policy infrastructure necessary to maintain this SDI, including a charter, governance documentation, memorandums of understanding to support data release and sharing agreements, and a roadmap of future development.
+
+#### Anticipated Outcomes
+Publishing and maintaining a policy infrastructure is one of the primary tenants of a Spatial Data Infrastructure (e.g., Laura et al., 2018; Rajabifard et al., 2002), and facilitates communication within the community, coordination between stakeholders, communicates expectations both of the SDI and from participating groups, and establishes efforts for the long-term maintenance of this infrastructure.
+
+#### Approach
+The primary approach includes writing documentation that describes 1) the Europa SDI charter, 2) governance policy documentation; 3) strategic direction and a 4-year roadmap; and 4) a memorandum of understanding. These documents will be drafted by Europa SDI working group members and reviewed collectively. We will seek group consensus regarding all governance and strategy decisions. These documents will also be posted on a publicly available website so that members of the Europa community can also comment and provide feedback. 
+
+#### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|1.1	|Write and publish the Europa SDI Charter	|Completed. This charter has been endorsed by MAPSIT.|
+|1.2	|Write and publish the governance documentation	|Completed in 2022.|
+|1.3	|Write and publish the strategic direction and 4-year roadmap (this document)	|Completed in 2022.|
+|1.4	|Write and publish the memorandum of understanding	|This document is under development and in collaboration with NASA and the USGS.|
+
+
+### Objective 2
+Engage with the user community, funding agencies, and NASA Advisory Groups to ensure the efforts of this body maximally align with targeted user community needs.
+ 
+#### Anticipated Outcomes
+Engaging a broad range of Europa data users will help to ensure that our efforts strategically align with the needs of the community and will also inform this community of our efforts. In this way, potential users can learn of available data and future planned additions, while also providing opportunities to stay in step with the evolving needs of data users. The feedback we receive from users will help to inform current and future efforts and SDI direction.
+
+#### Approach
+We will initially engage high-level stakeholders, including NASA, MAPSIT, and OPAG, to ensure that this working group is addressing a widely recognized need in the community. We will also engage the Europa Clipper mission team to communicate the efforts of this group, seek collaborative engagement, and ensure that our efforts are supportive and not redundant to Europa Clipper team efforts. We will also engage the planetary science community at annual meetings to obtain feedback on our efforts and collaborate with other interested groups. This approach helps us to initially understand the needs of scientists, engineers, mission teams, and software and tool developers. We will then build on this understanding to inform future work to serve the larger community of users and stakeholders, which in addition to the above groups include (but are not limited to) media relation activities, public engagement and education groups, and members of the general public. By engaging the Europa data community through many different avenues, we aim to intersect and meet the data use needs of the broadest group possible.
+
+#### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|2.1	|Engage NASA to ensure this effort is supportive of strategic direction and community needs and provide regular updates.	|Ongoing. This effort directly addresses needs expressed in the Planetary Data Ecosystem IRB Findings; we provide annual updates to NASA Program Managers.|
+|2.2	|Engage the Mapping and Planetary Spatial Infrastructure Team (MAPSIT) to communicate the efforts of this group.	|Ongoing. Received an endorsement of our charter and an invitation to present our efforts at future MAPSIT meetings.|
+|2.3	|Engage the Outer Planets Assessment Group (OPAG) to communicate the efforts of this group.	|Ongoing. Received with interest and an invitation to present our efforts at future OPAG meetings.|
+|2.4	|Engage the Europa Clipper mission team to communicate the efforts of this group and work to establish a cooperative relationship that supports community needs.	|Ongoing. Presented efforts to the Europa Clipper Geology Thematic Working group on January 10, 2022, with interest for continued discussions.|
+|2.5	|Present the efforts of this group at relevant community meetings, such as the Lunar and Planetary Science Conference (LPSC) and the American Astronomical Society Division of Planetary Science (DPS) meetings.	|Ongoing. Submitted an abstract describing these efforts to the 2022 LPSC meeting (Laura et al., 2022).|
+|2.6	|Engage tool developers to communicate the efforts of this group.	|Future effort|
+
+### Objective 3 
+Publish an initial set of standards that will define this SDI including standardized vertical and horizontal datums (i.e, the coordinate system), accepted map projections, interoperable data formats, and metadata formats.
+
+#### Anticipated Outcomes
+A defined set of standards for the Europa SDI will foster consistency in projections, data formats, and descriptive documentation in metadata. This consistency will lead to greater interoperability between components in this SDI and will result in data products that are immediately analysis ready by removing the need for additional data processing or reprojection.
+
+#### Approach
+Standards will be defined by considering current standards in use for Europa and those most often used by the Europa community.  We will consider existing IAU standards and those favored by the Europa Clipper mission, and we seek to be consistent with standards defined by authoritative sources.  When multiple or conflicting standards are in common use, we will determine the standard we believe best meets the needs of our user community thru discussion within the Europa Spatial Data Infrastructure Working Group. We will publish these standards on a public website.
+
+#### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|3.1	|Inventory existing projection, data format, metadata, and other standards currently in use by the Europa community and including the Europa Clipper mission team.	|Completed in 2022.|
+|3.2	|Identify IAU-endorsed standards relevant to Europa.	|Completed in 2022.|
+|3.3	|Define a set of standards to be used within this SDI to maximize consistency and interoperability.	|Completed in 2022.|
+|3.4	|Publish standards on a public website.	|Completed in 2022.|
+
+
+### Objective 4 
+Maintain, in conjunction with the Europa community, a living inventory of foundational and framework data products including quantitative (e.g., positional accuracy, resolution, data producer) and qualitative (e.g., fitness-for-use) metadata. This includes setting a standard for metadata to be reported for all data products managed under the Europa SDI organization.
+ 
+#### Anticipated Outcomes
+Maintaining a living inventory of foundational and framework data products will benefit the Europa data community by simplifying the search and discovery process. Collecting these data into a single clearinghouse, with descriptive and standards compliant metadata, allows the community to know what data products exist, the accuracy of those products, and whether they meet the needs of that use case. In addition, such an inventory allows NASA, mission teams, and data producers to identify gaps in knowledge that could be filled through future efforts.
+
+#### Approach
+Our primary approach is to build on the efforts of Laura and Beyer (2021) and use this information as an initial assessment of the publicly available foundational and framework data products for Europa. We will also engage data producers to determine interest in contributing to this SDI and to determine the process to contribute additional data products.  As additional data products are published in the literature or through community data portals/catalogs (e.g., the Planetary Data System), we will include them in our inventory, link to the publicly available products, and assess including them in this SDI.
+
+#### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|4.1	|Inventory the publicly available foundational and framework data products for Europa	|Completed in 2022. Laura and Beyer (2021) provide an initial assessment of such products.|
+|4.2	|Engage Europa data producers directly to collaborate and support including products in this SDI	|Ongoing. Working with Dr. Paul Schenk to incorporate Digital Elevation Models into this SDI.|
+|4.3	|Maintain knowledge of new data products published by the community for potential inclusion in our inventory.	|Ongoing|
+|4.4	|Develop a process for contributing data to this SDI, including a Memorandum of Understanding that supports sharing agreements between stakeholders (related to action 1.4).	|This document is under development.|
+
+
+### Objective 5
+Provide a mechanism to link users, such as data creators (who make the data products), custodians (who manage the data products lifecycle), and data integrators (who provide the data to end users) to create an interconnected user group. 
+
+#### Anticipated Outcomes
+The Europa SDI benefits from maximizing the availability of interoperable Europa data in order to support the broadest possible user community. As a communication tool, the Europa SDI links data creators with data stewards who ensure that generated data are broadly available. We anticipate this objective resulting in the identification of institutions that wish to act as data stewards and to whom data creators can submit data for inclusion in the Europa SDI.
+
+#### Approach
+Our primary approach is to first lay the groundwork to incorporate data contributions from data creators in a transparent manner where the expectations of the data creators, custodians, and data integrators are clearly identified and documented. Planned initial steps include developing clear documentation of standards and formats that are expected for all data products in the Europa SDI, ensuring such documentation is publicly available, and engaging Europa data producers. Once this initial foundation is established, we will identify institutions that are willing and able to serve as data stewards and engage the broader data community in these efforts.
+
+### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|5.1	|Engage Europa data producers and gain experience incorporating data from multiple institutions (related to action 4.2)	|Ongoing.|
+|5.2	|Develop and publish Europa SDI standards (related to action 3.4).	|Completed in 2022.|
+|5.3	|Identify institutions that can and will serve as data stewards.	|Future effort|
+|5.4	|Engage other data creators and stewards to identify one or more additional participants.	|Future effort.|
+|5.5	|Engage tool and service providers to build partnerships using the available data service(s) (related to Objective 8).	|Future effort.|
+
+
+### Objective 6
+Support (through policies and standards) the development of data discovery and access portals making use of Europa SDI managed data and associated Application Programming Interfaces (APIs).
+ 
+#### Anticipated Outcomes
+Supporting the development of data discovery and data access by the broadest possible Europa user community is a fundamental goal of the Europa SDI. Through policies and standards, we will provide a framework by which data can be organized, identified, searchable, and used while minimizing the need for post-processing or reprojection of data. We anticipate that this focus on standardization and data discovery will enable Europa data to be more easily discoverable in a format that is analysis ready, lead to a reduction in redundant data processing efforts across the Europa community and will potentially allow for current data processing resources to be used for science and engineering investigations.
+
+#### Approach
+Our approach to supporting data discovery and access is to develop policies and standards that are consistent with community leading practices. We will identify and implement practices that have demonstrated success in terrestrial and other communities and are relevant to the Europa community.  We will also engage Europa community user groups to educate potential users on the availability of this SDI and solicit feedback on the usability of this SDI. Finally, we will enable metrics on our websites and data portals to allow us to measure and evaluate how the community is interacting with our services and what data products and services are most impactful. These metrics will inform future efforts to modify our approaches and better support the Europa data community.
+
+### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|6.1	|Research community leading practices for data policies, standards, and technologies that enable discovery.|	Ongoing|
+|6.2	|Identify and implement practices that are applicable to the Europa community and practical to implement.| 	Ongoing|
+|6.3	|Engage Europa community user groups to educate potential users on the availability of this SDI and seek community feedback.|	Ongoing|
+|6.4	|Enable metrics to measure the use of the Geoportal, APIs, and the download of data.|	Future effort|
+
+
+### Objective 7
+Ensure the public release of all Europa SDI managed data products and APIs.
+
+#### Anticipated Outcomes
+Publicly releasing all data products and APIs managed under the Europa SDI ensures that these resources are available to the widest audience possible and seeks to democratize the availability of these data and infrastructure. We aim to publicly release all data and APIs in a manner that is discoverable, accessible, and usable (Laura et al., 2018), and that follows leading FAIR practices (Wilkinson et al., 2016). 
+
+#### Approach
+The Europa SDI working group will make data available under both FAIR data principles and the spatial standards defined by the Europa SDI working group, and to be compliant with NASA data release policies. Our approach to data product and API release follows the guidelines described in the NASA Scientific Information policy for the Science Mission Directorate (SPD-41). Specifically, data formats will be machine-readable to allow for automated processing and will include robust, standards-compliant metadata. All data, APIs, and software will be released under an open license, and will be indexed as part of the appropriate NASA catalog (i.e., either data or software). Our repository will also comply with standards for accessibility for all electronic and information technology to people with disabilities and with a principle of non-discriminatory data access so that all users will be treated equally.
+
+### Actions
+|  | Action |	Status |
+|--|--------|----------|
+|7.1	|Define the appropriate license for data and software release and document in the Europa SDI Governance Document.	|Completed in 2022.|
+|7.2	|Establish standards compliant data and metadata formats for this SDI that fulfill SPD-41 requirements (related to objective 3) and document in the Europa SDI Governance Document.	|Completed in 2022.|
+|7.3	|Determine industry standards for repository accessibility and develop actions to ensure these standards are met or exceeded.	|Ongoing|
+|7.4	|Apply for  CoreTrustSeal Certification to become a trusted data repository.|	Future effort|
+
+
+### Objective 8
+Engage with tool developers to ensure support for data and standards included in the Europa SDI.
+
+### Anticipated Outcomes
+We seek to provide a catalog of data and derived data products in a well-documented and standardized format that will benefit many user communities. By engaging with tool and data portal developers, we will better understand the needs of this community and be positioned to collaborate with these groups. We seek to minimize the need to regenerate or reprocess existing data, thereby minimizing redundant efforts within the Europa community. This engagement will help us to provide data in a manner where tool and data portal developer could access the data within the SDI with minimal subsequent processing needed, rather than these providers regenerating or reprocessing data themselves.
+
+### Approach
+We will identify groups developing tools or data portals targeted for use by the Europa community and initiate communication with these groups. We will engage in informal collaborations with interested teams, seeking to develop mutually beneficial partnerships. Our collaboration focus will be educating others about the availability of data, supporting others in the use of Europa SDI-provided services, identifying points of friction for using the Europa SDI, and using this feedback to help develop future efforts.
+
+### Actions
+|  | Action |	Status |
+|--|--------|----------|
+| 8.1	|Identify groups developing tools or data portals targeted for use by the Europa community.	|Future effort|
+| 8.2	|Initiate communication with the above defined groups.	|Future effort|
+| 8.4	|Enable metrics to measure the use of the Geoportal, APIs, and the download of data. |	Future effort |
+| 8.5	|Enable metrics to measure usage of the API. |	Future effort |
+
diff --git a/content/europa/strategy/strategy.md b/content/europa/strategy/strategy.md
new file mode 100644
index 0000000000000000000000000000000000000000..074a60b293ba8a2524360440c781fbee3df46faf
--- /dev/null
+++ b/content/europa/strategy/strategy.md
@@ -0,0 +1,29 @@
+---
+title: "Strategy"
+weight: 1
+---
+
+## Strategic Plan Overview and Executive Summary
+This Europa Spatial Data Infrastructure (SDI) Strategic Plan contains a high-level overview of the background, guiding principles, and philosophy of the Europa SDI and describes the primary strategic objectives from 2022 to 2025. This document explains where and how resources could be best spent to develop and implement the Europa SDI to support a coordinated and strategic effort to provide analysis ready data to Europa scientists and engineers, the Clipper and JUICE Mission teams, the planetary community, and the general public. This document also relates each of the strategic objectives listed below to actions that support accomplishing the objectives, and their anticipated outcomes, to ensure agreement on responsibilities, coherence, and timing for deliverables.
+
+## Background
+The Europa Spatial Data Infrastructure working group is a voluntary cooperation between planetary community members to evaluate existing spatial data and data standards for Europa and assess spatial data storage, acquisition, discovery, and use needs of the Europa community. The Europa SDI is endorsed by the NASA directed Mapping and Planetary Spatial Infrastructure Team (MAPSIT). A spatial data infrastructure (SDI) is the enabling collection of spatial data users, data interoperability agreements, policies and standards, data access mechanisms, and the spatial data themselves (Rajabifard et al., 2002). The overarching goal of the Europa SDI is to allow nonspatial data experts to use spatial data to the greatest extent possible, with the lowest possible overhead (Laura et al., 2018). This working group will address complexities by defining policies and standards that will be applicable to this Europa SDI regarding data interoperability, data contribution, and the long-term maintenance for the benefit of all user communities.
+ 
+The policy decisions for the Europa SDI consider the diverse groups interested in accessing high-quality and processed data, and include the Europa science and engineering communities, mission team needs for strategic planning and targeting observations (e.g., Clipper and JUICE), software application and tool developers, media relation activities, public engagement and education groups, and members of the general public. Understanding this diversity of long-term stakeholders, the Europa SDI strategy will first focus on the needs of scientists, engineers, mission teams, and software and tool developers, and then build on this understanding to inform future work to serve the larger community of users and stakeholders. The Europa SDI aims to improve the infrastructure for public access to and distribution of geospatial planetary data and help ensure that it is Findable, Accessible, Interoperable, and Reusable (FAIR; Wilkinson et al., 2016). It also aims to be a clearinghouse where data in a standardized format can be shared, duplication reduced, and community needs prioritized. In the context of the Europa SDI, a data clearinghouse house is a distributed system of data servers and services which have standardized metadata to facilitate data interoperability. The clearinghouse is a single access location that uses web standards to allow data discoverability. This working group will also help to ensure that valuable information is preserved for posterity in a way that is discoverable, has a high degree of usability, and can foster innovation and experimentation even while missions are actively collecting data (c.f. Planetary Data Ecosystem IRB Report, 2021).
+
+An SDI is an aspect of a Planetary Data Ecosystem (PDE), is complementary to the Planetary Data System (PDS) and serves a distinct need in the planetary community. An SDI is not an archive and therefore does not in any way replace the critical need for the PDS to ensure that NASA-collected data is preserved into antiquity. Instead, the Europa SDI working group aims to provide additional functionality, access, and services for Europa data that are built upon the important foundation the PDS provides (Laura et al., 2022), such as establishing policies, standards, and agreement between data providers that are focused on the needs of a specific community – in this case, those using data collected of Europa. The Europa SDI is a component of the PDE that is currently focusing on analysis ready data and metadata availability and services (Laura et al., 2022). 
+
+## Europa PSDI Vision and Mission
+**Vision:** The Europa Spatial Data Infrastructure will facilitate access to spatial information in support of mission planning, scientific investigation, and public outreach efforts.  
+ 
+**Mission:** The Europa Spatial Data Infrastructure mission is to promote cooperation and development of a Spatial Data Infrastructure that enables discovery, access, interoperability and sharing of Europa spatial data, while pursuing best data management practices (modeled after the Arctic SDI). 
+
+# Guiding Principals
+The following guiding principles are used to assess proposed activities and priorities when formulating and communicating the strategy of the Europa SDI: 
+ 
+The Europa Spatial Data Infrastructure: 
+·	Is a voluntary cooperation between planetary community members 
+·	Is focused principally on the relevant Europa data users, data providers, and stakeholders 
+·	Reflects user and stakeholder needs to enable interoperability and reusability via standardization 
+·	Remains focused on its strategic plan while developing infrastructure and services 
+·	Leverages existing NASA SDI and Planetary Data Ecosystem (PDE) investments 
\ No newline at end of file