# Weird webpage generator ## Product Vision - https://blog.erlend.sh/weird-web-pages - https://blog.erlend.sh/weird-inc ## Proof of Concept The primary of our first PoC is a static site export that can easily be pushed to one of the popular free host providers: https://github.com/commune-org/weird-rs/issues/3 The flow goes something like: - download Weird app (Tauri app) - Basic link entry & sorting onepager (supersedes a more low-fi proposal for a myonepager.toml) - initiate 'Build Website' in Weird-app - initiate Push Website to GitHub (or Netlify et.al.) (via GitHub action) in Weird-app TODO apps provide useful prior art for the minimal UI needed. ![](https://i.imgur.com/zMcBYzG.png) - https://github.com/sammi-turner/Tauri-Todos - https://github.com/parker-codes/todos-app All we really want to add to this for our PoC is a ‘generate site’ button at the bottom, which then hands over a list of links for `adapter-static` to generate a site with. ## Implementation notes > well, we can actually ship a "batteries-included" dist folder and then append it with a "content.json" that is used to build the website that way we don't even need to ship any extra tooling > > that way we don't even need to ship any extra tooling > > heck, premade style bundles could even be fetched remotely from some github contrib raw zip source > > THAT could be a good phase 2 > > phase 1 would be to get it to work and ship a base template dist with the app, and decide on the conventions > I am arguing for NOT shipping DENO / NODE in the very first instance we ship a prebuilt /dist that expects a /dist/content.json to be added by the app that can be manufactured in the CI/CD the content.json would look like this: ``` { "style": "color:rebeccapurple", "header": { "text": "Denjell", "link": "https://github.com/nothingismagick" } } ``` > where "style" applies CSS overrides, and "header" is a component type with "text" and "link" elements obv we can have many other component types the nice thing about this approach, is that we can actually dogfood these components and override them INSIDE the tauri app in a second window and show a preview before they even build them ## Scope We know we've completed phase 1 of this PoC when the personal website `erlend.sh` is up and running as a result of this website generator. ## Future Phases Possible avenues to explore: - https://blockprotocol.org - https://blog.netnerds.net/2022/11/alias-mastodon-github-pages/ - https://github.com/commune-os/weird-rs/issues/8 - https://github.com/rafaelcastrocouto/node-uda - https://github.com/sw-yx/swyxkit - https://github.com/commune-os/weird-rs/issues/3 - https://github.com/michael/editable-website - https://github.com/oddsdk/odd-app-template/ - https://blog.jim-nielsen.com/2023/well-known-avatar/
Last changed by  
 
Erlend Sogge Heggen
587

Read more

Open-Source Curriculum (v0.1.1)

(also ideal for viewing) In brief: A curriculum for students of 'open source' as it is practiced by open source spftware developers. Whether you’re a newcomer to open source or you’ve been involved with the practice for some time, this curriculum aims to provide a comprehensive overview of everything open source is, and aspires to be. This document aspires to become a comprehensive reading list for anyone seeking to deeply understand ‘openness’ as an ideology for knowledge work, a distributed movement, a commercial industry and more yet to come. Open Source as a subset of openness https://en.wikipedia.org/wiki/Openness

7/23/2022
Bevy Editor-UI research

Target https://github.com/bevyengine/bevy/issues/254 Before we can start work on the Bevy Editor, we need a solid UI implementation. Bevy UI already has nice "flexbox" layout, and we already have a first stab at buttons and interaction events. But Bevy UI still needs a lot more experimentation if we're going to find the "right" patterns and paradigms. Editor-Ready UI has the following requirements: Embraces the Bevy architecture: Bevy ECS, Bevy Scenes, Bevy Assets, Bevy Events A Canvas-style API for drawing widgets with shapes and anti-aliased curves Define a consistent way to implement widgets A core set of widgets: buttons, inputs, resizable panels, etc Theme-ability

10/15/2021
Intro

Intro Game core 2.1. Game loop 2.2. Tiled 2.3. World 2.3.1. Object hierarchy 2.3.2. Player

9/21/2021
Low-poly strategy

How we can use low-poly resources as high-res greyboxes for the first 6-12 months of development. I think low-poly is a very natural starting point for a game that wants to be as modding-friendly as possible. If the average asset creator needs to create this kind of HD scene: ..then there’s gonna be a lot of people who tap out right away, because they can tell that it’ll take them too darn long to be making something of that detail. Having to make something like this is much less daunting: The simplicity of low-poly also makes it a more powerful target for novel rendering techniques. There are loads of smart ways to give low-poly a distinct, fresh look at low cost:

3/21/2021
Read more from Erlend Sogge Heggen
Published on HackMD