Home

Welcome to iGEM 2024! Your team has been approved and you are ready to start the iGEM season!

How it's done

The HTML content you're reading right now is overlaid with a full-screen <canvas> element. There is a fragment shader that defines opacity and color for each pixel of the <canvas>. Shader input values are scroll progress (aka animation progress), time, and resolution.

While time and window size (resolution) are super easy to gather, for animation progress I use GSAP ScrollTrigger plugin.

Once the inputs are prepared, we pass them as uniforms to the shader. The WebGL part of this demo is a basic JS boilerplate to render a fragment shader on the single full-screen plane. No extra libraries here.

The fragment shader is based on Fractal Brownian Motion (fBm) noise.

First, we create a semi-transparent mask to define a contour of burning paper. It is basically a low-scale fBm noise with scroll progress value used as a threshold. Taking the same fBm noise with different thresholds we can
(a) darken parts of the paper so each pixel gets darker before turning transparent
(b) define the stripe along the paper edge and use it as a mask for flames

The fire is done as another two fBm based functions - one for shape and one for color. Both have a much higher scale and both are animated with time value instead of scroll progress.

linkedIn | codepen | twitter (X)

Hello 👋
scroll me

Before you start


Please read the following pages:

Styling your wiki


Feel free to customize the page styling according to your preferences, or you can simply leave the style as it is. It's wise to focus on a clear content first, and on a clean design later.

Be cautious with the size of the assets like images, videos, and more, that you put in your wiki. Large file sizes can hinder the presentation of wikis due to slow internet connections. Remember to compress large files before uploading them to iGEM servers.

This default wiki meets the requirements, enhances navigability, and provides a user-friendly experience for visitors. You should not feel obligated to go beyond the provided styling.

Tips


This wiki will be your team's first interaction with the rest of the world, so here are a few tips to help you get started:

  • State your accomplishments! Tell people what you have achieved from the start.
  • Be clear about what you are doing and how you plan to do this.
  • You have a global audience! Consider the different backgrounds that your users come from.
  • Make sure information is easy to find; nothing should be more than 3 clicks away.
  • Avoid using very small fonts and low contrast colors; information should be easy to read.
  • Start documenting your project as early as possible; don't leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the iGEM Competition calendar
  • Have lots of fun!

Inspiration


You can also view other team wikis for inspiration! Here are some examples: