Fix doubly redirected pages by script

* Reference the SHA of the pull request HEAD in the checkout.

* Minor content change to validate previews.

.github/workflows/ci.yml

@@ -9,11 +9,14 @@ jobs:
     runs-on: ubuntu-latest
     if: contains(github.event.pull_request.labels.*.name, 'preview')
     steps:
-      - uses: actions/checkout@v1
+      - name: Checkout
+        uses: actions/checkout@v4
         with:
-          ref: "refs/pull/${{ github.event.number }}/merge" # THIS IS INSECURE
+          ref: ${{ github.event.pull_request.head.sha }}
+          fetch-depth: 0
+
       - name: Set up Python
-        uses: actions/setup-python@v1
+        uses: actions/setup-python@v5
         with:
           python-version: '3.X'
       - name: Install dependencies

assets/static/beeware.css

@@ -156,7 +156,7 @@
   }
 
   .navbar-collapse {
-    background: #000;
+    background-color: #343a40;
     padding-top: 0.75em;
   }
 
@@ -353,6 +353,19 @@ blockquote {
 	position: relative;
 }
 
+/* Fix for separators in header menu when display is 760px-and-smaller wide */
+@media (max-width: 760px) {
+  .navbar-collapse li {
+    border-bottom: 1px solid #666;
+  }
+  .navbar-collapse .header-button li.nav-item {
+    border-bottom: 0
+  }
+  .navbar-collapse .header-button {
+    border-bottom: 1px solid #666;
+  }
+}
+
 /*----------------------------------------------------
   Homepage styles
  --------------------------------------------------- */
@@ -369,6 +382,26 @@ blockquote {
   margin: 2rem 0;
 }
 
