atopile 0.3.7.dev0__tar.gz → 0.3.9.dev0__tar.gz

atopile-0.3.9.dev0/.cursorrules

@@ -0,0 +1,18 @@
+You an expert Python programmer, cpp programmer and electrical engineer.
+
+You are developing an application called "atopile", which is a tool to design PCBs using a new language called "ato", or in Python with a framework called "fabll".
+
+You will follow the following rules and best practices during development:
+
+- When directed to "consider" something, assume it's an imperfect suggestion. Contemplate whether it's a good idea, and if it's not, suggest an alternative with reasoning.
+- Add comments to your code such that a future developer, also an expert in the field, but without the immediate context of the reason for development can understand the code.
+
+## Test Writing
+
+- Use pytest best practices
+- Use `pytest.mark.parametrize` to run tests on multiple inputs, rather than for loops within the a single test function
+- Run tests you have created or modified with `pytest <path_to_test_file>::<test_name>`
+- If you have made large changes, run the most appropriate of:
+  - `pytest -m <module_name>` for a single modules' changes
+  - `pytest -m "not regression"` to run all tests except for LONG regression tests
+  - `pytest` to run all tests

atopile-0.3.7.dev0/.github/workflows/wheels.yml → atopile-0.3.9.dev0/.github/workflows/deploy.yml

@@ -1,6 +1,6 @@
 # Taken from https://github.com/pybind/scikit_build_example/blob/master/.github/workflows/wheels.yml
 
-name: Wheels
+name: deploy
 
 on:
   workflow_dispatch:
