added an idea of how to do the database schema. for #2

docs/design/database.org

@@ -0,0 +1,46 @@
+#+TITLE: Database Schemas
+
+
+* User
+  - id
+  - username :: String
+  - email :: String
+  - password :: encrypted_and_hashsalted_string
+  - salt :: salt
+  - perms :: Enum/Integer
+  - bio :: Text
+  - avatar :: references: upload
+* Issue
+  - id
+  - title
+  - description :: Text
+  - cover :: references: upload
+  - author :: references: user
+  - cw :: Text
+  - mature :: integer (Flags) or enum
+  - release_date :: timestamp
+  - added :: timestamp
+  - available :: boolean
+  - options :: json? 
+* Page
+  - id 
+  - issue :: references: issue
+  - page_num :: integer
+  - spread :: boolean
+  - title :: String
+  - upload :: references: upload
+  - caption :: Text
+  - cw :: Text
+  - mature :: integer (flags) or an enum
+  - added :: timestamp
+  - release_date :: timestamp
+  - author :: references: user
+* Upload
+  - id
+  - file :: Filepath
+  - uploaded :: timestamp
+  - locked? :: boolean
+  - author  :: references: user
+  - deleted :: boolean
+  - modified :: timestamp
+  - deleted_date :: timestamp

docs/design/wants.org

@@ -0,0 +1,9 @@
+* Base Base Wants
+  - Ability to host issues and volumes, showing a cover.
+  - ability to handle a multipage view, reading two pages at a time
+  - Transcripts
+  - Content Warnings per pa
+  - Atom/RSS feed generation
+
+* Stretch Goals
+  - ActivityPub feed + m/RSS feed generation