3 devlogs
9h 7m 45s
a study tool
devlog before getting ahead of myself lol. okay in this session I have FINALLY finished all of the auth pages and finished choosing my ui components. We replaced the username -> name, to better suite the project and we also made everything taller and a lotta improvments on ux. This includes, instead of getting errors from frontend where we don’t know a lot we just query them from the backend, so minimizes getting errors from 2 places. then we put this inside of an alert component instead of throwing it out (Lessgooo), also migrated from self-hosted pg to neon pg, cause i couldn’t get coolify to work. added a BUNCH of needed logging on the go side and had to learn how to log + push to http so the frontend could see it. now it looks a LOT better. finished the signin page + plans?? to add otp signin (im tryna do this all myself instead of using a library to learn) and make the social signin buttons actually work. also added posthog for error tracking, actually i did sentry first, fully set that up and then realized i liked posthog better as a company and switched over, luckily ph (posthog) has this really cool ai cli which did everything for me so yay!. oh had some hydration issues with the nextjs on the auth pages, fixed it with stable id’s. it also took me a LONG time to understand how this STUPID monorepo has to work, and the ui now uses coss-ui which is built by cal.com so yay! also optimized a bunch of stuff on the frontend by uses the next/ packages for stuff like links and images. now ima go work on the HOMEPAGE!!!!
0
Log in to leave a comment
Okay, these hours i’ve done a lot of researching and trying out different things. So first for the ui I went with a svelte frontend with a go frontend, pros -> insanely fast, con-> it doesn’t have as big of a ecosystem as something that uses react, so I switched over. Then I turned my sight to UI. I already knew that I was going to go with a component library but I chose between HeroUI or ShadcnUI. HeroUI came out looking unique and fresh out of the box, but I wanted to control styling and actually look at the source code so I ended up choosing ShadcnUI. After that there were two things I could do. I could separate the frontend and the backend or I could use a monorepo application like Turborepo to combine them. I tried both out and I seemed to like the monorepo feeling a bit more. It did increase complexity and did take a loooong time to understand but the changes to efficiency that they promised were nice so I stuck to that. After that I designed a heck ton on figma. Going between a neo-brutalist design system, to something a little more flat and modern. After considering where I wanted the app to go I chose the flat design and with the Shadcn components I could easily switch courses. I also experimented with the Shadcn Create project thingy, which was super cool. I ended up choosing the Maia style (still can’t pronounce this lmao). Then I wired up the frontend to our go backend, I did think of doing something like a proxy, basically I would route the frontend to the Nextjs api routes and then route those to the backend, benefit being CORS (well not MOSTLY) but also the ecosystem advantage. I also integrated storybookJS, I really wanted to treat this project as something BIG, so (following the posthog repo) I painstakingly added all the componets to storybook. Anyway I’ll drop the screenshots and cya in the next devlog where i’ll be trying to wire up the dashboard :). IGNORE THE BLATANT FIZZY COPYING (I REALLY LIKED THE UI). THE ONE AT THE END IS MY INSPO.
0
Log in to leave a comment
I started the project off by using Svelte for the frontend and Go for the backend and developing backend auth in go. Since I’m quite new, it took a little while to get the hang of it and I had to use a lot of google but now I have a working auth backend in go using JWT tokens! I also imported a login page from shadcn and next i’ll try to wire the backend and frontend together
0
Log in to leave a comment