The Presentation Foundation

Online Presentation Data Management Cloud Platform for easy access and disribution of your presentations.
pr.djl.foundation »

About the Presentation Foundation

The Presentation Foundation is an initiative by the DJL Foundation, a nonprofit association based in Germany. Our mission is to make the management and distribution of presentation materials accessible, transparent, and community-driven. We believe that knowledge and educational resources should be easy to share, remix, and build upon—without unnecessary barriers or proprietary lock-in.

Our Goals

• Open Access: Enable anyone to host, access, and distribute presentations freely, supporting both private and public sharing.
• Simplicity: Provide a platform that is intuitive and easy to use, lowering the technical barrier for educators, students, and organizations.
• Transparency: Operate as an open-source project, inviting contributions and feedback from the community. All code is public, and development is guided by the needs of our users.
• Privacy and Control: Respect user privacy and give users control over their data and content. We do not monetize user data or restrict access through paywalls.
• Community Collaboration: Foster a collaborative environment where improvements, ideas, and new features are shaped by contributors from around the world.

Why Open Source?

We believe that open-source software empowers individuals and organizations to take ownership of their tools. By making our code and processes public, we encourage learning, transparency, and trust. Contributions are welcome from anyone who shares our vision for accessible, community-driven presentation management.

---

For more information about the DJL Foundation and our other projects, visit djl.foundation or parking.djl.foundation.

---

Welcome to your new TanStack Start app!

Getting Started

To run this application:

bun install
bun --bun run dev

Building For Production

To build this application for production:

bun --bun run build

Testing

This project uses Vitest for testing. You can run the tests with:

bun --bun run test

Styling

This project uses Tailwind CSS for styling.

Removing Tailwind CSS

If you prefer not to use Tailwind CSS:

1. Remove the demo pages in src/routes/demo/
2. Replace the Tailwind import in src/styles.css with your own styles
3. Remove tailwindcss() from the plugins array in vite.config.ts
4. Uninstall the packages: bun install @tailwindcss/vite tailwindcss -D

Linting & Formatting

This project uses Biome for linting and formatting. The following scripts are available:

bun --bun run lint
bun --bun run format
bun --bun run check

Deploy to Cloudflare Workers

This project uses the Cloudflare Vite plugin (configured in vite.config.ts) and wrangler.jsonc:

1. Install Wrangler: npm install -g wrangler
2. Authenticate: wrangler login
3. Deploy: npx wrangler deploy

For production env vars, run wrangler secret put MY_VAR for each secret listed in .env.example. Public (non-secret) vars go in wrangler.jsonc under vars.

KV, D1, R2, and Durable Object bindings are configured in wrangler.jsonc — see https://developers.cloudflare.com/workers/wrangler/configuration/.

Setting up WorkOS

• Set the VITE_WORKOS_CLIENT_ID in your .env.local.

Setting up Convex

• Set the VITE_CONVEX_URL and CONVEX_DEPLOYMENT environment variables in your .env.local. (Or run bunx --bun convex init to set them automatically.)
• Run bunx --bun convex dev to start the Convex server.

Paraglide i18n

This add-on wires up ParaglideJS for localized routing and message formatting.

• Messages live in project.inlang/messages.
• URLs are localized through the Paraglide Vite plugin and router rewrite hooks.
• Run the dev server or build to regenerate the src/paraglide outputs.

Shadcn

Add components using the latest version of Shadcn.

pnpm dlx shadcn@latest add button

T3Env

• You can use T3Env to add type safety to your environment variables.
• Add Environment variables to the src/env.mjs file.
• Use the environment variables in your code.

Usage

import { env } from "#/env";

console.log(env.VITE_APP_TITLE);

Setting up PostHog

1. Create a PostHog account at posthog.com
2. Get your Project API Key from Project Settings
3. Set VITE_POSTHOG_KEY in your .env.local

Optional Configuration

• VITE_POSTHOG_HOST - Set this if you're using PostHog Cloud EU (https://eu.i.posthog.com) or self-hosting

Routing

This project uses TanStack Router with file-based routing. Routes are managed as files in src/routes.

Adding A Route

To add a new route to your application just add a new file in the ./src/routes directory.

TanStack will automatically generate the content of the route file for you.

Now that you have two routes you can use a Link component to navigate between them.

Adding Links

To use SPA (Single Page Application) navigation you will need to import the Link component from @tanstack/react-router.

import { Link } from "@tanstack/react-router";

Then anywhere in your JSX you can use it like so:

<Link to="/about">About</Link>

This will create a link that will navigate to the /about route.

More information on the Link component can be found in the Link documentation.

Using A Layout

In the File Based Routing setup the layout is located in src/routes/__root.tsx. Anything you add to the root route will appear in all the routes. The route content will appear in the JSX where you render {children} in the shellComponent.

Here is an example layout that includes a header:

import { HeadContent, Scripts, createRootRoute } from '@tanstack/react-router'

export const Route = createRootRoute({
  head: () => ({
    meta: [
      { charSet: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { title: 'My App' },
    ],
  }),
  shellComponent: ({ children }) => (
    <html lang="en">
      <head>
        <HeadContent />
      </head>
      <body>
        <header>
          <nav>
            <Link to="/">Home</Link>
            <Link to="/about">About</Link>
          </nav>
        </header>
        {children}
        <Scripts />
      </body>
    </html>
  ),
})

More information on layouts can be found in the Layouts documentation.

Server Functions

TanStack Start provides server functions that allow you to write server-side code that seamlessly integrates with your client components.

import { createServerFn } from '@tanstack/react-start'

const getServerTime = createServerFn({
  method: 'GET',
}).handler(async () => {
  return new Date().toISOString()
})

// Use in a component
function MyComponent() {
  const [time, setTime] = useState('')
  
  useEffect(() => {
    getServerTime().then(setTime)
  }, [])
  
  return <div>Server time: {time}</div>
}

API Routes

You can create API routes by using the server property in your route definitions:

import { createFileRoute } from '@tanstack/react-router'
import { json } from '@tanstack/react-start'

export const Route = createFileRoute('/api/hello')({
  server: {
    handlers: {
      GET: () => json({ message: 'Hello, World!' }),
    },
  },
})

Data Fetching

There are multiple ways to fetch data in your application. You can use TanStack Query to fetch data from a server. But you can also use the loader functionality built into TanStack Router to load the data for a route before it's rendered.

For example:

import { createFileRoute } from '@tanstack/react-router'

export const Route = createFileRoute('/people')({
  loader: async () => {
    const response = await fetch('https://swapi.dev/api/people')
    return response.json()
  },
  component: PeopleComponent,
})

function PeopleComponent() {
  const data = Route.useLoaderData()
  return (
    <ul>
      {data.results.map((person) => (
        <li key={person.name}>{person.name}</li>
      ))}
    </ul>
  )
}

Loaders simplify your data fetching logic dramatically. Check out more information in the Loader documentation.

Demo files

Files prefixed with demo can be safely deleted. They are there to provide a starting point for you to play around with the features you've installed.

Learn More

You can learn more about all of the offerings from TanStack in the TanStack documentation.

For TanStack Start specific documentation, visit TanStack Start.