Rename opendata.studio -> opendatakit and update logo

open-datakit · Oct 24, 2024 · 93a10b3 · 93a10b3
1 parent 6919a48
commit 93a10b3
Show file tree

Hide file tree

Showing 12 changed files with 5,902 additions and 3,917 deletions.
diff --git a/.gitignore b/.gitignore
@@ -1,10 +1,54 @@
-.DS_Store
-
-# generated types
+# Generated types
 .astro
 
-dist/
-
+# direnv
 /.direnv/
 
+# https://yarnpkg.com/getting-started/qa#which-files-should-be-gitignored
+.yarn/*
+!.yarn/cache
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/sdks
+!.yarn/versions
+
 node_modules
+yarn-error.log
+
+.DS_Store
+.history
+
+junit.xml
+
+# This file is generated by the Smart Merge workflow
+/merge-conflict-resolution.patch
+
+# The tarballs generated by "yarn pack" are never kept either
+package.tgz
+
+# The artifacts generated by "yarn release:all" are never kept
+/artifacts
+/dist
+
+# Our documentation is now handled by Netlify
+/docs
+
+# Those files are meant to be local-only
+/packages/*/bundles
+
+# Those folders are meant to contain the prepack build artifacts; we don't commit them
+/packages/*/lib/*
+
+# Those packages are built inline and the artifacts must not be checked-in
+/packages/yarnpkg-libui/sources/**/*.js
+/packages/yarnpkg-libui/sources/**/*.d.ts
+
+# Used by /scripts/stable-versions-store.js
+/scripts/stable-versions-store.json
+
+/vscode-case-study
+
+.idea
+
+coverage
diff --git a/.yarnrc.yml b/.yarnrc.yml
@@ -0,0 +1 @@
+nodeLinker: node-modules
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-# opendata.studio website
+# opendatakit website
 
 ## Development
 

diff --git a/astro.config.mjs b/astro.config.mjs
@@ -5,6 +5,6 @@ import sitemap from "@astrojs/sitemap";
 
 // https://astro.build/config
 export default defineConfig({
-  site: "https://opendata.studio",
+  site: "https://opendatakit.io",
   integrations: [mdx(), sitemap()],
 });
diff --git a/package.json b/package.json
@@ -1,5 +1,5 @@
 {
-  "name": "opendata.studio",
+  "name": "opendatakit-website",
   "type": "module",
   "version": "0.0.1",
   "scripts": {

diff --git a/public/assets/images/logos/opendatakit.svg b/public/assets/images/logos/opendatakit.svg
diff --git a/public/assets/images/logos/opendatastudio.svg b/public/assets/images/logos/opendatastudio.svg
diff --git a/src/components/Header.astro b/src/components/Header.astro
@@ -53,15 +53,15 @@ import { SITE_TITLE } from "../consts";
   <div class="branding">
     <a href="/" title="Home">
       <img
-        class="opendatastudio-logo"
-        src="/assets/images/logos/opendatastudio.svg"
+        class="opendatakit-logo"
+        src="/assets/images/logos/opendatakit.svg"
       />
     </a>
   </div>
   <nav>
     <div class="internal-links">
       <HeaderLink href="/">Home</HeaderLink>
-      <HeaderLink href="https://docs.opendata.studio">Documentation</HeaderLink>
+      <HeaderLink href="https://docs.opendatakit.io">Documentation</HeaderLink>
       <HeaderLink href="/team">Team</HeaderLink>
     </div>
   </nav>

diff --git a/src/consts.ts b/src/consts.ts
@@ -1,2 +1,2 @@
-export const SITE_TITLE = "opendata.studio";
+export const SITE_TITLE = "opendatakit";
 export const SITE_DESCRIPTION = "Reproducible data publication for the web";
diff --git a/src/pages/index.astro b/src/pages/index.astro
@@ -83,7 +83,7 @@ var title = `${SITE_TITLE}`;
       }
     }
 
-    .opendatastudio-branding {
+    .opendatakit-branding {
       display: flex;
       align-items: center;
       margin: 1em 0;
@@ -99,9 +99,15 @@ var title = `${SITE_TITLE}`;
         font-variant: discretionary-ligatures;
         font-variation-settings:
           "opsz" 32,
-          "wght" 490;
+          "wght" 350;
         font-size: 3em;
         color: #212d49;
+
+        .title-branding-bold {
+          font-variation-settings:
+            "opsz" 32,
+            "wght" 580;
+        }
       }
     }
 
