+47
-30
README.md
+47
-30
README.md
···+This was an idea that sparked off a great discussion around decentralizing archives for fanfics and fan works. What if we could have archives that:+I'm setting out to explore these questions by building a prototype of a fanfic archive on Astro and AtProto.+... And probably more, and there's a lot of discussion around how user data ownership / censorship / etc gets handled on those layers.+In our case, we'll only worry about making the client and then get drafts of the lexicons from the community later.+Mainly because: 1, Astro is a really well-documented web framework that's pretty approachable as someone who used to handwrite HTML pages; 2, SQLite / LibSQL are (to my knowledge) fairly cheap databases to run; and 3, Unstorage is pretty dead simple for setting up auth sessions from scratch.+These hold actions that run every time a user wants to publish a new work or signs up for the archive.-Astro looks for `.astro` or `.md` files in the `src/pages/` directory. Each page is exposed as a route based on its file name.-There's nothing special about `src/components/`, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.+These hold components that are reused throughout `src/pages`. Like PHP includes but in HTML and JavaScript (well, technically it's JSX).+This holds all the relevant database connecting code. This also contains the types for database tables.-Feel free to check [our documentation](https://docs.astro.build) or jump into our [Discord server](https://astro.build/chat).+These are the actual pages where data, user interactions, etc happen. So this would be more HTML/CSS/JavaScript-oriented.
-46
src/lib/db.ts
-46
src/lib/db.ts
···
+12
src/lib/db/drizzle.config.ts
+12
src/lib/db/drizzle.config.ts
···
+24
src/lib/db/index.ts
+24
src/lib/db/index.ts
···
+23
src/lib/db/schema.ts
+23
src/lib/db/schema.ts
···