From 859c0b1bf2fdc4379ca2823afeb67f2c14aa21fa Mon Sep 17 00:00:00 2001 From: Joshua Lau Date: Wed, 9 Oct 2024 19:01:29 -0400 Subject: [PATCH] Update README --- README.md | 2 +- astro.config.mjs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c48f0a4..ac2e4dc 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,6 @@ If you're interested in building a Tiger App or joining the TigerApps team, chec If you've never worked with Astro before, it's essentially like HTML with a bit of JSX sprinkled in. Compared to pure HTML, it makes it easy to have modularity, accessibility, and SEO. -When updating data (apps, members, companies, etc.), be sure to decouple the data from the HTML/Astro markup. For example, MEMBERS (in [index.astro](./src/pages/index.astro)) holds the data for current members that will be rendered by the Astro markup. Global CSS styles should be used sparingly; TailwindCSS is preferred. However, you can place global CSS in [Layout.astro](./src/layouts/Layout.astro). +When updating data (apps, members, companies, etc.), be sure to decouple the data from the HTML/Astro markup. For example, the currentMembers variable (in [Members.astro](./src/components/landing/Members.astro)) holds the data for current members that will be rendered by the Astro markup. Global CSS styles should be used when preserving style across multiple elements, but Tailwind is preferred. You can place global CSS in [Layout.astro](./src/layouts/Layout.astro). Run `npm run format` to format code according to the [Prettier settings](./.prettierrc). diff --git a/astro.config.mjs b/astro.config.mjs index aa800e7..18be6a5 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -5,5 +5,5 @@ import tailwind from "@astrojs/tailwind"; // https://astro.build/config export default defineConfig({ integrations: [tailwind()], - site: "https://tigerapps.org", + site: "https://tigerapps.org" });