You are browsing as a guest. Sign up (or log in) to start making projects!

LaunchPad

  • 5 Devlogs
  • 7 Total hours

LaunchPad is a quality-of-life web app that helps makers organize their projects and quickly generate submission materials like README templates, devlogs, checklists, GitHub descriptions, and AI usage statements.

Ship #1

I built LaunchPad, a quality-of-life web app that helps makers organize their projects and generate useful submission materials faster. The app lets users create a local profile, save project information, add links such as GitHub and demo URLs, select the type of project, and choose which resources they want to generate. From one saved project, LaunchPad can generate materials like a README template, a GitHub description, a DevLog, a submission checklist, an AI usage statement, and a project submission text. Users can also copy or download the generated resources directly from the project page.

The most challenging part was connecting the whole front-end flow in a clean way. I had to work with React Router protected routes, localStorage persistence, form actions, dynamic project pages, and reusable generator functions. Another challenge was making the app feel simple and useful instead of overloaded, because the main goal was to remove friction from a repetitive workflow.

I am most proud of being able to apply the front-end knowledge I have been studying recently and turn it into a complete, working project with a satisfying final result. This project helped me practice React, Vite, TailwindCSS, routing, local data storage, and UI organization in a real use case. I am also proud that the tool solves a problem I personally have when submitting projects: rewriting the same information across README files, devlogs, descriptions, and checklists.

To test the project, open the live demo, create a simple local login, and then create a new project. Add a project name, description, type, technologies, GitHub link, demo link, challenges, and what you learned. After saving it, open the project from the dashboard and try generating, copying, and downloading the selected resources. All data is stored locally in the browser using localStorage, so no real account or backend is required.

Try project → See source code →
Open comments for this post

1h 32m 57s logged

This update focused on the project detail flow. I created a dedicated page for each project, updated the routes so users can open a project directly from the dashboard, and added an “Open project” action to the project cards. I also polished the styling of the project page to keep the new flow consistent with the rest of the app.

I made a few small improvements to the generators utility too, so it can handle project data more reliably when building formatted files like README, DevLog, checklist, and submission text.

This update focused on the project detail flow. I created a dedicated page for each project, updated the routes so users can open a project directly from the dashboard, and added an “Open project” action to the project cards. I also polished the styling of the project page to keep the new flow consistent with the rest of the app.

I made a few small improvements to the generators utility too, so it can handle project data more reliably when building formatted files like README, DevLog, checklist, and submission text.

Replying to @Manenti

0
2
Open comments for this post

1h 16m 30s logged

Since the last devlog, I focused on the generators layer of the project. I created a utility that turns a project’s data into formatted output files, including README, GitHub description, DevLog, checklist, AI usage statement, and submission text.

I also added filename generation for each resource so the exported content is organized and easy to reuse. This gave the app its first real content-generation workflow instead of just storing project information.

Since the last devlog, I focused on the generators layer of the project. I created a utility that turns a project’s data into formatted output files, including README, GitHub description, DevLog, checklist, AI usage statement, and submission text.

I also added filename generation for each resource so the exported content is organized and easy to reuse. This gave the app its first real content-generation workflow instead of just storing project information.

Replying to @Manenti

0
2
Open comments for this post

2h 51m 37s logged

Since the last devlog, I moved the project from a basic routed app into a more complete project-management flow. I set up a lightweight MVC structure for projects, added localStorage-backed project persistence, and refactored shared UI into reusable components like Button and InputField. I also started importing a custom font to make the interface feel less generic.

On the product side, I built the create-project screen with fields for project metadata, links, technologies, challenges, learnings, and generator selection, plus validation and save/cancel actions. I then expanded the dashboard into a real project overview that reads saved projects, handles the empty state, greets the logged-in user, and links into the new project flow. After that, I polished the styling of both the dashboard and the new project page so the app feels more consistent and usable

Since the last devlog, I moved the project from a basic routed app into a more complete project-management flow. I set up a lightweight MVC structure for projects, added localStorage-backed project persistence, and refactored shared UI into reusable components like Button and InputField. I also started importing a custom font to make the interface feel less generic.

On the product side, I built the create-project screen with fields for project metadata, links, technologies, challenges, learnings, and generator selection, plus validation and save/cancel actions. I then expanded the dashboard into a real project overview that reads saved projects, handles the empty state, greets the logged-in user, and links into the new project flow. After that, I polished the styling of both the dashboard and the new project page so the app feels more consistent and usable

Replying to @Manenti

0
1
Open comments for this post

39m 36s logged

Since the last update, I moved the project from a simple login prototype into a small routed app with actual navigation flow. I installed React Router, created public and protected routes, and wired the login so it now sends the user to the dashboard after saving their data locally.

I also built a first provisional dashboard with a greeting, logout action, and a placeholder projects section. After that, I refined the dashboard styling and started polishing the overall presentation by importing a font and improving the visual structure.

Since the last update, I moved the project from a simple login prototype into a small routed app with actual navigation flow. I installed React Router, created public and protected routes, and wired the login so it now sends the user to the dashboard after saving their data locally.

I also built a first provisional dashboard with a greeting, logout action, and a placeholder projects section. After that, I refined the dashboard styling and started polishing the overall presentation by importing a font and improving the visual structure.

Replying to @Manenti

0
4
Open comments for this post

49m 44s logged

I started the project with Vite and React and installed Tailwind CSS to speed up the interface. I structured the application to display a login screen as the app’s entry point. I created the basis of the authentication flow with simple name and email validation. I added local persistence with localStorage to save user data in this prototype. I adjusted the form fields and then refined the page’s appearance with a more polished and responsive layout.

I started the project with Vite and React and installed Tailwind CSS to speed up the interface. I structured the application to display a login screen as the app’s entry point. I created the basis of the authentication flow with simple name and email validation. I added local persistence with localStorage to save user data in this prototype. I adjusted the form fields and then refined the page’s appearance with a more polished and responsive layout.

Replying to @Manenti

0
1

Followers

Loading…