Flat File Wikis

From BTAWiki
Jump to navigation Jump to search

Requirements

Individuals should list their requirements, and others should make sub lists with "Accepted/Not Accepted" and any discussion points

Example: 

==Fake Requirements==
* Full Emoji Support
** Amid: Not Accepted
*** You're dumb and bad
* No PHP
** Amid: Accepted
*** Sane
* No Java
** Amid: Accepted
*** It's 2024, fuck off with JVMs.

Amid's Requirements

  • Uses Markdown or similar "light" language that is easily understood
  • No PHP
  • No Java
  • No Lua
  • Can be hosted in light CMS options
  • Looks purdy/Modern
  • Sane picture/media support

Wulf's Requirements

While markdown is pretty great for most things, I can even see simple html+css going strong. There is a few things that are quality of life that we have now, or would like to get, that I don't know how to achieve. These may only be relevant for a few pages, that may be semi-manual or generative, and could be explicitly using HTML instead of a markdown default, but I don't know how to do this in Markdown. W1; Sortable Tables. I am unaware of any way to do this in markdown. This may only be relevant for a few pages, the list of mech overviews W2; Embeddable Images. I think there's a few markdown things that play with html tags or ![alt text](image_url). We use these in some guide stuff, and it'd be nice to not loose functionality.

W3; TextTable Loadouts. Instead of updating pictures of the loadouts, generate loadouts in a nice positional layout like in the game. This would save all the storage and traffic, and should make the website more responsive and intuitive to use. I can imagine doing this in markdown with a fake table grid or so, but then hiding empty fields is like a weird extra layout step, and wouldn't know how to do this in markdown.

BD's Requirements

Final Requirements

To be built after we agree on them

Options So Far

Other Discussion

Retrieved from "https://www.bta3062.com/index.php?title=Flat_File_Wikis&oldid=54220"