diff --git a/content/.obsidian/workspace.json b/content/.obsidian/workspace.json index c7f194f9..3887c469 100644 --- a/content/.obsidian/workspace.json +++ b/content/.obsidian/workspace.json @@ -13,13 +13,38 @@ "state": { "type": "markdown", "state": { - "file": "Star Sailors/Pages/Gather.tsx.md", + "file": "Projects/Star Sailors Frontend/SSF-1.md", + "mode": "source", + "source": false + } + } + }, + { + "id": "6090b12b72db5d75", + "type": "leaf", + "state": { + "type": "markdown", + "state": { + "file": "Star Sailors/Narrative/Crafting.md", + "mode": "source", + "source": false + } + } + }, + { + "id": "70991b8c6045dd36", + "type": "leaf", + "state": { + "type": "markdown", + "state": { + "file": "Projects/Star Sailors Anomalies/GP-10.md", "mode": "source", "source": false } } } - ] + ], + "currentTab": 2 } ], "direction": "vertical" @@ -85,7 +110,7 @@ "state": { "type": "backlink", "state": { - "file": "Star Sailors/Pages/Gather.tsx.md", + "file": "Projects/Star Sailors Anomalies/GP-10.md", "collapseAll": false, "extraContext": false, "sortOrder": "alphabetical", @@ -102,7 +127,7 @@ "state": { "type": "outgoing-link", "state": { - "file": "Star Sailors/Pages/Gather.tsx.md", + "file": "Projects/Star Sailors Anomalies/GP-10.md", "linksCollapsed": false, "unlinkedCollapsed": true } @@ -125,7 +150,7 @@ "state": { "type": "outline", "state": { - "file": "Star Sailors/Pages/Gather.tsx.md" + "file": "Projects/Star Sailors Anomalies/GP-10.md" } } } @@ -146,9 +171,18 @@ "command-palette:Open command palette": false } }, - "active": "6f20c036690036e0", + "active": "70991b8c6045dd36", "lastOpenFiles": [ + "Daily tasks.md", + "Projects/Star Sailors Anomalies/GP-10.md", + "Projects/Star Sailors Anomalies", "Projects/Star Sailors Frontend/SSF-1.md", + "Star Sailors/Narrative/Crafting.md", + "Projects/Notes/Quick Plans.md", + "Star Sailors/Setup.md", + "Star Sailors/Narrative/Order of Operations.md", + "Star Sailors/Components/Content/Create Planet Sector.md", + "Star Sailors/Components/Content", "Star Sailors/Pages/Gather.tsx.md", "Star Sailors/Pages/Planets/Sector/id.md", "Star Sailors/Pages/Planets/Sectors/id.md", @@ -156,20 +190,15 @@ "Projects/Star Sailors Bugs/SSB-1.md", "Star Sailors/Pages/Planets/Sectors", "Star Sailors/Pages/Planets", - "Star Sailors/Narrative/Crafting.md", "Projects/Star Sailors Bugs", "Planning/StructureNarrative.md", "Planning/ComponentList.md", - "Projects/Notes/Quick Plans.md", "Projects/Notes/Protocols.md", "Untitled", - "Star Sailors/Setup.md", "Star Sailors/Narrative", "Star Sailors/API", "Star Sailors/Pages", "Star Sailors/Components/Tables/ContentRoverImages.md", - "Star Sailors/Components/Tables", - "Star Sailors/Components/Section", "Star Sailors/Components/Forms/CreatePostForm.md", "Star Sailors/Components/Classify/PostCard.md", "Star Sailors/Components/Classify/DiscussCard.md", diff --git a/content/Daily tasks.md b/content/Daily tasks.md new file mode 100644 index 00000000..f2bcee59 --- /dev/null +++ b/content/Daily tasks.md @@ -0,0 +1,62 @@ +1. Come up with todo list & structure by the hour -> including for the hours we're having our coffee +2. Dynamic plan for keepup, including logo +3. Check "promised" timeline for nk12 and prepare daily milestones +4. Contact Manu and produce a list of 10 components, provide a bit of discussion +5. Create plan for microservices, integration into `sytizen`, workflow for Unity (including action), discuss plan for integrating new UI & actions with microservices, automated tests. + 1. d3.js v0.dev based on lightcurves? +6. Continue with migration to Quartz + +### Microservices +1. Method for generating lightcurve, integrating into d3 +2. Method/route for populating anomaly/entity data -> sample, point to old routes in `signal-k/sytizen` repo + +### Nordkurve +Phase 1 -> +1. Registration, migration and schema setup +2. "Backend" portal (really a frontend, though, technically) for admins/board to view all data + +### Keepup +What we have now -> +1. Bottom bar +2. Main area/content grid + +Minimum viable product -> +1. Push notifications +2. Method to create a feed +3. Posts will be pushed from a local dictionary for now -> no server-side action for this component +4. Ability to "favourite" posts/messages, these will be saved in runtime state +5. Post category + +Post features: +1. Content +2. Avatar, title/user sender metadata +3. Favourite, user-determined metadata + +### Copernic +Possible components: +1. Discussion board, based around bucket/node + 1. Discussion board would be divided into Lens & other protocols (for now, off-chain) +2. News feed for nodes +3. Metadata/custom tags (e.g. linking to a "proper" dsl node) +4. Documentation area -> just do it here on quartz for now + 1. Should include videos/tutorials on how to use our platform +5. Physical data tracker -> could be especially useful for copernic passports? +6. Ask gpt for another 5. + +Focus on minimal/incomplete UI, the priority is reasoning, brainstorming, documentation and minimum functionality for presentation + +### Travel +Key dates: +1. May 18 -> Bayer Leverkusen vs FC Augsburg (11.30pm melbourne) +2. May 22 -> Europa League Final (Dublin) ** +3. May 25 -> DFB Pokal Final (Berlin) ** + +So some options -> +* Go for the week +* Go for first two +* Go for second two + +No other key conferences as far as I'm aware + +Key questions -> +1. Is it worth focusing on achieving Velocity Platinum or trying to maximise United Airlines/Star Alliance? keeping in mind I'm going to the US at least one more time this year \ No newline at end of file diff --git a/content/Projects/Notes/Quick Plans.md b/content/Projects/Notes/Quick Plans.md index a560c238..54080427 100644 --- a/content/Projects/Notes/Quick Plans.md +++ b/content/Projects/Notes/Quick Plans.md @@ -18,4 +18,6 @@ Supabase microframeworks + deepnote Jira export into Quartz -Tags -> for projects, also tag git issues/commits (maybe use Github discussions/issues like utteranc.es. The key here is creating a workflow that is simple to follow. Maybe custom account management would be the way to go, don't want to lock into using Github) \ No newline at end of file +Tags -> for projects, also tag git issues/commits (maybe use Github discussions/issues like utteranc.es. The key here is creating a workflow that is simple to follow. Maybe custom account management would be the way to go, don't want to lock into using Github) + +Create issues from project pages, tag those? -> question then is how do we set up a migration/export if we want to move to a self-hosted solution or another git client like gitlab? \ No newline at end of file diff --git a/content/Projects/Star Sailors Anomalies/GP-10.md b/content/Projects/Star Sailors Anomalies/GP-10.md new file mode 100644 index 00000000..bcc15d5f --- /dev/null +++ b/content/Projects/Star Sailors Anomalies/GP-10.md @@ -0,0 +1,20 @@ +--- +title: GP-10 +tags: + - Star-Sailors + - Content + - Sector + - Structure + - Building + - Anomaly +--- +https://signalk.atlassian.net/browse/GP-10?focusedCommentId=10122 + +Minimum requirement -> +1. Allow users to build structures on a planet's sector +2. Require classification to do so (this will, for now, be contingent on the user having set a `basePlanet` as their `profiles.location` field, which right now is done via fiddling with the backend -> but it could be considered to be an equivalent barrier) +3. Link the structure that has just been placed to the next step of classification. Provide a pathway to generate additional context/information once the user has placed that structure. + +A child issue, GP-11, has been created and will be targeted towards the microservice for validating correct items & crafting recipes. + +Some additional context has been added to the Jira issue, which has been handballed to Rhys for completion/filing \ No newline at end of file diff --git a/content/Projects/Star Sailors Frontend/SSF-1.md b/content/Projects/Star Sailors Frontend/SSF-1.md index 25d9f640..72f2c8e1 100644 --- a/content/Projects/Star Sailors Frontend/SSF-1.md +++ b/content/Projects/Star Sailors Frontend/SSF-1.md @@ -21,8 +21,10 @@ Click on Unity block -> open web-based context? ### To look into: 1. Hexagons & sectors, data using `d3.js` + 1. For the sector maps, one of the goals was to have a single image that is split into multiple hexagons, right now it's a grid of squares (masquerading as "hexagons") that each have a separate "cover" image 2. Boilerplating/microservice to migrate from custom `base...` tables to regular tables once we've added multiple collections ### Organisation * Complete `Components` & `Pages` dir in the notes -* Establishing understanding of branches & current tasks, archived jira tasks/branches \ No newline at end of file +* Establishing understanding of branches & current tasks, archived jira tasks/branches +* Can we get a coherent structure & understanding of what files are relevant, what (non-default) functions are being put in secondary files, etc \ No newline at end of file diff --git a/content/Star Sailors/Components/Content/Create Planet Sector.md b/content/Star Sailors/Components/Content/Create Planet Sector.md new file mode 100644 index 00000000..98831c9a --- /dev/null +++ b/content/Star Sailors/Components/Content/Create Planet Sector.md @@ -0,0 +1,50 @@ +--- +title: CreatePlanetSector.tsx +tags: + - Star-Sailors + - Sector + - Empty +--- + +Path: `components/Content/Planets/CreatePlanetSector.tsx` + +```tsx +import React, { useEffect, useState } from "react"; + +import { useSupabaseClient, useSession } from "@supabase/auth-helpers-react"; + + + +function CreatePlanetSectorComponent ({ planetId }) { + +const supabase = useSupabaseClient(); + +const session = useSession(); + +const [isLoading, setIsLoading] = useState(false); + + + +const createSector = () => { + +if (!session) { return; }; + + + +if (!planetId) { return; }; + + + +// Generate random mineral deposits - will later be set in db + +const depsitCount = Math.floor(Math.random() * 5); + +}; + +}; +``` + +I think this might be a component/script that was unfinished? Must look into this + +Update -> appears `components/Content/Planets/IndividualPlanet.tsx` is also another component. Might be from the v1 (`CPW-8` branch) template + Update 2 -> actually another way of showing the planet content in dynamic routing/pages. So should keep that here for now \ No newline at end of file diff --git a/content/Star Sailors/Narrative/Crafting.md b/content/Star Sailors/Narrative/Crafting.md index bd74caea..538a8c8f 100644 --- a/content/Star Sailors/Narrative/Crafting.md +++ b/content/Star Sailors/Narrative/Crafting.md @@ -16,11 +16,13 @@ tags: * Copper * Chromium * Nickel +* Water Some notes -> 1. Silicates should either be composed of, or smelt into, silicon 2. Alloy currently consists of a combination of multiple trace metals for simplicity 3. Fuel will be explored more in subsequent versions + 1. As an example, you can't just mine fuel from a sector IRL, you'd need to mine raw materials, as well as collect them from the atmosphere, refine them, etc ## Structures ### Exploration diff --git a/content/Star Sailors/Narrative/Order of Operations.md b/content/Star Sailors/Narrative/Order of Operations.md new file mode 100644 index 00000000..a88ff879 --- /dev/null +++ b/content/Star Sailors/Narrative/Order of Operations.md @@ -0,0 +1,23 @@ +--- +title: Star Sailors - Crafting & Inventory Operations +tags: + - Star-Sailors + - Content + - Narrative + - Planning + - Sector +--- +> Raw material [combination] → base building block → tool/structure/vehicle or other entity + +Current setup: +1. /Gather page -> list of all sectors, ability to create new sectors +2. Create sector -> Take a random raw material, add that as the mineral deposit for the sector + +It would probably be a good idea to get a list of all the files relevant to the gather and sector components to begin identifying possible duplication/code redundancy. + +`