Skip to content

Home

This is a template for an ESIIL postdoctoral researcher.

Postdoc Project Title

Postdoc Project Title

This postdoc project runs as a single system: a GitHub repository where environmental data science is organized, analyzed, and versioned, and a public website where results are explained and shared with collaborators, mentors, and community audiences.

As the project progresses, the repository becomes the reproducible record of the research, and the website becomes the public report.

Edit this homepage in GitHub Open the GitHub repository

Placeholder image for the homepage overview

This image gives the Postdoc Project homepage a shared visual identity for environmental data science.

Replace this image in GitHub

To update: delete the current image in this folder and upload one new image. Keep it clean, uncluttered, and concept-driven rather than photo-real.

Delete this note after the site is customized.

Postdoc Project Abstract

Add an overview of the postdoc project, the research question, the communities or systems involved, and the outputs the researcher expects to produce. This can mirror a project description, fellowship summary, or ESIIL profile.

Start Here

  1. Replace the title and summary with the project question, scientific or community need, and main outputs the postdoc expects to produce.
  2. Add or link datasets, working documents, references, and mentor/collaborator resources.
  3. Run or adapt at least one analysis workflow and record decisions in the repository.
  4. Commit figures, tables, notes, and summaries so the work is versioned and reproducible.
  5. Use the website to share progress, methods, and results with collaborators and community audiences.

Plan the work Document data and resources Set community expectations

Postdoc Project Landmarks

Use these lightweight labels to connect work sessions, meeting notes, and homepage edits:

PD-A People and roles; PD-B Question and scope; PD-C Data and access; PD-D Methods and workflows; PD-E Results and synthesis; PD-F Outputs and handoff.

Use the landmark guide

How This Repo Is Organized

The repository has two connected layers. Top-level files configure the project and its automation. The docs/ folder contains the website content. mkdocs.yml tells MkDocs how to turn that content into the public site. Analysis folders hold the working scientific materials that generate the results shown on the website.

Part of the repo What it does What usually belongs there
Top-level files and folders Configure the project and keep shared repository guidance in one place README.md, LICENSE, workflows, containers, templates, environment setup, and repo-wide metadata
docs/ Stores the source content for the public website Homepage text, summaries, methods, community-facing documentation, and website assets
mkdocs.yml Controls how the site is rendered Navigation, theme settings, plugins, and GitHub edit links
Working folders Hold the science-in-progress Data references, notebooks, scripts, workflows, figures, outputs, and reproducibility materials

Repository Side: Do The Research

Placeholder image for the repository side of the workflow

This image represents the repository side of the postdoc project: data, code, workflows, and reproducibility.

Replace this image in GitHub

To update: delete the current image in this folder and upload one new square image. Use a flat, minimal, screen-print style graphic with no text.

Delete this note after the site is customized.

Related landmarks: PD-C Data and access; PD-D Methods and workflows.

The repository is the working record of the project: it tracks what changed, why it changed, and how results were produced.

  • Data sources and metadata
  • Notebooks and scripts
  • Workflows and reproducible analysis
  • Meeting notes and decisions
  • Figures, tables, manuscripts, and other outputs

Website Side: Share The Research

Placeholder image for the website side of the workflow

This image represents the website side of the postdoc project: summaries, maps, figures, and public communication.

Replace this image in GitHub

To update: delete the current image in this folder and upload one new square image. Use a flat, minimal, screen-print style graphic with no text.

Delete this note after the site is customized.

Related landmarks: PD-E Results and synthesis; PD-F Outputs and handoff.

The website turns the research record into a readable public report.

  • Plain-language summaries
  • Methods documentation
  • Figures, maps, and visualizations
  • Project updates and synthesis products
  • Manuscripts, reports, dashboards, or educational materials

How The Two Sides Connect

The repository and website are not separate products. When the postdoc updates data, analysis code, figures, or written summaries in GitHub, those changes can be rendered through the website. Commits are the bridge between doing the research and sharing the research.

When This Postdoc Project Is Live

A postdoc project is live when:

  • The research question is stated
  • Data sources are linked or documented
  • At least one analysis or workflow is runnable
  • Outputs are committed to the repository
  • The website explains what the project is doing and why it matters

For guidance on turning this scaffold into a public scientific record, see the Public-Facing Site Guide.

Use this section to show how the project gets started without manually editing image links one by one.

This gallery displays early setup artifacts for the postdoc project.

Add or replace files in this gallery

To update: upload supported files to this folder and commit. The website sorts files alphabetically. Use this folder for kickoff notes, orientation screenshots, starter diagrams, and early planning visuals.

Delete this note after the site is finalized.

Use this section for the links the postdoc will actually maintain. Replace each placeholder with the working document, repository resource, dataset hub, or output page that collaborators should use.

  • Main Working Document: [link]
  • GitHub Repository: [link]
  • Data / Resources: [link]
  • Outputs / Dashboard: [link]

Current Phase

Working Phase: Project setup
(Replace this line with the phase the project is actually in, such as onboarding, data access, active analysis, writing, or handoff.)

People

Replace this table with names, roles, institutions, and responsibilities so new collaborators know who is doing what.

Related landmark: PD-A People and roles.

Placeholder image representing collaboration and project identity

This image represents collaboration, project identity, or a real postdoc project photo.

Replace this image in GitHub

To update: delete the current image in this folder and upload one new image. A real project photo is welcome here, but an abstract collaboration image also works.

Delete this note after the site is customized.

Name Role Institution Responsibilities
Name Postdoctoral researcher Institution Responsibilities
Name Mentor or collaborator Institution Responsibilities