Configuration

This template comes pre-configured with the author’s information. To personalize it for your own use, you’ll need to replace these details with your own information.

Here are the configurable elements:

src/data/site.tsx: This file holds your site’s core information and configuration.
src/i18n/messages: This directory contains the language files, enabling multilingual support.
- common.json: Stores common interface messages. Here, you can update the navigation bar and footer items.
- personal.json: Stores personal details. You can change your name, subtitle, description, and summary here.
- collections.json: Contains information about your main collections—such as projects, news, publications, invited talks, teaching experiences, and awards.
content directory: This folder houses your blog post markdown files. Refer to Blog for more guidance.
favicon: Update your site’s favicon by replacing favicon.ico, apple-icon.png, and icon.png. See Favicon for details.
domain: Configure your website’s custom domain. For instructions, check Deployment.

Delete a Section

To remove a section from your portfolio, you have two options:

In collections.json, simply set the items array for that section to be empty (do not delete the section key itself).


"news": {
    "items": []
}

If the section still appears, manually remove or comment out the relevant section in the src/app/[locale]/page.tsx file.

Modify Anything

If you want to modify anything else, you can do so by modifying the corresponding file in the src directory. For example, if you want to modify some texts of the portfolio, you can modify in the src/app/[locale]/page.tsx file.

Error Handling

While I have not extensively tested all scenarios, there may be cases when certain information is removed (e.g., Google Scholar link, Calendly link, etc.) that could cause issues. If you encounter any problems, don’t worry - there are two simple solutions:

Ask an AI assistant (e.g., Cursor) to help resolve the issue by requesting: “Please fix the issue in the code.”
Check the error details shown in your browser’s Next.js development console, locate the problematic file, and remove or modify the relevant code section.

Feel free to open an issue if you encounter any problems.