+/*----------------------------------------------------
+  Project Showcase and Important Category Styles
+ --------------------------------------------------- */
+.showcase {
+  margin: 2vh;
+  font-size: larger;
+}
+
+.important-category {
+  margin: 2vh;
+  padding-bottom: 1rem;
+}
+
+.important-description {
+  margin-bottom: 1.2rem;
+}
+
+.important-projects {
+  padding-left: 1rem;
+}
 
 /*----------------------------------------------------
   Sticky footer styles
@@ -479,6 +512,7 @@ body {
 
 .project img {
   margin-bottom: 2rem;
+  float: left;
 }
 
 /*----------------------------------------------------

content/about/contact/contents.lr

@@ -0,0 +1,23 @@
+_model: page
+---
+title: Contact
+---
+summary: Looking to speak to someone from the BeeWare project? Here's how.
+---
+sort_key: 6
+---
+incomplete: no
+---
+body:
+
+
+If you have a general question about BeeWare usage, we have a number of `community communication channels </community/getting-help/>`__ where you can ask for assistance.
+
+If you need advice on how to contribute, or you have questions about the management of the project, anyone on the `Core Team </community/team>`__ will be able to help you.
+
+If you want to report a security problem with one of the BeeWare tools, please contact the `Core Team </community/team>`__.
+
+If you have had a bad experience in a BeeWare community space, or want to report a behaviour problem with someone who is a member of the BeeWare community, the `Core Team </community/team>`__ will be happy to manage your report in accordance with our `Code of Conduct reporting guide </community/behavior/making-a-coc-complaint/>`__.
+
+For all other enquiries, please contact Founding Apiarist `Russell Keith-Magee <mailto:russell@beeware.org>`__.
+

content/about/contact/media/contents.lr

@@ -0,0 +1,82 @@
+_model: page
+---
+title: Media
+---
+body:
+
+
+Short description
+=================
+
+BeeWare is a collection of tools and libraries to aid in writing application user interfaces in Python.
+
+Long description
+================
+
+BeeWare is a collection of tools and libraries to aid in writing application user interfaces in Python. It enables developers to write applications for iPhone, Android, Linux, macOS and Windows that are indistinguishable from natively written applications.
+
+
+Logos
+=====
+
+BeeWare logo
+~~~~~~~~~~~~
+
+.. image:: /contact/media/beeware-150.png
+    :alt: BeeWare logo
+
+* `Small </contact/media/beeware-150.png>`__
+* `Medium </contact/media/beeware-519.png>`__
+* `Vector </contact/media/beeware.eps>`__
+
+BeeWare (wide) logo
+~~~~~~~~~~~~~~~~~~~
+
+.. image:: /contact/media/beeware-wide-143.png
+    :alt: BeeWare logo (wide)
+
+* `Small </contact/media/beeware-wide-143.png>`__
+* `Medium </contact/media/beeware-wide-600.png>`__
+* `Large </contact/media/beeware-wide-2028.png>`__
+* `Vector </contact/media/beeware-wide.eps>`__
+
+BeeWare Enthusiasts logo
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. image:: /contact/media/beeware-enthusiasts-150.png
+    :alt: BeeWare Enthusiasts logo
+
+* `Small </contact/media/beeware-enthusiasts-150.png>`__
+* `Medium </contact/media/beeware-enthusiasts-600.png>`__
+* `Large </contact/media/beeware-enthusiasts-2000.png>`__
+* `Vector </contact/media/beeware-enthusiasts.eps>`__
+
+Brutus the Bee
+~~~~~~~~~~~~~~
+
+.. image:: /contact/media/brutus-128.png
+    :alt: Brutus the Bee
+
+* `Small </contact/media/brutus-32.png>`__
+* `Medium </contact/media/brutus-128.png>`__
+* `Large </contact/media/brutus-256.png>`__
+* `X-large </contact/media/brutus-1024.png>`__
+* `Vector </contact/media/brutus.eps>`__
+
+---
+summary: Are you from a media organization and want to write something about BeeWare? Here are some resources you may find helpful.
+---
+incomplete: no
+---
+gutter:
+
+Contact
+=======
+
+For all media enquiries, please contact:
+
+ * **Dr Russell Keith-Magee**, Founding Apiarist: `russell@beeware.org <mailto:russell@beeware.org>`__.
+ * **Philip James**, Apiarist: `philip@beeware.org <mailto:philip@beeware.org>`__.
+
+---
+sort_key: 2

content/about/contents.lr

@@ -0,0 +1,27 @@
+_model: page
+---
+title: About BeeWare
+---
+summary: The history and philosophy of the BeeWare Project
+---
+sort_key: 5
+---
+body:
+
+
+BeeWare: The IDEs of Python
+===========================
+
+This is BeeWare. We're incredibly excited about what the future holds for Python. We hope you'll join us on this journey.
+
+
+---
+gutter:
+
+Meet Brutus
+===========
+.. image:: /static/images/brutus-128.png
+
+Brutus the Bee is the mascot of the BeeWare project. He's a busy little worker bee.
+
+Fun fact: a person who keeps bees is called an **apiarist** - a name that the BeeWare project uses to describe the core team. This also reflects the relationship that the core team wishes to have with the community - we're shepherds of the community, and we'll provide direction, but we know the real work is done by the community as a whole.

content/about/goal/contents.lr

@@ -0,0 +1,73 @@
+_model: page
+---
+title: Goals
+---
+summary: The goals of the BeeWare Project
+---
+sort_key: 5
+---
+body:
+
+
+The goal
+========
+
+The end goal of the BeeWare project: To be able to do for mobile and desktop user-facing software the same thing that Django has done for web software - to put into the hands of users a set of tools and libraries that enables them to develop rich, native user interfaces, and deploy them to their devices. This includes:
+
+ * Tools to enable Python to run on different devices,
+ * Tools to package a Python project so it can run on those devices,
+ * Libraries to access the native widgets and capabilities of devices,
+ * Tools to help develop, debug, analyze and these projects.
+
+This aim is that this set of tools will be easy enough to use for complete newcomers to use in a Django Girls-like setting; but powerful enough that they could be used to drive the next Instagram, Pinterest or Disqus.
+
+Most importantly, it aims to do all this as an Open Source community. The Open Source development process has proven itself to be the most reliable way to develop robust and reliable software, and the fact that anyone can access the software means that everyone can start with the same set of excellent tools, be they expert or enthusiastic amateur.
+
+Python everywhere
+~~~~~~~~~~~~~~~~~
+
+A modern computing project can't ignore the biggest development in computing of the last 10 years. Python prides itself on being a cross-platform language. 10 years ago, being cross-platform meant being available for Windows, macOS and Linux. These days, mobile computing is much more important. Despite this, there aren't many good options for Python programming on mobile platforms, and cross-platform mobile coding is still elusive.
+
+BeeWare embraces mobile and other emerging platforms (like watches and set-top-boxes) as a first class citizen of the computing ecosystem - because if people have these devices, why shouldn't they be able to write software for them in Python.
+
+Native everywhere
+~~~~~~~~~~~~~~~~~~
+
+It's easy to use themes to achieve cross-platform. However, it's easy to spot apps that have been built using themes - they're the ones that don't behave quite like any other app. Widgets don't look *quite* right, or there's a menu bar on a window in an OS X app. Themes can get quite close - but there are always telltale signs.
+
+On top of that, native widgets are always faster than a themed generic widget. After all, you're using native system capability that has been tuned and optimized, not a drawing engine that's been layered on top of a generic widget.
+
+Themes also miss many of the accessibility benefits of native platforms. Modern OS authors spend a lot of time tuning affordances for people with impaired mobility, vision or cognition. If you use native widgets, you usually get these affordances for free. If you reimplement widgets with a theme, you also have to re-implement the affordances.
+
+BeeWare uses native widgets and native functionality, rather than using a theme-based approach to application development.
+
+Python native
+~~~~~~~~~~~~~
+
+BeeWare is also an unapologetically "Python first" framework. We like Python. We like the way it looks, and the way it works. If Python isn't available as a first-class option on a particular platform, we'll do whatever is necessary to make Python available as a development language. And when we have the opportunity to embrace Python idiom for an API or a design, we're going to do just that. That means we're going to use generators, context managers, `yield from` asynchronous calls, and more, in order to provide the best Python-native API for cross-platform app development.
+
+We're also looking to the future - this means that we support Python 3 exclusively.
+
+Native experience
+~~~~~~~~~~~~~~~~~
+
+The experience of using any tool starts with the installation process. Part of BeeWare's "Native everywhere" philosophy is adopting appropriate native mechanisms for installation. If you're using a user-space tool, it should be presented to you as a package that is to be installed in the same way you would install any other tool - be that through an app store, an installer, or a simple executable package. End users shouldn't know that you've written the application in Python.
+
+But if you're using a developer tool or library, then it should integrate with your development environment. And since we're using Python, that means you should be able to install it into your virtual environment using `pip install` and nothing more. No C-extensions, no compilers, no setting system paths or environment variables - Just install it, import it, and start writing (or running) code.
+
+---
+gutter:
+
+* `The Goal`_
+   - `Python everywhere`_
+   - `Native everywhere`_
+   - `Python native`_
+   - `Native experience`_
+
+
+.. _`The Goal`: ./#the-goal
+.. _`Python everywhere`: ./#python-everywhere
+.. _`Native everywhere`: ./#native-everywhere
+.. _`Python native`: ./#python-native
+.. _`Native experience`: ./#native-experience
+

content/about/history/contents.lr

@@ -0,0 +1,61 @@
+_model: page
+---
+title: History and Philosophy
+---
+summary: The history and philosophy of the BeeWare Project
+---
+sort_key: 5
+---
+body:
+
+History
+=======
+
+The BeeWare project started with a simple question: Why aren't the tools that we use as Python developers improving at the same rate as the rest of the technology we use on a daily basis?
+
+Python has proven itself as a highly capable language - approachable for newcomers, but powerful in the hands of experts. Python is rapidly becoming a major part of the data analysis, scientific computing, and web development landscape. And initiatives like `Django Girls`_ have demonstrated that using Python, it is possible to provide a 1-day training courses that introducing people with no programming experience to Python; and at the end of a day, attendees have developed and deployed a database-backed dynamic website, deployed to a publicly visible server.
+
+.. _Django Girls: https://djangogirls.org/
+
+However, the developer experience for someone writing Python sometimes reflects more of the early 90's than the new millennium. The default development environment for Python is still an 80x25 console window. For users who have come from a Windows or Apple environment, where they're used to highly detailed, well designed graphical interfaces, this 30 year flashback can be a completely alien experience.
+
+And, yes, there are IDEs (Integrated Development Environments) that provide a native application experience for writing code. But those tools require you to adopt, wholesale, the IDE's way of looking at a project. They often introduce as many headaches to the development process as they solve.
+
+And so, we're left with an interesting schism, between the "old way" of Unix development in a console window, and the "new way" of all-in-one IDEs.
+
+The Unix Philosophy
+~~~~~~~~~~~~~~~~~~~
+
+However, it doesn't have to be that way. The core tenet of the Unix Philosophy is that "each tool does one thing, well". This is a very powerful philosophy, and it enables the composition of extremely powerful toolchains by putting together a suite of extremely focussed, independent tools.
+
+Unfortunately, most UNIX tools have convolved this to also mean "all tools must use a console interface". However, there's nothing in the UNIX philosophy that says that tools have to use a console interface - it's just turned out that way.
+
+The BeeWare project started with the premise we can have the best of both worlds. We can have a chain of composable tools that each do one thing, well. But those tools can also expose their functionality using a rich graphical user interface.
+
+More than just code
+===================
+
+It's about more than just code, though. A successful software project requires documentation, design skills, feedback and bug reports. The BeeWare community acknowledges that *all* contributions are important - not just the ones that come as a pull request on GitHub.
+
+Even then, it's easy to think of a project in a vacuum, as the sum of all contributions. But that's never the case. An open source project is about community.
+
+Diversity and inclusion
+~~~~~~~~~~~~~~~~~~~~~~~
+
+A diverse community is a strong community. This means accepting people of all levels of experience, from all backgrounds, of all races, creeds, orientations and expressions. The BeeWare project is committed to developing and maintaining a inclusive, diverse and welcoming community.
+
+To back this up, we have an open offer to mentor anyone who wants to get involved as a contributor, and a `Code of Conduct`_ that is rigorously enforced. Any reports of violations of that code of conduct - even by senior community members - will be treated with respect and actioned appropriately.
+
+.. _Code of Conduct: /community/behavior/code-of-conduct/
+
+Healthy and sustainable
+~~~~~~~~~~~~~~~~~~~~~~~
+
+It's also important to make sure that the community is accessible and sustainable. It's unfortunately become an accepted part of Open Source culture that "true" Open Source projects have to be developed entirely by volunteers. This acts as a barrier to entry for many groups - the only people able to spend their free time volunteering are those that *have* free time.
+
+It also frequently leads to burnout and other mental health issues amongst contributors. The fact that depression, anxiety, and burnout are so common in software development communities shouldn't be considered a badge of honour, or a demonstration of how committed a development team can be. It's a problem that needs to be tackled head on, and addressed in the same way a software bug would be addressed - with immediate workarounds, and long term plans to remove the systemic cause of the problem.
+
+While we place incredible value on the contributions of volunteers, we also know that volunteer efforts alone aren't the way to develop a healthy and sustainable community. For that reason, financial sustainability is a key consideration in the operation of the BeeWare project. As a community, we don't ignore the role that money has to play in providing the resources that allows people to begin and continue to contribute. We will, as a community, provide accepted mechanisms for individuals to monetize their work in meaningful ways, and wherever possible, compensate people for their work - without compromising the ideals of Open Source development.
+
+
+

content/about/overview/contents.lr

@@ -0,0 +1,46 @@
+_model: page
+---
+title: What is BeeWare?
+---
+body:
+
+
+Python has proven itself as a highly capable language - approachable for newcomers, but powerful in the hands of experts. The BeeWare Project aims to take the power of Python as a language, and use it to enable users of all skill levels to develop applications with native user interfaces.
+
+The end goal of the BeeWare project: To be able to do for mobile and desktop user-facing software the same thing that Django has done for web software - to put into the hands of users a set of tools and libraries that enables them to develop rich, native user interfaces, and deploy them to their devices. This includes:
+
+* Tools to enable Python to run on different devices,
+* Tools to package a Python project so it can run on those devices,
+* Libraries to access the native widgets and capabilities of devices,
+* Tools to help develop, debug, analyze and deploy these projects.
+
+The aim is that this set of tools will be easy enough to use for complete newcomers to use in a Django Girls-like setting; but powerful enough that they could be used to drive the next Instagram, Pinterest or Disqus.
+
+We're not just about software, though. We also aim to be a project with a social conscience. We aim to develop and maintain a diverse and inclusive community, and we have a Code of Conduct that is rigorously enforced. We also aspire to develop a healthy and sustainable community - one that is aware of mental health issues of its participants, and provides the resources for people to start engaging, and continue to engage with the community.
+
+Where to from here?
+===================
+
+If you'd like to know more about the history of BeeWare, `start here </project/about/>`__.
+
+If you'd like to take BeeWare for a test drive, `take a look at the the various ways BeeWare tools can be used </project/using/>`__.
+
+If you'd like to keep up to date with what we're doing, follow `@beeware@fosstodon.org <https://fosstodon.org/@beeware>`__ on Mastodon. If you'd like to receive updates, hints, tips and announcements about the BeeWare project, `sign up for the Beeware Enthusiasts mailing list  </community/keep-informed/>`__.
+
+---
+gutter:
+
+Next steps
+==========
+
+* The `History of the BeeWare project  </project/about/>`__
+* `BeeWare test drive </project/using/>`__
+* `@beeware@fosstodon.org on Mastodon <https://fosstodon.org/@beeware>`__
+* The `Beeware Enthusiasts mailing list  </community/keep-informed/>`__
+
+---
+incomplete: no
+---
+sort_key: 1
+---
+summary: A first-timer's introduction to the BeeWare project

content/about/team/cflee/contents.lr

@@ -0,0 +1,24 @@
+name: Chiang Fong Lee
+---
+description:
+
+Chiang Fong has been pretending to be a systems administrator since the Mandriva Linux days, and has recently moved into acting like he knows how to write software.
+
+When not poking at code to de-stress, he spends his time fiddling with fountain pens and mechanical keyboards.
+He has yet to learn the lesson of not mixing inky fingers with pretty keycaps.
+---
+email: myself@cflee.net
+---
+github_handle: cflee
+---
+twitter_handle: cflee
+---
+mastodon_handle: @cflee@hachyderm.io
+---
+join_date: 2017-03-11
+---
+summary: cflee
+---
+superpower: voc
+---
+emeritus_date: 2020-06-01

content/about/team/contents.lr

@@ -0,0 +1,9 @@
+_model: team
+---
+sort_key: 2
+---
+title: The Bee Team
+---
+summary: The core team behind BeeWare development
+---
+body: So who are the people behind BeeWare? Well, there's a huge group of contributors, but the project is managed by the Bee Team.

content/about/team/danyeaw/contents.lr

@@ -0,0 +1,24 @@
+name: Dan Yeaw
+---
+join_date: 2018-02-28
+---
+twitter_handle: danyeaw
+---
+mastodon_handle: @danyeaw@fosstodon.org
+---
+description:
+
+Dan leads teams to design safety in to complex automotive and mobility systems, and dreams of using BeeWare tools to help model these systems.
+
+When not hacking on open source projects, Dan likes to hang with his kids, brew beer, and play soccer.
+---
+github_handle: danyeaw
+---
+email: dan@yeaw.me
+---
+superpower: toga, lektor
+---
+summary: Submarine Bubblehead
+---
+emeritus_date: 2021-05-01
+

content/about/team/elias/contents.lr

@@ -0,0 +1,19 @@
+name: Elias Dorneles
+---
+description:
+
+Elias is a certified yak-shaver. He likes to fiddle with Python and open source stuff. At home, he likes to read, cook and to play Beatles songs on his guitar.
+
+Elias gets by with a little help from his friends.
+---
+email: eliasdorneles@gmail.com
+---
+github_handle: eliasdorneles
+---
+join_date: 2017-03-01
+---
+summary: Yak-shaver
+---
+superpower: voc, android
+---
+emeritus_date: 2020-06-03

content/about/team/flowerncsu/contents.lr

@@ -0,0 +1,17 @@
+description: Charlotte has been coding for more years than she likes to admit, and has a passion for building cool things and helping other people learn how to build cool things. She is among the organizers of PyLadies RDU, and can often be found making things out of yarn when not making things out of code.
+---
+name: Charlotte Mays
+---
+twitter_handle: charlottecodes
+---
+mastodon_handle: @charlotte@hachyderm.io
+---
+summary:
+---
+join_date: 2017-08-17
+---
+github_handle: flowerncsu
+---
+email: charlotte@charlottemays.me
+---
+superpower: cricket

content/about/team/freakboy3742/contents.lr

@@ -0,0 +1,17 @@
+description: Dr Russell Keith-Magee is the founder of the BeeWare project. He joined the Django core team since 2006, and for 5 years, was President of the Django Software Foundation. When he's not contributing to open source, he's a Principal Software Engineer in the Open Source group at Anaconda.
+---
+name: Russell Keith-Magee
+---
+twitter_handle: freakboy3742
+---
+summary: Founding Apiarist
+---
+join_date: 2013-09-05
+---
+github_handle: freakboy3742
+---
+email: russell@beeware.org
+---
+superpower: bdfn
+---
+mastodon_handle: @freakboy3742@cloudisland.nz

content/about/team/glasnt/contents.lr

@@ -0,0 +1,21 @@
+name: Katie McLaughlin
+---
+join_date: 2016-04-02
+---
+twitter_handle: glasnt
+---
+mastodon_handle: @glasnt@cloudisland.nz
+---
+description:
+
+Katie has worn many different hats over the years. She has previously been a software developer for many languages, systems administrator for multiple operating systems, and speaker on many different topics.
+
+When she's not changing the world, she enjoys cooking, making tapestries, and seeing just how well various application stacks handle emoji.
+---
+github_handle: glasnt
+---
+email: katie@beeware.org
+---
+superpower: batavia, lektor, senior
+---
+summary: Tasmanian Devil Wrangler

content/about/team/hawkowl/contents.lr

@@ -0,0 +1,21 @@
+description:
+
+Amber Brown pretends to be an owl on the internet.
+When she's not releasing or working on Twisted, she works on software for various commercial and non-profit companies.
+She's so good at talking endlessly about Twisted that Russell even once invited her to keynote on it.
+
+Also, she likes people tweeting pictures of owls at her.
+---
+name: Amber Brown
+---
+twitter_handle: hawkieowl
+---
+summary: Owl-themed Toga Widget Simulator
+---
+join_date: 2016-10-13
+---
+github_handle: hawkowl
+---
+email: hawkowl@atleastfornow.net
+---
+superpower: toga, lektor

content/about/team/mhsmith/contents.lr

@@ -0,0 +1,13 @@
+name: Malcolm Smith
+---
+join_date: 2022-08-31
+---
+twitter_handle:
+---
+description: Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+---
+github_handle: mhsmith
+---
+email: smith@chaquo.com
+---
+superpower: android

content/about/team/obulat/contents.lr

@@ -0,0 +1,17 @@
+name: Olga Bulat
+---
+join_date: 2018-03-05
+---
+twitter_handle: bulat_olga
+---
+description:
+
+Olga is a python and BeeWare enthusiast, also interested in NLP, geography and languages. 
+
+She also enjoys hanging out with kids.
+---
+github_handle: obulat
+---
+email: obulat@gmail.com
+---
+superpower: toga

content/about/team/phildini/contents.lr

@@ -0,0 +1,17 @@
+name: Philip James
+---
+description: Philip writes code for computers and for humans. His first computing love is Python, but is too often forced to write JavaScript and Swift. When he's not writing code for money or for Open Source or for his own crazy projects, he gives talks at conferences. Philip lives in Alameda, California with his wife and her cat. Philip believes in the web.
+---
+join_date: 2016-06-03
+---
+summary:
+---
+twitter_handle: phildini
+---
+mastodon_handle: @phildini@phildini.net
+---
+github_handle: phildini
+---
+email: philip@beeware.org
+---
+superpower: batavia, senior

content/about/team/rmartin16/contents.lr

@@ -0,0 +1,13 @@
+name: Russell Martin
+---
+join_date: 2022-08-31
+---
+twitter_handle:
+---
+description: Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+---
+github_handle: rmartin16
+---
+email: rmartin16@gmail.com
+---
+superpower: briefcase

content/about/team/samschott/contents.lr

@@ -0,0 +1,18 @@
+name: Sam Schott
+---
+description: Sam is a physicist and a software engineer. He got introduced
+to Python while automating data acquisition in the lab and soon realised
+that he enjoyed writing and sharing code. When away from a computer,
+you will find him hiking or sailing along the English coast.
+---
+join_date: 2021-07-29
+---
+summary:
+---
+twitter_handle:
+---
+github_handle: samschott
+---
+email: sam.schott@outlook.com
+---
+superpower: toga

content/about/team/saroad2/contents.lr

@@ -0,0 +1,15 @@
+name: Sagi Shadur
+---
+description: Sagi Shadur is a software engineer and a mathematician. He has a B.Sc. in mathematics and these days he's on his way for a second B.Sc. in physics. He's also a poet who published two books in Hebrew, "Mountains and Valleys" and "The Emissary".
+---
+join_date: 2020-05-31
+---
+summary:
+---
+twitter_handle:
+---
+github_handle: saroad2
+---
+email: saroad2@gmail.com
+---
+superpower: toga

content/about/team/swenson/contents.lr

@@ -0,0 +1,26 @@
+description:
+
+Dr. Christopher Swenson is a software engineer, computer scientist, and occasional mathematician.
+Swenson has been working with Python since about 2004, and involved in open source since before knowing what open source really was.
+Swenson likes sorting a lot, and maintains an open source high-performance C sorting library.
+Swenson has sold their labor to companies big and small, such as Simple, Google, and the US Government, and wrote a book on cryptography.
+Swenson is an organizer of PyDX.
+Swenson is a cupcake.
+---
+name: Christopher Swenson
+---
+twitter_handle: chris_swenson
+---
+mastodon_handle: @chris_swenson@tweets.icu
+---
+summary: Cupcake
+---
+join_date: 2016-09-07
+---
+github_handle: swenson
+---
+email: swenson@beeware.org
+---
+superpower: batavia
+---
+emeritus_date: 2021-05-01

content/batavia/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /batavia/
----
 new_path: /project/projects/bridges/batavia/
 ---
 _discoverable: no

content/bee/join/contents.lr

@@ -1,5 +1,5 @@
 _model: redirect
 ---
-old_path: /join/
+new_path: /membership/
 ---
-new_path: /contributing/membership/
+_discoverable: no

content/bee/podium/contents.lr

@@ -1,5 +1,5 @@
 _model: redirect
 ---
-old_path: /podium/
+new_path: /project/applications/podium/
 ---
-new_path: /project/projects/applications/podium/
+_discoverable: no

content/beefore/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /beefore/
----
-new_path: /project/projects/tools/beefore/
+new_path: /project/attic/beefore/
 ---
 _discoverable: no

content/beekeeper/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /beekeeper/
----
-new_path: /project/projects/tools/beekeeper/
+new_path: /project/attic/beekeeper/
 ---
 _discoverable: no

content/briefcase/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /briefcase/
----
-new_path: /project/projects/tools/briefcase/
+new_path: /project/briefcase/
 ---
 _discoverable: no

content/bugjar/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /bugjar/
----
-new_path: /project/projects/tools/bugjar/
+new_path: /project/applications/bugjar/
 ---
 _discoverable: no

content/cassowary/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /cassowary/
----
-new_path: /project/projects/attic/cassowary/
+new_path: /project/attic/cassowary/
 ---
 _discoverable: no

content/colosseum/contents.lr

@@ -1,7 +1,5 @@
 _model: redirect
 ---
-old_path: /colosseum/
----
-new_path: /project/projects/libraries/colosseum/
+new_path: /project/utilities/colosseum/
 ---
 _discoverable: no

content/community/behavior/code-of-conduct/contents.lr

@@ -23,14 +23,18 @@ By adopting this Code of Conduct, project maintainers commit themselves to fairl
 
 This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
 
-To report an issue, please see `Making a CoC Complaint </community/behavior/making-a-coc-complaint>`__
-
+If you feel the code of conduct has been violated, please `report the incident </code-of-conduct/making-a-coc-report/>`__ to the Beeware core team.
 
 ---
 summary: All participants in the BeeWare community are expected to adhere to a Code of Conduct
 ---
 gutter:
 
+`Making a Code of Conduct Report </code-of-conduct/making-a-coc-report/>`__
+-----------------------------------------------------------------------------------------------
+
+Has something or someone in the BeeWare community made you feel uncomfortable? Here's how to report the situation.
+
 Credits
 -------------
 

content/community/behavior/making-a-coc-complaint/contents.lr

@@ -1,74 +1,5 @@
-_model: page
+_model: redirect
 ---
-title: Making a CoC complaint
+new_path: /community/behavior/making-a-coc-report/
 ---
-body:
-
-If you believe someone is violating the `BeeWare Project Code of Conduct </community/behavior/code-of-conduct/>`__ we ask that you report it to the BeeWare Project by emailing one or more of the project maintainers (listed in the sidebar). All reports will be kept confidential. In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
-
-**If you believe anyone is in physical danger, please notify appropriate law enforcement first**. If you are unsure what law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.
-
-In your report please include:
-
- * **Your contact info** (so we can get in touch with you if we need to follow up)
- * **Names (real, nicknames, or pseudonyms) of any individuals involved**. If there were other witnesses besides you, please try to include them as well.
- * **When and where the incident occurred**. Please be as specific as possible.
- * **Your account of what occurred**. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link.
- * **Any extra context** you believe existed for the incident.
- * If you believe this incident is ongoing.
- * If you believe any member of the core team has a conflict of interest in adjudicating the incident.
- * What, if any, corrective response you believe would be appropriate.
- * Any other information you believe we should have.
-
-Core team members are obligated to maintain confidentiality with regard to the reporter and details of an incident.
-
-What happens after you file a report?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You will receive an email acknowledging receipt of your complaint. We promise to acknowledge receipt within 24 hours (and will aim for much quicker than that).
-
-The core team will immediately meet to review the incident and determine:
-
- * What happened.
- * Whether this event constitutes a code of conduct violation.
- * Who the bad actor was.
- * Whether this is an ongoing situation, or if there is a threat to anyone's physical safety.
- * If this is determined to be an ongoing incident or a threat to physical safety, the working groups' immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.
-
-If a member of the core team is one of the named parties, they will not be included in any discussions, and will not be provided with any confidential details from the reporter.
-
-If anyone on the core team believes they have a conflict of interest in adjudicating on a reported issue, they will inform the other core team members, and recuse themselves from any discussion about the issue. Following this declaration, they will not be provided with any confidential details from the reporter.
-
-Once the working group has a complete account of the events they will make a decision as to how to response. Responses may include:
-
-* Nothing (if we determine no violation occurred).
-* A private reprimand from the working group to the individual(s) involved.
-* A public reprimand.
-* An imposed vacation (i.e. asking someone to "take a week off" from a mailing list or IRC).
-* A permanent or temporary ban from some or all BeeWare spaces (GitHub repositories, Discord, etc.)
-* A request for a public or private apology.
-
-We'll respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved.
-
-Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but we don't guarantee we'll act on it.
-
-Finally, depending on the specifics of the incident and the potential for ongoing harm, the core team may choose to make a public report of the incident on `The Buzz`_, the BeeWare blog.
-
-.. _The Buzz: /news/buzz/
-
----
-summary: Has something or someone in the BeeWare made you feel uncomfortable? Here's how to report the problem.
----
-gutter:
-
-
-Reporting contacts
-~~~~~~~~~~~~~~~~~~~
-* `Russell Keith-Magee <mailto:russell@beeware.org>`__
-* `Katie McLaughlin <mailto:katie@beeware.org>`__
-* `Philip James <mailto:philip@beeware.org>`__
-
-Credits
-~~~~~~~
-This reporting guide draws heavily from the `Django Software Foundation Code of Conduct Reporting Guide <https://www.djangoproject.com/conduct/reporting/>`__. The BeeWare Project thanks the DSF, and the DSF Code of Conduct Committee for their work in drafting this document.
-
+_discoverable: no