Lesson Description
The "Wrapping Up" Lesson is part of the full, Build a Fullstack Next.js App, v4 course featured in this preview video. Here's what you'd learn in this lesson:
Brian wraps up the course by highlighting ways to extend and practice what was learned, suggesting features like search, pagination, collaborative editing, AI assistants, analytics, and improved CI/CD workflows. He emphasizes forming opinions on different technologies, making trade-offs, and experimenting with alternative stacks to deepen understanding and developer experience.
Transcript from the "Wrapping Up" Lesson
[00:00:00]
>> Brian Holt: this is the end. There's no more code. We did all the Next.js things. One thing I like to put at the end of these courses is like, what could you do if you wanted to go kind of extend and do more and practice more here. So I just wrote down a bunch of ideas, feel free to use these, not use these, but I think practice is always good here. We didn't do anything with search. So like if you wanted to be able to search wikis, we didn't paginate as well either.
[00:00:26]
So adding pagination probably number one, and then adding full text search. Neon has that built in with pg_search, so you could use that. Or you could use Algolia or TypeSense or something like that. A tag category system related articles would be really cool, using like vector search with pgvector, which is also available on Neon. Collaboration, you could do something like Commento or build like your own using the database of like a commenting system, revision histories, so you could kind of store that into some sort of like analytical pool where you can pull that back out.
[00:01:02]
Collaborative editing with PartyKit, which is a very cool piece of software if you haven't ever used PartyKit before. Article templates, AI writing assistant, that seemed like it could be fun to do. Do some sort of like a table of contents using like the AI to generate like the contents table. We have it so you can only upload one image at a time, make it so that there's a one-to-many relationship there, so you can have multiple images, you can have like a primary image and secondary images.
[00:01:34]
Being able to pull out of a PDF, Open Graph would be cool as well, if you wanted to do like for sharing. Mentions, real time notifications, digest emails, Slack or Discord integrations. We already did an email, you might do Twilio for text notifications. More analytics would be cool. Doing some things like published versus non-published, we also have the slug in there as opposed to using the ID. Having a slug would be better SEO, as well as like a better looking URL.
[00:02:12]
Spell check templates. We could do something like, let's say you have like one article that's really popular right now, everything's kind of more dynamic, but you could actually like render them to flat files and then cache that. We talked about doing this from like a Cloudflare worker at the edge, right, where you could actually load these things into like, hey, put my most popular articles into the edge so that the user is just hitting the edge as opposed to doing all the way to my app server.
[00:02:35]
Read replicas, they're pretty easy to set up with Neon, just say like I have this database, give me a read replica, and only hit the write primary from the actions and everything else comes from the read replicas. Infinite scroll pagination. Webhooks would be cool. You can make a CLI for like bulk importing. Download as a PDF. Everyone likes dark mode, you could do dark mode, keyboard shortcuts, voice to text.
[00:03:10]
Code quality, obviously this could be better tests. Storybook, I thought about doing this that we could like show you all the components that we've written. Storybook is really cool for like creating a design system. Better error handling, loading skeletons, we could do way better with like the loading states. Have it not be shadcn and make your own, kind of more design feel to it. Yeah, proper logging would be better, feature flags, A/B testing, going to dev staging and prod if you wanted to get more into like the GitHub action side of things.
[00:03:45]
Canary deployments where like you deploy one app server that's this particular like new service and then like roll it out slowly if it's like works okay. 2FA, CSP, rate limiting audit logs, if you really like HIPAA compliance, I got a job for you. More integrations. Auto generate more summaries, semantic search, content moderation, OpenAI has some like moderation APIs that are kind of interesting.
[00:04:23]
Recommendations would be cool. Go set up more sophisticated monitoring with something like Datadog or New Relic, I think they both have some free tier free trial to try out with. Better error tracking with Sentry or TrackJS, it's another great Frontend Masters teacher's, Todd. Uptime with Pingdom and a status page, as we looked at today for Vercel. So, hopefully one of those is like, oh, that sounds like fun.
[00:04:55]
I could do something like that. I try to cover like the entire swath of things that we covered here. That could be fun. But you did it. You made it through the Next.js course. Hope you learned something here, if nothing else, of Brian's deep love for Postgres. I hope you're not necessarily attached to like Vercel and Neon Upstash. Like that was never the point of this to be like an advertisement for any one of these services.
[00:05:22]
Vercel didn't pay me enough to do that, which is to say they didn't pay me. But I wanted to take an opinionated stab at this, so that like we went really deep into some of these technologies and I hope you got into some of these like, I like this, I don't like this, this was a pain, this was nice. Just taking a swing at these and like gaining opinion is like one of the most valuable things you can do, because when you go to like build your own thing next, you'll know that like, I liked Upstash, I did not like Vercel blob storage or whatever, you know, just whatever that ends up being.
[00:05:59]
Make trade-offs, right? Like at the end of this, I'm hoping that you learned enough to make tradeoffs in your head of like, I'm, you know, giving more in latency so I can get better developer experience or vice versa. Yeah, I hope this didn't read like an ad that I was really trying hard not to, and it's hard because like I really like these services, particularly Neon, like where I'm kind of passionate about it.
[00:06:23]
But I hope you examine things on their own merit, not just because I talked too much about it. Yeah, it was meant to be more of just like, let's take an opinion, let's have a specific stack, let's go deep, see what happens. And then, like a really good next step here would just be go try this with like the Cloudflare stack. Use like R2 and like they have stuff that's kind of like blob storage and database and workers and all that kind of stuff.
[00:06:51]
And it would be a wildly different experience. Better in some ways, worse than others. And yeah, and see what you like better. In any case, this was super fun. Thank you all for coming, for listening. It's like, please share back with me what you build, like I'm always interested in these kind of things. It's what makes this community fun is like they're pretty open and sharing about it. And I will catch you on the next Frontend Masters whenever they let me back on.
Learn Straight from the Experts Who Shape the Modern Web
- 250+In-depth Courses
- Industry Leading Experts
- 24Learning Paths
- Live Interactive Workshops