Code Monkey home page Code Monkey logo

vaarn.github.io's People

Contributors

adams-michael avatar graculusdroog avatar gulluth avatar omniczech avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

vaarn.github.io's Issues

CC-BY-SA-4.0 to CC-BY-4.0 License

There was a discussion about the licensing discrepancies between the zines, and the SRD, and which Creative Commons license everything falls under. This was asked by the discord user JeremyZ in the #game-jam channel during the Vaults of Vaarn summer jam.

This issue is to discuss the conversion of the SRD from CC-BY-SA-4.0 to CC-BY-4.0.

Cross-link Tables to Mobs

Cross-link the Random Encounter, and Lair tables from regions/interior.md to the appropriate bestiary entries.

merge roll tables where appropriate

The roll tables were copied from the zines, and the zines were formatted for A5 pages. Thus some tables were split to accommodate this format. As long as merging these tables does not cause left-right scrolling, merge the tables into a single table.

Tables affected by this:

  • Ancestries
  • Gear

Font Color CSS

Update the vov.css stylesheet to override the green color of the text from the default Docsify theme.

@GraculusDroog do you have any preference on the hyperlink highlighting color? I was thinking the blue-gray (#92BEC7) from the background of VoV #1's itch page.

Remove 3rd party store URLs from the SRD

Vov 1-3 and the DE are out of print and largely unavailable. The two exceptions for the zines availability are Leo's store Antipode, and Lulu for print on demand. Since maintaining these links for future releases of the zine will result in whack-a-mole with 3rd party eCommerce platforms, I am opting to remove the 3rd party links entirely while maintaining links to Leo's store and Lulu.

This affects README.md and translations (vaarn-ko).

Constant width tables

Right now the tables are variable width, and so there are various size tables that disrupt the page flow. Convert the tables to constant width using CSS.

960px or percentage based on browser size, I don't know, I need to research current trends.

VoV 3 ancestry tables

Fix the tables for VoV 3 ancestry tables. These were combined into a single table, but causes left-to-right scrolling to see the full table with 1080p displays.

update language used in physical products

In the print and pdf versions of the zines, words such as "phamphlet" and "zine" are used, update these to use "srd" where appropriate. This might be on a case-by-case basis, as we are trying to preserve the original content as closely as possible.

Footnote

In referee-rules.md there is a footnote under the Rations section. I am not sure how best to use this for web, so I am leaving this bug here to remind me. Perhaps Leo can guide how this information is relayed.

References to "zine" in the SRD should be edited

This report compiles a list of references in the SRD to it being a zine. This language was carried over directly to the SRD from the zines when it was converted to web.

  • acknowledgements.md
    • 'add to the contents of this zine' on line 2.
    • 'downloaded the previous issues of this zine' also line 2.
  • the-interior.md
    • 'use the tables provided in this zine' on line 6.
    • 'the hex-chart on the opposite page' on line 122
  • content-generators.md
    • 'Use the generators on the following pages' on line 2.
  • regions/gnomon.md
    • 'Such techniques are detailed further in the following faction pages.' on line 29.

Content reorg

This is a place holder and is currently the last item in this project that should be considered.

I would like to evaluate if it makes sense to reorganize the content of the SRD. I am thinking about how future zine content will be integrated into the existing SRD, if @GraculusDroog continues to publish the content under a creative commons license. I also want to consider the differences between the _sidebar.md and the Table of Contents in the Deluxe Edition.

remove duplicate tables from VoV #1

The tables that are under the Content Generators header come from VoV #1. Some of these tables were revised and added to the Creating Regions section of VoV #3. The duplicate tables under Content Generators need to be removed.

Merge introductory text into a single document.

The SRD was originally a direct conversion from print to web. This created a few issues such as the web still referring to itself as a zine (#26), but also a haphazard merging of the introductory "welcome to vaarn" text.

With the removal of links to 3rd party stores (#27) the resulting landing page will become sparse, also I feel like the contents of README.md and what-is-vaarn.md could be merged into a single document that is served up as the landing page when folks visit the SRD. This will be similar to the editing that was done in the DE.

acknowledgements page formatting

The formatting for acknowledgements.md was retained from the space constrained section of the last page of VoV3. This formatting makes the content a little hard to parse on web, and creates a very long single line in git. I have also proposed that this page could be used to list SRD contributors (#29), so updating the formatting would help the flow of the page for if/when this content is added.

Add a contributors section

I would like to add a section to list contributors to the SRD. It does not matter if those contributions are large, such as a complete language translation, or minor such as a fix to formatting, contributors should be recognized for their contributions.

Adding this content to the acknowledgements.md document could be the right place for it, but maybe a dedicated contributors.md is better? I don't know right now and want to discuss.

When the location is identified, the footer section ' user contributions' needs to be updated to link to the anchor or document listing the contributors.

HTML Linter

The HTML needs to be linted for missing table markup.

Add a how-to-translate guide.

I want to encourage translations for the Vaarn SRD, but I also want to create a process that can be followed so the translation repositories end up correctly formatted for inclusion in the language selector.

There is a Spanish translation provided by Inguaz and Dark Soups on the VoV Discord that I will use to define this process as I convert the google doc to web.

I have a rough document started by google gemini that defines this process very generically, I will use this as a starting point but it needs significant modification. Thanks evil AI overlords for the first draft!

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.