@@ -115,7 +121,7 @@ var title = `${SITE_TITLE}`;
     }
 
     @media (max-width: 445px) {
-      .opendatastudio-branding {
+      .opendatakit-branding {
         font-size: 0.8em;
         margin: 0;
         margin-bottom: 1em;
@@ -134,7 +140,7 @@ var title = `${SITE_TITLE}`;
     <link href="/assets/fonts/FontAwesome/css/all.css" rel="stylesheet" />
   </head>
 
-  <body class="opendatastudio">
+  <body class="opendatakit">
     <div class="layout-container">
       <div class="site-header-background"></div>
       <div class="site-header">
@@ -143,20 +149,22 @@ var title = `${SITE_TITLE}`;
 
       <main>
         <section class="introduction">
-          <div class="opendatastudio-branding">
+          <div class="opendatakit-branding">
             <img
-              class="opendatastudio-logo"
-              src="/assets/images/logos/opendatastudio.svg"
+              class="opendatakit-logo"
+              src="/assets/images/logos/opendatakit.svg"
             />
-            <h1 class="title-branding">opendata.studio</h1>
+            <h1 class="title-branding">
+              open<span class="title-branding-bold">datakit</span>
+            </h1>
           </div>
           <span class="title-byline">
             Reproducible data publication for the web
           </span>
 
           <div class="intro-box">
             <p>
-              opendata.studio is a software toolbox that makes publishing
+              opendatakit is a software toolbox that makes publishing
               reproducible data workflows simple.
             </p>
             <p>
@@ -167,21 +175,21 @@ var title = `${SITE_TITLE}`;
               > specification.
             </p>
             <p>
-              opendata.studio packages can be published as interactive web
+              opendatakit packages can be published as interactive web
               applications, or embedded as individual components in other web
               pages, making it simple to share data while maintaining
               reproducibility and provenance.
             </p>
           </div>
 
           <div class="link-tiles">
-            <a href="https://docs.opendata.studio">
+            <a href="https://docs.opendatakit">
               <h2>Documentation&nbsp;→</h2>
-              <p>Get started with opendata.studio</p>
+              <p>Get started with opendatakit</p>
             </a>
             <a href="/team">
               <h2>Team&nbsp;→</h2>
-              <p>The opendata.studio team</p>
+              <p>The opendatakit team</p>
             </a>
           </div>
         </section>

diff --git a/src/pages/team.astro b/src/pages/team.astro
@@ -71,7 +71,7 @@ var title = `${SITE_TITLE}`;
     <BaseHead title={title} description={SITE_DESCRIPTION} />
     <link href="/assets/fonts/FontAwesome/css/all.css" rel="stylesheet" />
   </head>
-  <body class="opendatastudio">
+  <body class="opendatakit">
     <div class="layout-container">
       <div class="site-header-background"></div>
       <div class="site-header">
@@ -95,10 +95,10 @@ var title = `${SITE_TITLE}`;
               and systems chemistry.
             </p>
             <p>
-              Pall is the progenitor of the opendata.studio project, starting
-              from its original incarnation as supramolecular.org. Pall is
-              passionate about facilitating tooling for open science and
-              encouraging reproducibility in data analysis.
+              Pall is the progenitor of the opendatakit project, starting from
+              its original incarnation as supramolecular.org. Pall is passionate
+              about facilitating tooling for open science and encouraging
+              reproducibility in data analysis.
             </p>
             <a href="https://www.unsw.edu.au/staff/pall-thordarson">
               UNSW profile</a
@@ -118,10 +118,10 @@ var title = `${SITE_TITLE}`;
             <span class="project-role">Software Architect</span>
             <p>
               Varvara is a solutions architect and implementation specialist for
-              the opendata.studio project with a background in astrophysics. She
-              is responsible for architecting and implementing the backend
-              services underpinning the opendata.studio ecosystem as well as
-              frontend implementation details.
+              the opendatakit project with a background in astrophysics. She is
+              responsible for architecting and implementing the backend services
+              underpinning the opendatakit ecosystem as well as frontend
+              implementation details.
             </p>
             <p>
               In her various roles she has worked extensively across the web
@@ -144,7 +144,7 @@ var title = `${SITE_TITLE}`;
           <div class="bio-copy">
             <span class="project-role">Software Architect</span>
             <p>
-              James is a solutions architect for the opendata.studio project. He
+              James is a solutions architect for the opendatakit project. He
               specialises in data specification design and is a passionate
               advocate for FAIR data management principles. He has extensive
               experience in web application architecture and frontend design.
@@ -166,11 +166,11 @@ var title = `${SITE_TITLE}`;
           <div class="bio-copy">
             <span class="project-role">Cloud Infrastructure Specialist</span>
             <p>
-              Thomas is the cloud infrastructure specialist for opendata.studio.
-              He has extensive experience with AWS and Google Cloud
-              infrastructure deployments and holds certifications in both. He
-              specialises in Infrastructure as Code deployments with Terraform,
-              ensuring reproducible and resilient deployments.
+              Thomas is the cloud infrastructure specialist for opendatakit. He
+              has extensive experience with AWS and Google Cloud infrastructure
+              deployments and holds certifications in both. He specialises in
+              Infrastructure as Code deployments with Terraform, ensuring
+              reproducible and resilient deployments.
             </p>
             <a href="https://www.linkedin.com/in/thomas-wilmot/">LinkedIn</a>
           </div>