@@ -88,10 +88,12 @@ jobs:
         path: wheelhouse/*.whl
 
 
-  upload_all:
-    name: Upload if release
+  publish_wheels:
+    name: Publish Wheels
     needs: [build_wheels, build_sdist]
     runs-on: ubuntu-latest
+    # Publish wheels properly on release
+    # or to testpypi on main branch pushes to validate the workflow
     if: github.event_name == 'release' && github.event.action == 'published' || github.event_name == 'push' && github.ref == 'refs/heads/main'
     environment: pypi
     permissions:
@@ -123,3 +125,62 @@ jobs:
       uses: pypa/gh-action-pypi-publish@release/v1
       with:
         attestations: true
+
+
+  docker:
+    name: Docker Build and Publish
+    runs-on: ubuntu-latest
+    needs: build_wheels
+
+    strategy:
+      matrix:
+        include:
+          - dockerfile: "Dockerfile.kicad"
+            image: "atopile-kicad"
+
+    # Sets the permissions granted to the `GITHUB_TOKEN`
+    # for the actions in this job.
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Download wheel artifacts
+        uses: actions/download-artifact@v4
+        with:
+          pattern: cibw-*
+          merge-multiple: true
+          path: dist
+
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: |
+            ghcr.io/atopile/${{ matrix.image }}
+          flavor: |
+            latest=${{github.event_name == 'release' && github.event.action == 'published' && !github.event.release.prerelease && !github.event.release.draft}}
+          tags: |
+            type=ref,event=branch
+            type=ref,event=pr
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=sha
+
+      - name: Log in to the Container registry
+        uses: docker/login-action@0d4c9c5ea7693da7b068278f7b52bda2a190a446
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build and push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          file: dockerfiles/${{ matrix.dockerfile }}
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}

{atopile-0.3.7.dev0 → atopile-0.3.9.dev0}/.github/workflows/pre-commit.yml

@@ -2,6 +2,10 @@ name: pre-commit
 
 on:
   push:
+    branches:
+      - main
+  pull_request:
+  workflow_dispatch:
 
 jobs:
   pre-commit:

{atopile-0.3.7.dev0 → atopile-0.3.9.dev0}/.github/workflows/pytest.yml

@@ -2,6 +2,10 @@ name: pytest
 
 on:
   push:
+    branches:
+      - main
+  pull_request:
+  workflow_dispatch:
 
 jobs:
   pytest:
@@ -29,12 +33,36 @@ jobs:
     - name: Setup cmake
       uses: jwlawson/actions-setup-cmake@v2
 
+    # Required by examples
+    # TODO: remove dependency on global fp-lib-table
+    - name: Configure AWS Credentials
+      uses: aws-actions/configure-aws-credentials@v4
+      with:
+        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
+        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+        aws-region: ${{ secrets.AWS_REGION }}
+
+    - name: Prepare test environment
+      run: |
+        mkdir -p ~/.config/kicad/8.0/
+        aws s3 cp "s3://${{ secrets.TEST_DATASET_BUCKET }}/kicad-8.0-fp-lib-table" ~/.config/kicad/8.0/fp-lib-table
+
+        mkdir -p /usr/share/kicad/
+        aws s3 cp "s3://${{ secrets.TEST_DATASET_BUCKET }}/kicad-8.0-footprints.tar.gz" - | tar -xz -C /usr/share/kicad/
+
     - name: Run pytest
       id: pytest
       continue-on-error: true
-      run: |
-        uv run --dev --no-editable --frozen pytest -m "not not_in_ci and not slow and not regression" --timeout=300
+      run: >
+        uv run --dev --no-editable --frozen
+        --with pytest-github-actions-annotate-failures
+        pytest
+        -m "not not_in_ci and not slow and not regression"
+        --timeout=300
       env:
+        GH_TOKEN: ${{ github.token }}
+        PYTEST_HISTORY_EMAIL: ${{ vars.PYTEST_HISTORY_EMAIL }}
+        PYTEST_HISTORY_PASSWORD: ${{ secrets.PYTEST_HISTORY_PASSWORD }}
         COLUMNS: 150  # rich console width will be pulled from this
 
     - name: Upload all test logs

atopile-0.3.9.dev0/.github/workflows/website.yml

@@ -0,0 +1,66 @@
+name: website-deploy
+on:
+  push:
+    branches:
+      - main
+  release:
+    types: [published]
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    environment: github-pages
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Required for mike to work with git history
+
+      - name: Configure Git Credentials
+        run: |
+          git config user.name github-actions[bot]
+          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version-file: 'pyproject.toml'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          version: '0.5.5'
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+
+      - name: Get version
+        id: get_version
+        # Uses hatch rather than ato to get the version
+        # because currently ato might also produce logging output
+        # which contaminates stdout
+        run: |
+          VERSION=$(uv run --dev hatch version)
+          MAJOR_MINOR=$(echo $VERSION | cut -d. -f1,2)
+          echo "VERSION=$VERSION" >> $GITHUB_ENV
+          echo "MAJOR_MINOR=$MAJOR_MINOR" >> $GITHUB_ENV
+
+      # FIXME: enable deployment access restrictions
+      # - enforce https://github.com/atopile/atopile/settings/rules/3213715
+      # - specify the --remote in `mike deploy` to include the app token https://stackoverflow.com/questions/18935539/authenticate-with-github-using-a-token
+      # - uses: actions/create-github-app-token@v1
+      #   id: app-token
+      #   with:
+      #     app-id: ${{ vars.WEBSITE_DEPLOYER_APP_ID }}
+      #     private-key: ${{ secrets.WEBSITE_DEPLOYER_KEY }}
+
+      - name: Deploy development docs
+        if: github.event_name == 'push'
+        # TODO: it'd be nice to have the upcoming version number here as well
+        # but it clobbers the latest release in case they're the same
+        run: uv run mike deploy --push --update-aliases dev
+
+      - name: Deploy release docs
+        if: github.event_name == 'release' && !github.event.release.prerelease && !github.event.release.draft
+        run: uv run mike deploy --push --update-aliases $MAJOR_MINOR latest

{atopile-0.3.7.dev0 → atopile-0.3.9.dev0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atopile
-Version: 0.3.7.dev0
+Version: 0.3.9.dev0
 Summary: A toolchain bringing the best of software development to the real-world!
 Project-URL: Homepage, https://github.com/atopile/atopile
 Project-URL: Bug Tracker, https://github.com/atopile/atopile/issues
@@ -48,7 +48,7 @@ Requires-Dist: isort<5.14.0,>=5.6.4
 Requires-Dist: jinja2>=3.1.3
 Requires-Dist: kicadcliwrapper<2.0.0,>=1.0.0
 Requires-Dist: matplotlib<4.0.0,>=3.7.1
-Requires-Dist: more-itertools<10.6,>=10.4
+Requires-Dist: more-itertools<10.7,>=10.4
 Requires-Dist: natsort>=8.4.0
 Requires-Dist: numpy<3.0.0,>=2.2.0
 Requires-Dist: packaging>=23.2
@@ -56,6 +56,7 @@ Requires-Dist: pandas>=2.1.4
 Requires-Dist: patool<2.4.0,>=2.3.0
 Requires-Dist: pint<1.0.0,>=0.24.4
 Requires-Dist: psutil<7.0.0,>=6.0.0
+Requires-Dist: pydantic-settings>=2.7.1
 Requires-Dist: pygls>=1.3.0
 Requires-Dist: quart-cors>=0.7.0
 Requires-Dist: quart-schema[pydantic]>=0.20.0

{atopile-0.3.7.dev0 → atopile-0.3.9.dev0}/dockerfiles/Dockerfile.kicad

@@ -34,8 +34,8 @@ COPY --from=ghcr.io/astral-sh/uv:0.5.5 /uv /bin/uv
 # @python3.14
 RUN uv python install 3.13
 
-COPY --chown=kicad:kicad dist/atopile-*.whl /tmp/
+COPY --chown=kicad:kicad dist/atopile-*-cp313-cp313-manylinux*.whl /tmp/
 
-RUN uv tool install /tmp/atopile-*.whl
+RUN uv tool install /tmp/atopile-*-cp313-cp313-manylinux*.whl
 
 ENTRYPOINT [ "bash", "-c", "ato install && ato build" ]

atopile-0.3.9.dev0/docs/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Change Log
+
+## v0.3.x
+
+Firstly, thanks for using atopile! It's been a ride, and we're glad you're here. 🙌
+
+### Changed Commands
+
+Add `--help` after any command to see new options in the CLI. This is always the most accurate source of information.
+
+| Old | New |
+|-----|-----|
+| `ato install --jlcpcb` | `ato create component` |
+
+
+### I'm seeing a bunch of `DeprecationWarning`
+
+There will be a LOT of new deprecation warnings you'll see.
+
+For the most part, it's safe to ignore them for the minute, and we plan to make the breaking changes in 0.4.0
+
+Upgrading will give you more access to features as they're added, but there's no need to rush if you're content.
+
+### PCBs are now directly modified
+
+This means no more need to open the PCB file, import the netlist and cycle.
+
+`ato build` now directly modifies the PCB file as required on each build.

atopile-0.3.9.dev0/docs/CNAME

@@ -0,0 +1 @@
+docs.atopile.io

atopile-0.3.9.dev0/docs/assets/logo/emblem-white.svg

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg id="Layer_2" data-name="Layer 2" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 264.12 264.12">
+  <defs>
+    <style>
+      .cls-1 {
+        fill: #fff;
+        stroke-width: 0px;
+      }
+    </style>
+  </defs>
+  <g id="_Слой_1" data-name="Слой 1">
+    <g>
+      <rect class="cls-1" x="0" y="229.39" width="57.39" height="34.73" rx="2.5" ry="2.5" transform="translate(57.39 493.5) rotate(180)"/>
+      <path class="cls-1" d="m168.54,26.23V8.5c0-4.7,3.81-8.5,8.5-8.5h78.57c4.7,0,8.5,3.81,8.5,8.5v88.27c0,4.7-3.81,8.5-8.5,8.5h-17.73c-4.7,0-8.5-3.81-8.5-8.5v-53.54c0-4.7-3.81-8.5-8.5-8.5h-43.84c-4.7,0-8.5-3.81-8.5-8.5Z"/>
+      <path class="cls-1" d="m0,147.08v-17.73c0-4.7,3.81-8.5,8.5-8.5h40.38c4.7,0,8.5,3.81,8.5,8.5v37.26c0,4.7,3.81,8.5,8.5,8.5h29.82c4.7,0,8.5,3.81,8.5,8.5v37.26c0,4.7,3.81,8.5,8.5,8.5h108.17c4.7,0,8.5-3.81,8.5-8.5v-56.8c0-4.7-3.81-8.5-8.5-8.5h-45.95c-4.7,0-8.5-3.81-8.5-8.5v-43.42c0-4.7-3.81-8.5-8.5-8.5h-29.67c-4.7,0-8.5-3.81-8.5-8.5v-43.43c0-4.7-3.81-8.5-8.5-8.5h-24.05c-4.7,0-8.5-3.81-8.5-8.5V8.5c0-4.7,3.81-8.5,8.5-8.5h57.25c4.7,0,8.5,3.81,8.5,8.5v43.42c0,4.7,3.81,8.5,8.5,8.5h29.67c4.7,0,8.5,3.81,8.5,8.5v43.42c0,4.7,3.81,8.5,8.5,8.5h47.48c4.7,0,8.5,3.81,8.5,8.5v126.27c0,4.7-3.81,8.5-8.5,8.5H78.95c-4.7,0-8.5-3.81-8.5-8.5v-37.26c0-4.7-3.81-8.5-8.5-8.5h-29.83c-4.7,0-8.5-3.81-8.5-8.5v-37.26c0-4.7-3.81-8.5-8.5-8.5h-6.61c-4.7,0-8.5-3.81-8.5-8.5Z"/>
+      <path class="cls-1" d="m25.08,86.66v-17.73c0-4.7,3.81-8.5,8.5-8.5h61.84c4.7,0,8.5,3.81,8.5,8.5v43.42c0,4.7,3.81,8.5,8.5,8.5h32.03c4.7,0,8.5,3.81,8.5,8.5v37.26c0,4.7,3.81,8.5,8.5,8.5h39.69c4.7,0,8.5,3.81,8.5,8.5v17.73c0,4.7-3.81,8.5-8.5,8.5h-73.46c-4.7,0-8.5-3.81-8.5-8.5v-37.26c0-4.7-3.81-8.5-8.5-8.5h-31.45c-4.7,0-8.5-3.81-8.5-8.5v-43.42c0-4.7-3.81-8.5-8.5-8.5h-28.65c-4.7,0-8.5-3.81-8.5-8.5Z"/>
+      <rect class="cls-1" x="25.08" y="0" width="34.73" height="34.73" rx="2.5" ry="2.5" transform="translate(84.9 34.73) rotate(180)"/>
+    </g>
+  </g>
+</svg>

atopile-0.3.9.dev0/docs/development.md

@@ -0,0 +1,31 @@
+# Development
+
+## Prerequisites
+
+- [Editable atopile install](/guides/installation/#editable-installation-best-for-development)
+
+## Dev Tools
+
+We recommend VSCode for development. If nothing else, it has heaps of high quality extensions and atopile language support, plus it's what we all use internally - so we know how to configure it for purpose.
+
+You should have at minimum:
+- [Cursor](https://www.cursor.com/) or [VSCode](https://code.visualstudio.com)
+- [VSCode atopile extension](https://marketplace.visualstudio.com/items?itemName=atopile.atopile) (also works for Cursor)
+
+### Verbosity
+
+You can increase the verbosity of atopile by using the `-v`, `-vv` or `-vvv` flags, eg. `ato -vv build`
+
+!!! tip "Flag Location"
+    Flags are placed after the `ato` command and before the command you want to run. For example, `ato -vv build` will run the build command with the verbose flag set to the highest level, while `ato build -vv` will not work.
+
+### Debugging
+
+You can start the CLI in debug mode by using the `--debug` flag, eg. `ato --debug build`
+
+This will run a [`debugpy`](https://github.com/microsoft/debugpy) server on port `5678` which you can connect to with the VSCode built-in debugger.
+
+![connect debugger](assets/images/debugger-vscode.png)
+
+??? help "Syntax highlighting isn't working"
+    If you're having trouble with syntax highlighting in the debugger, it might be because VSCode sets up a mapping between the remote and local file paths by default - remove it.

atopile-0.3.9.dev0/docs/guides/faebryk.md

@@ -0,0 +1,24 @@
+# `faebryk` & `fabll` 🐍
+
+`faebryk` is atopile's core. It's how we model the world.
+
+`faebryk` is a Python module that uses a powerful and efficient core graph (nodes + edges) to represent every relationship in your design or circuit.
+
+`fabll` is a Python framework to model circuits, much like `ato`. It unlocks a the whole Turing-complete power of Python to do design in + low-level procedural code and logic. Think of it like writing C for a Python module. It's focus is power - not ease of use like `ato`, so it's not recommended for most designs to start with.
+
+!!! warning
+    `fabll` is currently in a very early stage of development. It's not publicly supported yet.
+
+## Building `fabll` code
+
+To build a `fabll` module with atopile, you just need to point to the module within your `ato.yaml` configuration file.
+
+When you run `ato build`, atopile will automatically build the `fabll` module and link it to your project.
+
+## Importing `fabll` code
+
+You can just import `fabll` modules in `ato` like any other import:
+
+```ato
+from path/to/some/fabll.py import SomeModule
+```

atopile-0.3.9.dev0/docs/guides/git.md

@@ -0,0 +1,50 @@
+# Using `git` for Hardware
+
+`git` is a powerful way to version control your design and one of the key reason we started atopile. If you don't know about `git`, we strongly recommend learning it. There is a high chance you will end up loving it.
+
+## Workflow Overview
+
+`git` is the de-facto standard for version control in software development. For people who haven't used it before, it's worth explaining a few terms and the workflow
+
+| Term | Definition |
+| --- | --- |
+| Repo or Repository | A collection of files and directories that is version controlled together. |
+| Branch | A "branch" is an isolated space for your changes. |
+| Commit | A "commit" is a snapshot of some changes in that place in time. |
+| Push | A "push" is sending your changes to the remote repo. |
+| Pull Request | A "pull request" is a request to merge your changes into the main branch. This is the time to review and test your changes with others on your team. |
+
+```mermaid
+flowchart TD
+    AA[Find a project you want to work on on Github] --> A[**Clone** a copy of the repo to your computer]
+    AB[Create a new project on Github] --> A
+    A --> B["Create an isolated space (or **branch**) for your changes"]
+    B --> C[Do some work ⛏️]
+    C --> D[Check the **status** of your changes]
+    D --> E[**Stage** the changes for one topic]
+    E --> F[**Commit** the changes with a message explaining what you did]
+    F -->|More work to do on this topic| D
+    F -->|Ready for review| H[**Push** your branch to the **remote** repo on Github]
+    H --> I[Create **Pull Request** on GitHub]
+    I --> II["Continuous Integration (**CI**) runs tests and ensures your project still builds after your updates"]
+    II -->|Tests pass| J[**Review** all the changes]
+    II -->|Tests fail| D
+    J -->|Changes requested in review| D
+    J -->|Approved| K[**Merge** to main]
+    K --> L[Your changes are now combined with the work of everyone else on the project]
+```
+
+## Basic Usage
+
+```sh
+git clone <repo-url>
+git checkout -b <new-branch-name>
+git add <file-to-commit>
+git commit -m "This commits adds an LED indicator..."
+git push -u origin HEAD
+```
+
+## More resources
+
+- https://github.com/git-guides
+- https://git-scm.com/docs/gittutorial

atopile-0.3.9.dev0/docs/guides/installation.md

@@ -0,0 +1,38 @@
+# Alternative Installation
+
+!!! warning
+    Check out the [quickstart guide](quickstart.md) for a step-by-step guide for the recommended way to install atopile.
+    This page provides alternative installation methods.
+
+Ultimately `atopile` is a python package, so you can install it where and however you want - but some python package managers are better than others. Here's how we recommend you install atopile.
+
+## Editable installation (Best for development)
+
+1. Install `uv`
+    See: https://docs.astral.sh/uv/getting-started/installation/
+
+3. Clone the repo
+
+    ``` sh
+    git clone https://github.com/atopile/atopile
+    ```
+
+4. `cd` into the repo
+
+    ``` sh
+    cd atopile
+    ```
+
+5. Install
+
+    ``` sh
+    uv sync --dev
+    ```
+
+## Via `brew`
+
+We would recommend this, however it's not yet quite ready
+
+``` sh
+brew install atopile/tap/atopile
+```

atopile-0.3.9.dev0/docs/index.md

@@ -0,0 +1,62 @@
+# Welcome
+
+`atopile` is a language, compiler and toolchain to design electronics with code.
+
+Design circuit boards with the same powerful workflows that software developers use - version control, modularity, and automated validation. Instead of point-and-click schematics, use human-readable `.ato` files that can be version controlled and shared. Capture design intelligence and validation rules in code to ensure your hardware works as intended.
+
+## Features
+
+- 🚀 Auto-select components like resistors and capacitors, based on their attribute's values
+- 🤖 Embed calculations in your code, which are checked on every build
+- 🧱 Build you circuit from reliable configurable modules so you can focus on high level design
+- 💥 Build, release and test your circuit board from the `CLI`
+- 📦 Embedded package manager to install and manage modules from https://packages.atopile.io, or Github
+- 🔍 Version control line-by-line diffable code w/ git
+
+Jump right in with the [quickstart guide](quickstart.md)
+
+## Who's atopile for?
+
+Currently atopile is young - which means we can't do everything yet and we're focussed on being incredible at a few things:
+
+### Custom Validation Equipment
+
+> "Rome wasn't built in a day, but your HiL should be"
+
+If you're serious about automating the validation of your production hardware, you're in the right place.
+
+[Cell-sim](https://github.com/atopile/cell-sim/) is a 16ch, 16-bit, isolated, 0-5V, 0-500mA battery-cell simulator designed from scratch in atopile, from concept to 2-revisions in under 5 days work. Oh, and that time includes the firmware. It is a relatively complex HiL design, and required many new modules that didn't yet exist on our package manager. Simpler HiL designs are frequently just a day's work.
+
+![cell-sim](assets/images/cell-sim.png)
+
+### Young companies who need to iterate on hardware
+
+`atopile` designed hardware is in satellites, humanoid robots and VTOL drones - all from startups within the last year.
+
+Not every young company NEEDs to iterate on it's hardware, but many more should than do.
+
+We're used to this in the software world, but getting the same engine running at even remotely similar speeds for hardware is a huge challenge. `atopile` let's multiple people work on different features or concepts on the same project in parallel via branches in `git`. With calculations checked and tests run automatically on every change, you can iterate as an individual - quickly trying out new ideas before committing to a design as a team and only after validating it in the real-world.
+
+### Huge nerds 🤓
+
+Welcome the club!
+
+If you like making dope stuff, like these [servo drives](https://github.com/atopile/spin-servo-drive) you're in the right place. Welcome!
+
+![spin-showing-off-the-very-goods](assets/images/spin-showing-off-the-very-goods.jpg)
+
+## Roadmap
+
+### Up-next
+
+- [ ] 📦 [Package Manager](https://github.com/atopile/atopile/discussions/495) - Make finding, installing and publishing modules fast and easy
+- [ ] First-party packages for HiL systems
+
+### Soon
+
+- [ ] Language Server - A standard LSP server for atopile
+- [ ] Plugin system - Make it easy to extend the `ato` CLI
+
+### Non-goals
+
+- Integration with XXX design tool. Reliably supporting all the features of legacy EDA tools is a huge lift, and, with rapid continued improvement in the open-source EDA space, it's not currently the best use of our time.

{atopile-0.3.7.dev0 → atopile-0.3.9.dev0}/docs/overrides/home.html

@@ -17,7 +17,7 @@
           <a href="{{ page.next_page.url | url }}" title="{{ page.next_page.title | e }}" class="md-button md-button--primary">
             Quick start
           </a>
-          <a href="mailto:tim@atopile.io,matt@atopile.io,narayan@atopile.io" title="Email us" class="md-button">
+          <a href="mailto:founders@atopile.io" title="Email us" class="md-button">
             Contact us
           </a>
         </div>

{atopile-0.3.7.dev0 → atopile-0.3.9.dev0}/docs/overrides/main.html

@@ -1,7 +1,12 @@
-{#-
-  This file was automatically generated - do not edit
--#}
 {% extends "base.html" %}
+
+{% block outdated %}
+  You're not viewing the latest version.
+  <a href="{{ '../' ~ base_url }}">
+    <strong>Click here to go to latest.</strong>
+  </a>
+{% endblock %}
+
 {% block announce %}
   For updates, star us on
   <a href="https://github.com/atopile/atopile">
@@ -23,6 +28,7 @@
       {% include ".icons/fontawesome/brands/youtube.svg" %}
     </span>
     <strong>YouTube</strong>
+  </a>
   , or join us on
   <a href="https://discord.gg/nkpC7wYRVw">
     <span class="twemoji discord">
@@ -31,9 +37,11 @@
     <strong>Discord</strong>
   </a>
 {% endblock %}
+
 {% block extrahead %}
   <link rel="stylesheet" href="{{ 'assets/stylesheets/custom.css' | url }}">
 {% endblock %}
+
 {% block scripts %}
   {{ super() }}
   <script src="{{ 'assets/javascripts/custom.129bd6ad.min.js' | url }}"></script>