prebid · bretg · Dec 21, 2021 · Dec 21, 2021 · Dec 21, 2021
diff --git a/_data/sidebar.yml b/_data/sidebar.yml
@@ -53,7 +53,7 @@
 
 - sbSecId: 0
   title: Header Bidding
-  link: /wrapper_code_of_conduct.html
+  link: https://prebid.org/code-of-conduct/
   isHeader: 0
   isSectionHeader: 0
   sectionTitle:

diff --git a/guide.md b/guide.md
@@ -100,7 +100,7 @@ The includes directory contains HTML files that can be included within files, su
 
 **_bidders**
 
-The bidders directory is not a standard part of Jekyll; it’s a special use directory specifically for the Prebid.org site. The files in this directory are used to construct the table of partners on the partners/partners.html page.
+The bidders directory is not a standard part of Jekyll; it’s a special use directory specifically to construct the table of bidders on dev-docs/bidders.md and dev-docs/pbs-bidders.md
 
 **_sites**
 

diff --git a/overview/prebid-management-committees.md b/overview/prebid-management-committees.md
@@ -8,118 +8,10 @@ sidebarType: 0
 # Project Management Committees
 {: .no_toc}
 
-Project Management Committees are responsible for the active management of one or more GitHub repositories, which are also identified by resolution of the Board.
-
-The committees meet periodically to:
-
-- establish and prioritize roadmap items
-- review open issues and pull requests
-- discuss policies
-- create development plans
-
-The following sections describe the committees.
-
-* TOC
-{:toc}
-
-## Prebid.js
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Prebid.js and related repositories |
-| **Description** | browser-based header bidding |
-| **Chair** | Gareth Glaser (Rubicon Project) |
-| **Audience** | Product and Engineers |
-
-GitHub Repositories:
-
-+ https://github.com/prebid/prebid.js
-+ https://github.com/prebid/Prebid.js-packager
-+ https://github.com/prebid/prebid-universal-creative
-+ https://github.com/prebid/currency-file-generator
-+ https://github.com/prebid/prebid-js-build-generator
-
-
-## Prebid Mobile
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Prebid Mobile SDK |
-| **Description** | Mobile-app based header bidding |
-| **Chair** | Bryan Szekely (Rubicon Project) |
-| **Audience** | Product and Engineers |
-
-GitHub Repositories:
-
-+ https://github.com/prebid/prebid-mobile-ios
-+ https://github.com/prebid/prebid-mobile-android
-
-
-## Prebid Server
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Prebid Server and Prebid Cache |
-| **Description** | Server-side header bidding |
-| **Chair** | Bret Gorsline (Rubicon Project) |
-| **Audience** | Product and Engineers |
-
-GitHub Repositories:
-
-+ https://github.com/prebid/prebid-server
-+ https://github.com/prebid/prebid-cache
-+ https://github.com/prebid/prebid-server-java
-+ https://github.com/prebid/prebid-cache-java
-
-
-## Prebid Tools
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Misc. Tools |
-| **Description** | Debugging and Operational Support |
-| **Chair** | Asaf Shamly (Browsi) |
-| **Audience** | Product, Business, and Engineers |
-
-GitHub Repositories:
-
-+ https://github.com/prebid/header-bidder-expert
-
-## Identity
-
-{: .table .table-bordered .table-striped }
-| **Scope** | User Identification |
-| **Description** | Chart Prebid's role in the future of identity on the web and coordinate any implementation efforts |
-| **Chair** | Stephanie Layser (NewsCorp) |
-| **Audience** | Product, Business, and Engineers |
-
-GitHub Repositories:
-
-+ TBD
-
-## Video Taskforce
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Video |
-| **Description** | Define the needs for video header bidding |
-| **Chair** | Mike Chowla (Pubmatic) |
-| **Format Lead** | Joel Korpi (Xandr) |
-| **Audience** | Product, Business, and Engineers |
-
-## Marketing Taskforce
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Prebid.org events and marketing |
-| **Description** | Coordinates Prebid events and press releases |
-| **Chair** | Joel Fisher (Rubicon Project) |
-| **Audience** | Marketing, Business |
-
-## Publisher Taskforce
-
-{: .table .table-bordered .table-striped }
-| **Scope** | Publisher-related topics |
-| **Description** | Header bidding issues, optimization, strategy, best practices |
-| **Chair** | Stephanie Layser (NewsCorp) |
-| **Audience** | Business |
+This page has moved to [https://prebid.org/project-management-committees/](https://prebid.org/project-management-committees/)!
 
 ## Further Reading
 {: .no_toc}
 
 * [What is Prebid.org?](/overview/what-is-prebid-org.html)
-* [Prebid.org Membership and Partners](/partners/partners.html)
+* [Prebid.org Membership](/partners/partners.html)
diff --git a/overview/what-is-prebid-org.md b/overview/what-is-prebid-org.md
@@ -27,8 +27,7 @@ We focus on providing value-add to publishers and encourage the industry to depl
 Prebid takes two approaches to accomplish this:
 
 ### Wrapper Code of Conduct
-Prebid members must agree to support the [Wrapper Code of Conduct](/wrapper_code_of_conduct.html
-). This ensures that all wrapper providers are operating within the same principles.
+Prebid members must agree to support the [Wrapper Code of Conduct](https://prebid.org/code-of-conduct/). This ensures that all wrapper providers are operating within the same principles.
 
 ### Trademark  
 We support wrappers based on Prebid technology with rights to the **Powered by Prebid** brand.

diff --git a/partners/partners.md b/partners/partners.md
@@ -1,54 +1,15 @@
 ---
 
 layout: page_v2
-title: Partners | Prebid
-description: Partners
+title: Membership
+description: Membership
 sidebarType: 0
 
 ---
-# Prebid.Org Members
+# Prebid.Org Membership
 
-<div style="text-alignment:center">
-<h2>Join Now</h2>
-</div>
+This page has moved to [https://prebid.org/membership/](https://prebid.org/membership/)!
 
-Prebid.org was developed to bring together the oversight, guidance, and development capabilities of the ad tech community to solve the industry’s common technical hurdles. By structuring the organization with a tiered membership system, we can ensure that the organization’s standards are upheld and appropriately funded, and that Prebid solutions continue to be built by and made available to the Prebid community.
-
-Join your industry peers in helping build and shape the ad tech ecosystem.
-
-<hr>
-
-## Why Join?
-
-Companies join Prebid.org because they want to take an active role in supporting the growth and evolution of the ad tech ecosystem:  
-- Network with other members of Prebid.org.
-- Support the community by helping fund Prebid services and events.
-- Demonstrate thought leadership in the ad tech space.
-- Promote Prebid projects for faster market adoption.
-- Help define the technologies that shape of the industry by participating in our Slack workspace and joining the [Product Management Committees](/overview/prebid-management-committees.html).
-
-<hr>
-
-## How To Join
-
-1. Download and review the [Prebid.org Bylaws](https://files.prebid.org/docs/Prebid_org_bylaws_jun_2019.pdf).  
-2. Complete the [Prebid.org Membership Agreement](https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=610f838a-3001-4999-aca0-6682cbcac66c&env=na3-eu1&acct=2160069d-b42e-4c0a-9528-3a58d1c58bf9&v=2).
-3. Prebid will consider your membership application.
-
-<hr>
-
-## Membership Levels and Pricing
-
-{: .table .table-bordered .table-striped }
-|                     | Board Seat                                                            | PMC Participation | Private Slack Instance | Participate in Prebid.org Events | Prebid.org Email Address | Logo on Prebid.org Website | Annual Fees |
-|---------------------|-----------------------------------------------------------------------|-------------------|------------------------|----------------------------------|--------------------------|----------------------------|-------------|
-| Leader Members     | <span style="color:#32CD32;">✓</span>                                                                    | <span style="color:#32CD32;">✓</span>                 | <span style="color:#32CD32;">✓</span>                      | <span style="color:#32CD32;">✓</span>                               | <span style="color:#32CD32;">✓</span>                        | <span style="color:#32CD32;">✓</span>                          | $40,000     |
-| Technology Partners | As a Group,  Technology members  elect a representative  to the board | <span style="color:#32CD32;">✓</span>                 | <span style="color:#32CD32;">✓</span>                      | <span style="color:#32CD32;">✓</span>                                | <span style="color:#32CD32;">✓</span>                        | <span style="color:#32CD32;">✓</span>                          | $25,000     |
-| Publishers          | As a Group, Publisher members elect  a representative to  the board  | <span style="color:#32CD32;">✓</span>                 | <span style="color:#32CD32;">✓</span>                      | <span style="color:#32CD32;">✓</span>                                | <span style="color:#32CD32;">✓</span>                        | <span style="color:#32CD32;">✓</span>                          | $5,000      |
-| Buyers          | As a Group, Buyer members elect  a representative to  the board  | <span style="color:#32CD32;">✓</span>                 | <span style="color:#32CD32;">✓</span>                      | <span style="color:#32CD32;">✓</span>                                | <span style="color:#32CD32;">✓</span>                        | <span style="color:#32CD32;">✓</span>                          | $5,000      |
-| Community           | <span style="color:#B22222">✖</span>                                                                     | <span style="color:#32CD32;">✓</span>                 | <span style="color:#32CD32;">✓</span>                      | <span style="color:#32CD32;">✓</span>                                | <span style="color:#B22222">✖</span>                         | <span style="color:#B22222;">✖</span>                           | Free        |
-
-Have questions about becoming a member, email us at [[email protected]](mailto:[email protected]).
-
-<br>
-<br>
+## Related Reading
+- [Why Prebid](https://prebid.org/why-prebid/)
+- [Code of Conduct](https://prebid.org/code-of-conduct/)
diff --git a/prebid-server/developers/add-new-bidder-go.md b/prebid-server/developers/add-new-bidder-go.md
@@ -37,7 +37,7 @@ Throughout the rest of this document, substitute `{bidder}` with the name you've
 
 ### Respect The Rules
 
-We are proud to run the Prebid Server project as a transparent and trustworthy header bidding solution. You are expected to follow our community's [code of conduct](https://docs.prebid.org/wrapper_code_of_conduct.html) and [module rules](https://docs.prebid.org/dev-docs/module-rules.html) when creating your adapter and when interacting with others through issues, code reviews, and discussions.
+We are proud to run the Prebid Server project as a transparent and trustworthy header bidding solution. You are expected to follow our community's [code of conduct](https://prebid.org/code-of-conduct/) and [module rules](/dev-docs/module-rules.html) when creating your adapter and when interacting with others through issues, code reviews, and discussions.
 
 **Please take the time to read our rules in full.** Below is a summary of some of the rules which apply to your Prebid Server bid adapter:
   - Adapters must not modify bids from demand partners, except to either change the bid from gross to net or from one currency to another.

diff --git a/prebid-server/developers/add-new-bidder-java.md b/prebid-server/developers/add-new-bidder-java.md
@@ -37,7 +37,7 @@ Throughout the rest of this document, substitute `{bidder}` with the name you've
 
 ### Respect The Rules
 
-We are proud to run the Prebid Server project as a transparent and trustworthy header bidding solution. You are expected to follow our community's [code of conduct](https://docs.prebid.org/wrapper_code_of_conduct.html) and [module rules](https://docs.prebid.org/dev-docs/module-rules.html) when creating your adapter and when interacting with others through issues, code reviews, and discussions.
+We are proud to run the Prebid Server project as a transparent and trustworthy header bidding solution. You are expected to follow our community's [code of conduct](https://prebid.org/code-of-conduct/) and [module rules](/dev-docs/module-rules.html) when creating your adapter and when interacting with others through issues, code reviews, and discussions.
 
 **Please take the time to read our rules in full.** Below is a summary of some of the rules which apply to your Prebid Server bid adapter:
 - Adapters must not modify bids from demand partners, except to either change the bid from gross to net or from one currency to another.

diff --git a/principles.md b/principles.md
@@ -23,4 +23,4 @@ Prebid.org uses the following principles to guide how we develop [Prebid.js]({{s
 ## Further Reading
 
 + [What is Prebid?](/overview/intro.html)
-+ [Header Bidding Wrapper Code of Conduct]({{site.baseurl}}/wrapper_code_of_conduct.html)
++ [Header Bidding Wrapper Code of Conduct](https://prebid.org/code-of-conduct/)
diff --git a/wrapper_code_of_conduct.md b/wrapper_code_of_conduct.md
@@ -8,85 +8,9 @@ sidebarType: 0
 # Prebid.org Header Bidding Code of Conduct
 {:.no_toc}
 
-Nov 17, 2020
+This page has moved to [https://prebid.org/code-of-conduct/](https://prebid.org/code-of-conduct/)!
 
-In order to encourage the development of quality products while maintaining a healthy open source community, Prebid.org members and contributors are expected to abide by technical guidelines based on the core values of the organization.
-
-* TOC
-{:toc}
-
-## Prebid.org Core Values
-
-The main objective of Prebid.org is to make great header bidding technology available for web publishers and mobile app developers. We believe great technology is:
-
-- **Efficient** - Products offered by Prebid.org should not burden a user device, the network, or a company server.
-- **Secure** - Prebid.org software should not open doors to security risks, including electronic attack, denial of service, fraud, or data leakage.
-- **Transparent** - Our products are built in the open with community review. Changes to Prebid software and modules must be open to inspection before and after release.
-- **Fair** - The Prebid.org platform doesn’t favor any one entity over another. No entity can be favored over another in technical ordering or status as a default value. No entity can gain information about another entity without approval.
-- **Collaborative** - Human interactions in Prebid.org public forums and events must be courteous. 
-- **Privacy Sensitive** - Our products are built for publishers to support users’ privacy concerns and comply with industry standards.
-
-## Auction Principles
-
-The guidelines in this section apply to open source software written for the Prebid.org platform, or plugins designed to integrate into the Prebid.org platform.
-
-**Definitions:**
-
-- **Publisher**: the party who is integrating the header bidding technology into their page, app, video service, etc. They may integrate Prebid software on their own or through an approved agent.
-- **Publisher Agent**: a party who helps a Publisher integrate or install Prebid software.
-- **Auction Layer**: the part of the system that facilitates bids from demand partners being passed into the decisioning layer.
-- **Demand Partner**: any party that is willing to provide a price to be paid to the Publisher for a given impression, and is integrated into header bidding.
-- **Decisioning Layer**: the part of the system that decides the final winning bid.
-
-![Conduct](/assets/images/code-of-conduct-diagram.png){:class="pb-lg-img"}
-
-### Auction Logic
-
-1. The Auction Layer must not modify bids from Demand Partners unless specifically instructed to do so by configuration. For example, a Publisher might instruct the Auction Layer to:
-    1. Apply a modification that changes the bid from gross to net or;
-    1. Apply a modification that changes the bid from one currency to another;
-    1. Account for a consistent discrepancy;
-    1. Account for managed service fees;
-    1. Drop bids that do not meet the floor requirement
-1. The Auction Layer must provide equal opportunity for all Demand Partners to bid, either by randomizing the order in which they are called, or by requesting bids in the order specified by the publisher.
-    1. Publisher configuration may override which bidders take part in each auction.
-    1. This also specifically covers any situation where a Publisher Agent is also a Demand Partner or a Demand Partner is hosting the Auction Layer.
-1. The Auction Layer must send all demand returned within the configured timeout period to the Decisioning Layer.
-1. The Decisioning Layer must make the final choice of which bid wins unless configured to do otherwise.
-1. The Decisioning Layer can be determined by the Publisher, e.g. It could be an ad server or the same software that implements the Auction Layer, or a proxy server. If decisioning is done in Prebid software, it must conform to all other rules in this section.
-1. The Auction Layer should provide a mechanism or process for Publishers and Demand Partners to validate auction mechanics, including:
-    1. Confirmation that bid requests were sent to Demand Partners
-    1. Confirmation that bid responses were sent to the Decisioning Layer
-    1. Confirmation that the correct bid values were sent to the Decisioning Layer
-    1. Bid timing information such as which Demand Partners met the timeout period
-
-### Data and Transparency
-
-1. The Auction Layer must segregate demand data so there is no opportunity for Demand Partners to have access to other bids or bidder data.
-1. The Auction Layer must pass available bid request information to each configured demand partner, subject to Publisher configuration and privacy regulation controls.
-1. The Auction Layer must not collect and store Publisher or Demand Partner information (such as bid stream information, user information, and Publisher first party data) except in the following cases:
-    1. Passing information to Demand Partners or Analytics Adapters
-    1. Validating header bidding mechanics
-    1. Troubleshooting and diagnosing implementations
-1. The Auction Layer must not record, use, or sell Publisher or Demand Partner data except in accordance with the instructions of the Publisher and the Demand Partner.
-1. The Prebid ecosystem will endeavor to support industry standard privacy regulations, including allowing Publishers to transmit notice, consent, and opt-out state.
-1. Analytics Adapters must not utilize header bidding auction data outside of any agreement they reached with the Publisher.
-
-### User Experience
-
-1. The system should minimize the impact on the user’s web browsing experience.
-1. Users, Publishers and Advertisers deserve a reliable ad serving environment. Prebid software should facilitate data that helps determine if an impression is fraudulent or undisplayable for any reason.
-1. Publishers should be able to utilize Prebid software while adhering to their privacy policies. 
-
-### Adapter Conduct
-
-Prebid software supports different types of ‘plugin’ modules, including for example bid adapters, analytics adapters, user ID modules, real-time-data modules, and others.
-
-1. Adapters of all types must follow all of the above guidelines and specific technical rules defined by the relevant Prebid committee.
-    1. Prebid.js and Prebid Server technical rules are defined by Prebid Module Rules.
-1. As technical rules may change over time, Prebid committees are empowered to force adapters to change specific behaviors as part of major milestone releases. The committees should strive to give the adapter community ample opportunity to weigh in on specific guidelines and ample time to make changes.
-
-## Information and Resources
+## Related Reading
 
 - [Prebid.org Community Code of Conduct](https://prebid.org/code-of-conduct/#community)
 - [Prebid.org Member Companies](https://prebid.org/membership/member-directory/)