diff --git a/content/PlanetarySDIs/about.md b/content/PlanetarySDIs/about.md
index b2f22b3f99d4a069e33ec488f841a9bb9f3ee744..c139e8e385037f137129a3cad864ecbba5b767ed 100644
--- a/content/PlanetarySDIs/about.md
+++ b/content/PlanetarySDIs/about.md
@@ -1,6 +1,29 @@
 ---
-title: What are Planetary SDIs?
-weight: 1
+weight: 0
+title: About Planetary SDIs
+bibFile: content/bibliography.json
 ---
+## What is a planetary SDI?
+Collecting, managing, finding, and analyzing spatial data is hard. The knowledge required to discuss each of those tasks easily fills a book and the knowledge required to support others performing one or more of those tasks easily fills several more volumes. It is all to easy to not know how to find, use, or interpret publicly available spatial data.
 
-High level.
\ No newline at end of file
+Spatial data infrastructures were born from the terrestrial science (geography) community in the early 1980s with the birth of Geographic Information Systems (GIS). An explosion in digital data collection, mapping, and dissemination necessitated the development of infrastructures for organization much in the same way that, for example, the advent of the automobile heralded the development of the US interstate highway system. The infrastructures needed to store, organize, and make spatial data both discoverable and interoperable were called Spatial Data Infrastructures or SDIs.
+
+Planetary SDIs are body (e.g., the Moon or Mars) specific infrastructures created by groups of planetary scientists, data scientists, geographers, and engineers that are interested in making spatial data easier for you to discover, download, and use. The members of the planetary SDI governing groups have expertise in the areas described above and have gotten together to codify the spatial concepts, like map projections, data formats, or body parameters, in order to ensure that data within a planetary SDI are discoverale, interoperable, well described, and ultimately usable. The groups also work to build out governance models, data sharing agreements, and the other policy related items necessary to support SDIs over the long term.
+
+The ultimate goal of each governing group is to support the widest possible cross section of users by growing the scope of data, metadata, and usage documentation available within their given SDI. This support takes the form of outreach to data producers and providers, drafting of living standards documents to support interoperability, engagement with past, current, and future flight missions to ensure interoperability, and engagement with you, the user.The efforts of PSDIs distill down to seeking an environment where data are [FAIR](https://www.go-fair.org/fair-principles/)ly available for all users, whatever their expertise level.
+
+For a significantly more scholarly discussion of planetary SDIs, see {{< cite "Laura:2017;Laura:2018ess">}}.
+
+## Participants
+Planetary SDIs are a community driven, cross institutional endeavour. By necessity, they are successful because they engage a wide cross-section of the community with different expertise and institutional affiliations. While this website is hosted by the USGS Astrogeology, none of this work would be possible without the active participation by community members from the following organizations.
+
+<span style="margin:auto; display:table;">
+<table>
+<tr>
+<td><img src="https://www.lpi.usra.edu/publications/newsletters/lpib/new/wp-content/uploads/2017/07/lpi_logo_fullname_002_black.png" width=200/></td>
+<td><img src="https://www.nasa.gov/sites/default/files/thumbnails/image/edu_what_is_nasa_emblem.jpg" width=200/></td>
+<td><img src="https://www.seti.org/sites/default/files/styles/original/public/2018-05/seti_logo_starfield_560px.jpg?itok=3Gci_Y5-" width=200/></td>
+<td><img src="https://d9-wret.s3.us-west-2.amazonaws.com/assets/palladium/production/s3fs-public/styles/medium/public/thumbnails/image/usgs-placeholder_0.png?itok=AO6-JETt" width=200/></td>
+</tr>
+</table>
+</span>
\ No newline at end of file
diff --git a/content/europa/data/data_gaps.md b/content/europa/data/data_gaps.md
index d08f5bb91458facb6a8f2aab309c4ebde3efeaf2..1ee21cb1f5ea9786f8ef5f86533ad43b1f70044d 100644
--- a/content/europa/data/data_gaps.md
+++ b/content/europa/data/data_gaps.md
@@ -1,6 +1,14 @@
 ---
-title: ESDI Data Gaps
+title: Europa SDI Data Gaps
 weight: 31.1
 ---
 
-What gaps exist in the available data? What data is this group specifically seeking out?
\ No newline at end of file
+Data gaps are derived [foundational or framework data products](https://fdp.astrogeology.usgs.gov) that the Europa SDI governance groups would be of high value to the Europa science community. At this time, data gaps are primarily focused on making existing data publicly, and widely available. In the future, missions such as [Europa Clipper](https://www.google.com/search?client=safari&rls=en&q=Europa+Clipper&ie=UTF-8&oe=UTF-8) and [JUICE](https://sci.esa.int/web/juice) will collect new data that can and will be used to create new products. As those data begin to come, we expect that more ideas for derived products will be included here.
+
+We identify the following data gaps and wish to actively engage with the community to make these data widely available in an [analysis ready data](https://stac.astrogeology.usgs.gov/docs/about/) format:
+
+- Europa Digital Terrain Models (DTMs)
+- Galileo [Near Infrared Mapping Spectrometer (NIMS)](https://nssdc.gsfc.nasa.gov/nmc/experiment/display.action?id=1989-084B-01) data
+- Any and all geologic maps, including the soon to be released [global geologic map](https://planetcarto.wordpress.com/2019/09/23/the-first-global-geologic-map-of-europa/)
+
+The above listing is not exhaustive, as our knowledge of the available data products is not exhaustive. If you have a product and are interested in making it publicly available [get involved]({{< ref "get_involved" >}})! We are more than happy to help make these data available under the Europa SDI umbrella.
\ No newline at end of file
diff --git a/content/europa/data/data_products.md b/content/europa/data/data_products.md
index d7435799949842dfd88aa994aba4161ee6e76874..5e7d0557dfa3a4fd7242a8e24d0ce7e0240e1489 100644
--- a/content/europa/data/data_products.md
+++ b/content/europa/data/data_products.md
@@ -1,6 +1,11 @@
 ---
-title: ESDI Compliant Data Products
+title: Europa SDI Compliant Data Products
 weight: 31.1
 ---
 
-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
+The Europa SDI maintains a list of known, compliant data products. We would like to bring additional products into the Europa SDI. If you have products and would like us to link or serve them, please [get involved]({{< ref "get_involved" >}}) as a data producer or data provider.
+
+| Data Description | Data Documentation | Data Browser |
+|------------------|--------------------|--------------|
+| [Absolutely Controlled](https://fdp.astrogeology.usgs.gov/fdp/about/#geodetic-control-or-just-control) Galileo observations | [LINK](https://stac.astrogeology.usgs.gov/docs/data/jupiter/europa/galileo_individual_images/) | [STAC Browser](https://stac.astrogeology.usgs.gov/browser-dev/#/collections/galileo_usgs_photogrammetrically_controlled_observations) |
+| [Absolutely Controlled]() Galileao observation sequences | [LINK](https://stac.astrogeology.usgs.gov/docs/data/jupiter/europa/galileo_sequence_mosaics/) | [STAC Browser](https://stac.astrogeology.usgs.gov/browser-dev/#/collections/galileo_usgs_photogrammetrically_controlled_mosaics)
\ No newline at end of file
diff --git a/content/europa/data/data_services.md b/content/europa/data/data_services.md
index d8a10224f9390939973fa2c2d0c8ddc921421a1a..ae26c231a219c2da5b1641aa862e5499c1a8641a 100644
--- a/content/europa/data/data_services.md
+++ b/content/europa/data/data_services.md
@@ -1,5 +1,5 @@
 ---
-title: ESDI Compliant Data Services
+title: Europa SDI Compliant Data Services
 weight: 31.1
 ---
 
diff --git a/content/europa/get_involved.md b/content/europa/get_involved.md
index bbdc66d1b17b1e53c3f407980e902ed6e03ff71c..fca0167d0d6e479266266d0c1fbe82063ffbe399 100644
--- a/content/europa/get_involved.md
+++ b/content/europa/get_involved.md
@@ -13,10 +13,10 @@ If you have Europa data or are interested in creating new derived products, this
 
 {{< tab "Data Providers">}} 
 ## Who is this section for?
-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.
+If you run a server or a data clearing house and would like to make Europa SDI compliant data available, this is the place to start.
 {{< /tab >}}
 
-{{< tab "ESDI Evangalizers" >}}
+{{< tab "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.
 
@@ -24,6 +24,6 @@ If you are excited about Europa spatial data, metadata, standards, and/or data a
 
 {{< 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.
+If you are a data user and you need help using products within the Europa SDI, this is the place to start.
 
 {{< /tabs >}}
\ No newline at end of file
diff --git a/content/europa/standards/cartographic_standards.md b/content/europa/standards/cartographic_standards.md
index 7fd82abcd95f9418fbea20cda94d44eeda2e8e91..19d3db5c6f66fd6407fbdf30fca344a7cdd1fbc5 100644
--- a/content/europa/standards/cartographic_standards.md
+++ b/content/europa/standards/cartographic_standards.md
@@ -3,5 +3,5 @@ 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.
+The Europa SDI 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_standards.md b/content/europa/standards/data_standards.md
index eec297c82fb7505e4b7b6b1efe478c028fc61e89..943063f0075b9cd07eac0d57291fe2479c976329 100644
--- a/content/europa/standards/data_standards.md
+++ b/content/europa/standards/data_standards.md
@@ -18,3 +18,6 @@ weight: 50
 - 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
+
+## Ephemeris Information
+- All sun, spacecraft, sensor, and target body ephemeris information is to be provided either by [Navigation and Ancillary Information Facility (NAIF)](https://naif.jpl.nasa.gov/naif/) as SPICE kernels or in NAIF SPICE compliant format by another provider (e.g., a mission team). This includes sensor and target positions, velocities, and orientations as well as sensor parameters such as distortion models.
\ No newline at end of file
diff --git a/content/europa/standards/metadata_standards.md b/content/europa/standards/metadata_standards.md
index 3876878eb233287890c1741337f7306bd57dec3a..87e0a72f295f601e6d9c449526982b20e2bd5a94 100644
--- a/content/europa/standards/metadata_standards.md
+++ b/content/europa/standards/metadata_standards.md
@@ -5,7 +5,7 @@ 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).