I agree, making it more wiki-like would be good. However, it is what it is now because I wanted to get it thrown together quickly. I’m definitely open to visual design changes, it’s not very good right now.
The difference in back-end code (Wikis are easy to edit because you can go out and find example code for just about anything you’d want to do).
The good news is, there’s a lot of information about editing markdown pages and working with Jekyll. And it’s not too bad once you use it. But that feeds into your next point…
Despite being one of the editors of the original FIRSTwiki, I’m personally not familiar enough with GitHub editing to be able to contribute in any meaningful way at this point. If you want more help from editors like me, you need to work on two major things: Page templates (basically blank pages with the layout structure there, to allow for “fill in the blank” use) and example pages (a few pages of each type that are all, or mostly, filled in, so editors know what completed pages should look like).
The feedback I’m reading from you is that “we need a step-by-step guide for non-programmers to be able to contribute”. And I 100% agree. It’s not what people who haven’t used github are used to, and will take a small bit of education to get there. But it’s doable. Hopefully we can do that soon.
To more directly answer your embedded question (and I’ll try to add this to a page somewhere), consider the ‘mascots’ page on the wiki:
As you can see, the source file is super simple, just like a wiki.
If you wanted to edit the page, here’s what you would need to do (presuming you have a github account):
Editing the metadata on a team’s page is similar, but there’s different formatting. Yet another howto guide that needs to be created…
I have some ideas for having an online editor integrated with github’s API so you don’t have to know how to use github to edit… but that’s more involved and will have to come later.
Also, I’d be curious if Brandon made a backup of the original FIRSTwiki before taking it down, getting a copy of it from him could drastically speed up adding content to the site and help fill in details from more distant history that many of us either weren’t around for, or don’t remember well.
I contacted Brandon, and he was not able to find a backup. However, the copy that Archive.org has seems to be reasonably complete, and all the content I scraped from that is in the original_archive repo.