First install pre-commit to keep your commits clean.

The website is using Jekyll static website generator and Github pages. To run and develop it locally you need to install rbenv using apt install rbenv ruby-build. Then use rbenv init and follow the instructions to set it up. With rbenv installed and activated in your shell:

git clone --recurse-submodules https://github.com/precice/precice.github.io && cd precice.github.io
pre-commit install
rbenv install
bundle install
bundle exec jekyll serve -l

You can now view website locally in your browser at localhost:4000.

Submodules do not yet get updated automatically. This means if you change something in the OpenFOAM adapter documentation or the description of the tutorials, you need to explicitly trigger an update here:

git submodule update --remote --merge

This updates all submodules. You can call it from everywhere (you do not need to cd into the submodule). Afterwards, commit and push.

Do not directly edit the content of the submodules from within the website repository. This might give ugly merge conflicts.

To pull changes including submodules

git pull --recurse-submodules

Instead of building on your system (which requires some setup the first time), you can directly serve the website from a Docker container (using the community image jekyll/jekyll). In this directory, after you initialize and update the git submodules, run the following:

docker run --rm --volume="$PWD:/srv/jekyll:Z" --publish 127.0.0.1:4000:4000 -it jekyll/jekyll jekyll serve

Arguments:

• docker run: The Docker command to run a container from an existing image
• --rm: Automatically remove (or not) the container when it exists
• --volume: Mount the current directory ($PWD) to a directory in the container (/srv/jekyll), so that only the current container can see the content (:Z)
• --publish: Publish the container's port 4000 (where Jekyll serves the website) to the host port 4000. Note that 127.0.0.1 is the localhost in IPv4. For IPv6, you can replace that with [::1].
• -it: Interactive container, capturing signals (such as Ctrl-C).
• jekyll/jekyll: The image
• jekyll serve: The command to run. Somehow, the current default make target does not work in this context.

If you would like to learn more about the preCICE documentation, a good start are the documentation of the documentation pages.

Edit _includes/news_banner.html.

A good starting point is the following:

<div class="background-light banner-container">
  <div class="container">
    <div class="row m-0">
      <div class="col-lg-12 banner">
        <p class="m-0">
          This is the text of my news banner.
        </p>
      </div>
    </div>
  </div>
</div>

Use the following to selectively change appearance.

{% if include.landing %}
  Displayed on the landing page.
{% else %}
  Displayed on other pages.
{% endif %}

• If you get permission issues to install gems, resist the impulse of sudo: you can install the dependencies locally by running bundle config set --local path 'vendor/bundle' before bundle install.

• If you get errors like Gem::Ext::BuildError: ERROR: Failed to build gem native extension. or mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h, then (as the error message suggests), you may need to install a Ruby development environment (e.g., ruby-dev).

• If you are a poor soul that is stuck developing on Windows, the -l flag is known to crash, so best try without.

• Should you get the warning

  Fetching citation data failed with OpenURI::HTTPError

  while building the site locally, then you have been rate limited by Google Scholar. The citation database won't be up to date. Alternatively open http://scholar.google.com/ in a browser and complete the Captcha.

For further information see the documentation page on common issues.

The content of the preCICE webpage is licensed under CC-BY 4.0. Third-party licenses (e.g. of the framework we use) are collected in the licenses subfolder. Note that preCICE itself has a software license, LGPL v3.