Skip to content
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.

ideas42ventures/eleventy-ideas42ventures.com

Repository files navigation

The ideas42 Venture Studio website.

Analytics

We do not use Google Analytics because we respect the privacy of people that visit our websites.

We still want to track how our site is being used, so instead, we use the privacy-focused Fathom.

  • The main Fathom account is under tyler@ideas42ventures.com
  • The analytics dashboard is available–password protected–at https://app.usefathom.com/share/jggxgdmd/ideas42ventures.com Ping Tyler in Slack or email for the password.
  • We track custom Goals. That's Fathom's term for custom events. There is JS set up to track goals for any a element that includes a data-fathom-goal attribute. Example; <a data-fathom-goal="1234" href="/">Link</a>. Goals must be set up in the Fathom dashboard, that's where the goal ids come from. Again, for now, ping Tyler in Slack or email if you need to track a goal.

Email subscription form

We use Mailchimp to handle the form submission.

Contributing

Requirements

  • node.js: LTS version recommended
  • yarn: Latest version recommended

Local setup

Clone the repo

git clone git@github.com:ideas42ventures/ideas42ventures.com.git
cd ideas42ventures.com

Install dependencies

yarn

Start the dev server and watcher

yarn start

The site will be available at http://localhost:8080/.

Build without dev server or watcher

When you need to do a new build without starting the dev server or file watchers run:

yarn build

Deploying

To Production

We host this site on Netlify. Anything merged into the main branch is deployed to production.

To Staging

We use Netlify preview builds. To see any branch in a live environment, push the branch to the remote and open a pull request.

Code formatting

We format all JavaScript, CSS, and HTML with Prettier. We use the lint-staged with husky approach to make sure formatting happens for all contributors.

A note about inline styles

For production builds, we put all CSS in the head of each page. This helps avoid layout shift during page load.

During dev builds–with yarn start–all CSS is compiled to an external site.css. We include that file with a link element in the head.