GithubHelp home page GithubHelp logo

psenough / livecode.demozoo.org Goto Github PK

View Code? Open in Web Editor NEW
22.0 6.0 17.0 357.23 MB

archive of demoscene related live coding events

Home Page: http://livecode.demozoo.org

GLSL 65.78% Python 2.22% HTML 6.63% CSS 0.67% HLSL 0.39% JavaScript 0.20% Lua 22.38% Fennel 0.06% Jinja 0.06% Assembly 1.60%
shader-showdown shader-effect documentation

livecode.demozoo.org's Issues

about page

create an about page with info on what demoscene is, live shader coding is, live bytebatttle is, links on how to get started and participate on upcoming events. also link to repo requesting people to do PR to fix missing data.

Cache does not persist new data in current workflow

Since the commit-triggered workflow now commits to branch gh-pages instead of main, newly downloaded images as well as handles looked up from Demozoo are downloaded again on every run instead of being persisted after the first successful download/lookup to public/media and cache/handles.json, respectively.

While the Demozoo handle lookup is integrated in the generate_html.py script, images are downloaded as a separate workflow step.

I assume we should be able to commit to the main branch after the "Download Images" step, then switch to a fresh(!) gh-pages brand (as we currently) do, trigger HTML generation, and commit to gh-pages.

Add nova 2022

{
    "title": "Nova 2022",
    "started": "2022-08-12",
    "type": "Shader Showdown",
    "website": "https://novaparty.org/#compos--shadershowdown",
    "flyer": "",
    "software_used": [
        {
            "name": "Bonzomatic",
            "url": "https://github.com/Gargaj/Bonzomatic/",
            "version": "Original Bonzo",
            "purpose": "Graphic"
        }
    ],
    "staffs": []
}

Move public data to a sub-path

What

I strongly suggest to introduce a sub-path exclusively for files that should be part of the generated website (i.e. rendered HTML documents, assets).

How

GitHub pages has an option to specify a different folder than / (in "Settings" โ†’ "Pages" โ†’ "Source).

In my experience, the CNAME file has to be moved to the new path as well.

Why

Currently all data from the repository (minus .git/, at least) is published as part of the website. This includes the code to generate the site, the original JSON data files, etc. While the data is public on GitHub anyway, it shouldn't be included in what is served as the website.

PR

I made #39 which lays a bit of ground work towards moving public website data to a separate path. After that is merged, I would like to attempt a solution to this issue in a new PR.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.