Skip to content

Change-Bio/PhaffiiNet

Repository files navigation

PhaffiiNet

A virtual and physical network of Komagataella phaffii strains (AKA Pichia pastoris) with gold-standard documentation.

Visit phaffii.net for documentation on PhaffiiNet and the goals there, this README.md file describes how to work with the backend here at GitHub.


Website Development Guide

This repository includes a Next.js static website that showcases the PhaffiiNet strains. Here's how to work with it:

Quick Start

npm install              # Install dependencies
npm run dev             # Start development server at http://localhost:3000
npm run build           # Build static site (outputs to out/)
npm run deploy          # Build and deploy to Firebase dev environment
npm run deploy:prod     # Build and deploy to Firebase production

Editing Content (CMS)

The website uses a file-based CMS - all content is stored in markdown files in the content/ folder:

Homepage Content (content/home.md)

---
hero_title: PhaffiiNet
hero_subtitle: A virtual and physical network of *Komagataella phaffii* strains...
strains_title: The strains
strains_content: Brief description...
---

Strain Files (content/strains/*.md)

---
strain_name: PN-1
strain_description: Description of the strain...
order: 1
---

The order field controls the display order of strain cards. Lower numbers appear first.

Site Settings (content/settings.md)

---
primary_color: '#D4AF37'
company_name: 'Change Bio'
---

Markdown Formatting: Use *text* for italics, **text** for bold. The content is rendered with react-markdown.

Adding New Sections

To add a new section to the homepage:

  1. Add content fields to content/home.md:

    ---
    hero_title: PhaffiiNet
    # ... existing fields ...
    new_section_title: My New Section
    new_section_content: Content goes here...
    ---
  2. Update the page component in src/app/page.tsx:

    // Add to the homeData interface/default:
    let homeData = {
      // ... existing fields ...
      new_section_title: 'Placeholder',
      new_section_content: 'Placeholder',
    };
    
    // Add new section in the JSX (around line 100+):
    <section className="py-12 px-4 bg-white">
      <div className="max-w-4xl mx-auto">
        <h2 className="text-4xl font-bold mb-8 text-center">
          {homeData.new_section_title}
        </h2>
        <div className="text-lg text-gray-700">
          <ReactMarkdown>
            {homeData.new_section_content}
          </ReactMarkdown>
        </div>
      </div>
    </section>

Adding New Pages

  1. Create a new file in src/app/[page-name]/page.tsx
  2. Add content file in content/[page-name].md
  3. Read the content using the same pattern as src/app/page.tsx:
    import fs from 'fs';
    import path from 'path';
    import matter from 'gray-matter';
    
    const contentPath = path.join(process.cwd(), 'content', 'page-name.md');
    const fileContents = fs.readFileSync(contentPath, 'utf8');
    const { data } = matter(fileContents);
  4. Add navigation link in the header (around line 62-66 in src/app/page.tsx)

File Structure

PhaffiiNet/
├── src/app/              # Next.js pages
│   ├── page.tsx         # Homepage
│   ├── layout.tsx       # Root layout
│   └── globals.css      # Global styles
├── content/             # Content files (CMS)
│   ├── home.md         # Homepage content
│   ├── settings.md     # Site settings
│   └── strains/        # Strain markdown files
├── public/              # Static assets (images, videos)
├── data/                # Scientific data (CSV, sequences)
└── package.json         # Dependencies and scripts

Styling

The site uses Tailwind CSS. Common patterns:

  • Colors: Use settings.primary_color from content/settings.md for brand colors
  • Responsive: Use md: prefix for desktop styles (e.g., text-xl md:text-3xl)
  • Spacing: px-4 (padding), mb-8 (margin-bottom), py-12 (padding vertical)

Deployment

The site is configured for static export (output: 'export' in next.config.mjs). After building, all static files are in the out/ directory and can be hosted anywhere.


What are the strains?

We (Change Bio) received the YB-4290 strain of Komagataella phaffii from the ARS collection (NRRL) - we're calling this one PhaffiiNet-1 (PN-1) but it can also be called the type strain. We followed the steps given by Claes et al., 2024 for making their NCYC 2543 hoc1tr-1 strain. The genetic elements used are in the `sequences' folder and the workflow is represented in the OpenCloning file: YB-4290_hoc1tr.zip. To view this file visit https://opencloning.org/, select File->Load cloning history from File, and upload the .zip archive. We've then called this strain PhaffiiNet-2 (PN-2)

Briefly, we used a double-crossover with a split Noursethricin antibiotic marker to replace the native hoc1 gene in the strain with the version with a premature stop codon that is found in Y-11430. The selection region of the integrated sequence was floxed, and so we transiently expressed cre recombinase using an episomal genetic element with Zeocin selection to "flip out" the selection, leaving only a lox scar. After passaging on non-selective media, we confirmed susceptibility to both Noursethiricin and Zeocin as an indication that the cre-recombination had happened and the episomal plasmid had been lost. We then carried out sequencing of an amplicon amplified from the genome region using colony PCR around the hoc1 gene to confirm that the truncation had occured. We have not yet carried out whole-genome sequencing of the strain (see "Outstanding To-dos").

Why are you doing this?

We are a protein manufacturer that uses our proprietary strains of K. phaffii and process to make our customers' proteins. When starting the company and looking to onboard a base strain of K. phaffii our eyes were opened by the OpenPichia paper Claes et al., 2024. We would like to say an enormous thank you to the authors of that paper and the related paper Offei et al., 2022 for their work in piecing together the story of what we call the "Industrial strain" of K. phaffii - CBS7435/Y-11430. Unfortunately we found the terms of distribution of the OpenPichia strain too restrictive for commercial use, and so we replicated their construction of the strain in our lab. As a business, we're uniquely positioned to be able to make the decision to release the strain under the OpenMTA without the encumbrance of university TTO etc., so to support the Pichia community (and to grow the community in future) we've released it.

Where can I get it?

You can email us at hello@changebio.uk and we can send you the MTA, or you can look at the list of people and emails from the bionet and pick your best option from there. We just ask that you pay for shipping and deal with customs, and have patience with us as we aren't a strain collection!

Under what conditions is it distributed?

We distribute it under the OpenMTA, for free, and you can do whatever you want with it. Clearly it's nice if you acknowledge where it came from, but we really really don't want any strings attached at all. NB April 2025: please don't acknowledge us for now we're keeping it on the downlow at the moment! If you get it from someone else, it's up to them, but it will originally have come from us under the OpenMTA!

What is the FTO status?

The request for the strain to the ARS Collection was placed on the 3rd May 2024 by Noah Sprent of Change Bio. A copy of the ordering form with personal details removed is found in NRRL_Order_Form_anonymised.pdf. The text relevant to FTO in this document is:

The above listed microorganism is provided under the following terms:

  1. Recipient shall acknowledge the contribution of ARS to any work reported that uses this microorganism.
  2. Any third party requesting a sample shall be referred to ARS

Therefore, any third party who wishes for a sample of strain YB-4290 should contact the ARS instead of Change Bio.

CB paid for shipping through provision of a FEDEX shipping label. As the organism was not Risk Group 2, an MTA was not required inline with the ARS collection policy. Therefore, the only relevant text on the website related to obligations of CB were:

Is there a restriction on use of Strains? While the NRRL has no restrictions on the use of the strains in the open or patent collection that have been patented or no longer fall under patent regulations, that does not exclude the possibility that other patent applications may have been filed for the use of this isolate or patents/applications that claim using strains of this type for a particular purpose or process. While the strain itself may not be currently patented, we really cannot provide any guidance on freedom to operate; that would depend upon how you wish to use the strain and what patents/patent applications already exist and would best be addressed by your intellectual property counsel. The only restriction we do have that is we do not allow third party distribution of strains. Any third party requesting a sample shall be referred to ARS NRRL Culture Collection. NRRL is a publicly funded collection and it is important that we document our impact to ensure continued funding. If at any point any of the strains lead to a discovery of innovation, we ask that you periodically update us on the use of these strains. This will allow us to more accurately quantify our impact.

We request that recipients acknowledge the contribution of the ARS Culture Collection to any work using microorganisms from the culture collection by including the following text “Microbial strains used in this work were provided by the USDA-ARS Culture Collection (NRRL)” The closest date archived by the Waybackmachine to when the strain was ordered is 10th May 2024.

Therefore, while CB are not able to redistribute the original YB-4290 strain, we gratefully ackowledge the contribution of the ARS Culture collection to this work: Microbial strains used in this work were provided by the USDA-ARS Culture Collection (NRRL).

Change Bio are not able to warrant any Freedom to Operate of this strain. We also do not guarentee that the information above is complete. Anyone using this strain should carry out their own FTO investigation.

Outstanding to-dos:

  • Obviously we want to be able to warrant FTO. Can we crowd-fund some work from lawyers to carry out a proper FTO investigation and get some documentation put in this repo?
  • We need to do a whole-genome sequence, preferably more than one, to confirm the genotype.
  • Are there killer plasmids present in the strain? Connected to whole-genome sequencing
  • Change Bio have carried out extensive testing of the strain in-house, but we aren't able to share the results of this work. It would be useful to the community of others could reproduce some of the findings shown in the OpenPichia paper using this strain.
  • Change Bio have in-house strain modifications for protein production etc., which also cannot be shared, however the community may find it useful to create a library of useful mutants etc. from this strain.

About

PhaffiiNet

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •