Source code
Developer tier exports are standalone Next.js apps generated from the selected BuildFolyo template.
The Developer tier lets you download the selected template as a standalone Next.js project. This export is template-specific. It is not the full BuildFolyo SaaS codebase.
What you get
A self-contained Next.js app for the chosen template, plus the local components that template depends on.
What you do not get
BuildFolyo auth, billing, analytics, database code, and server actions are removed from the export.
Where the download lives
Developer downloads are exposed from the template gallery. Open a template, then use Download Source from the preview modal.
The download option is only unlocked for signed-in Developer accounts. Community and Pro accounts see the same entry point, but it stays locked behind the Developer tier.
What is inside the zip
Every export is assembled as a standalone app. The exact component tree varies by template, but the project shape follows this pattern:
your-template/
app/
globals.css
layout.tsx
page.tsx
components/
templates/
SelectedTemplate.tsx
...
data/
portfolio.json
.gitignore
next-env.d.ts
next.config.ts
package.json
postcss.config.mjs
README.md
tailwind.config.ts
tsconfig.json
Key files
`app/page.tsx`
Renders your selected template against local JSON data. There is no BuildFolyo account dependency in the export.
`data/portfolio.json`
Holds placeholder portfolio content that you replace with your own profile, projects, links, education, and experience.
`components/`
Includes the selected template and any shared local components that template imports.
Project config
Includes the minimal Next.js, TypeScript, Tailwind, and PostCSS config needed to run the export.
What the export intentionally strips out
The export script removes platform-specific dependencies before packaging the zip.
These BuildFolyo systems are not part of the standalone export:
- Clerk authentication
- MongoDB and Mongoose access
- BuildFolyo server actions
- Cashfree billing
- PostHog providers and platform analytics wiring
That is why the exported app is portable. You get the front end and its local dependencies, not the hosted platform behind it.
What the runtime looks like
The generated package.json is intentionally small. It includes the dependencies the templates need to render, such as next, react, react-dom, framer-motion, lucide-react, clsx, and tailwind-merge.
More interactive templates usually ship with a larger supporting component tree because the export recursively copies local imports used by that template.