From 6711797f99e420f7d8ededce48142a304d791c8f Mon Sep 17 00:00:00 2001 From: Youwen Wu Date: Sun, 11 Feb 2024 02:08:55 -0800 Subject: [PATCH] fix broken image --- README.md | 2 +- src/app/layout.tsx | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d3aac7d..7bf0d04 100644 --- a/README.md +++ b/README.md @@ -26,4 +26,4 @@ The dummies guide to maintaining a Next.js project: - Try to use CSS modules for your components. You can access them from your modules by importing them (`import styles from './path-to-css-module` and using them in your components with `className={styles.class_name}`). This will allow you to use the same class names in different parts of the website without any conflicts, as Post CSS will generate unique classes from the CSS modules. - Important: THIS IS NOT JAVASCRIPT! You CANNOT use global variables, window variables, etc, or even stateful variables that are meant to persist beyond a single refresh cycle (which can happen many times per second). Use the STATE for this (see [the module we are using for state management](https://github.com/pmndrs/zustand)) - Try to define modules for your components instead of putting everything in one file to avoid JANK -- You should put all static assets like images, icons, sound bytes, etc, in the `public` folder. These assets will be made available at the root directory `/`. For example, if `eecs-wordmark.png` is in `public`, then I can access it from an image element like so: ``. diff --git a/src/app/layout.tsx b/src/app/layout.tsx index 35079ef..33680c6 100644 --- a/src/app/layout.tsx +++ b/src/app/layout.tsx @@ -31,7 +31,10 @@ export default function RootLayout({
- +