2. Create your personal page

[edakturk14]

Goal

Create a PR with your personal page so it's displayed on the Batch site.

Creating the Batch page

1. If you haven't done it already: fork & clone the repo, install dependencies, and create your own branch.
2. Create a new folder & file in packages/nextjs/app/builders/[your-0xAddress]/page.tsx
3. You can have a little bio, avatar, address, links to your socials, etc.
   -> Keep it simple! (no heavy assets, etc.)

⚠️ Important Notes:

• Pay special attention to linting, code format, etc.
• Be creative! Don't just copy what other builders and doing.
• Inspecting how other SE-2 components/pages are created is a great way to learn.
• Make sure to read the README file for more guidance.

⚠️ If you are the first one to create your personal page, you'll need to create the builders folder in packages/nextjs/app/.

[fedeloterstein]

Completed in this PR ✨

[arjanjohan]

Check out my personal page here #17

[danitome24]

Hi all!

For this issue, the task is to create only your page (page.tsx). However, you need to remember your address to reach the url (domain:3000/builders/[address]).

I suggest modifying app/component/Header.tsx to add a dropdown where everyone can map their name => address, making it easier to navigate to individual pages

Maybe something like:

What do you think about it?

Perhaps modifying Header.tsx code should be a new issue...

[arjanjohan]

@danitome24 Check out issue #4 where two solutions for this are proposed. I personally like the /builders page approach that is suggested there. In a drop-down, it might be difficult to distinguish students, especially those without an ENS name. On a dedicated page, we can add more information (like profile pictures).

On the other hand, I never created a dropdown in the scaffold header, so I am keen to trying to build it (although it should not be that difficult). For learning purposes, I suggest implementing both solutions.

[derrekcoleman]

I appreciate your suggestion, @danitome24! As Arjan pointed out, this problem is exactly the scope for #4.

I encourage you to open an issue for any other design ideas you have! This collaborative discussion is at the heart of OSS development.