HEAD requests will be routed as GET requests, and Content-Type and Content-Length headers will always be sent for all requests.
Co-authored-by: Ben Visness <bvisness@gmail.com>
Reviewed-on: #104
Start foundation / about page work
Add some job descriptions
Add Advocacy role
Make things look barely tolerable
Cloin'd
Better About intro
no fundo
Link from manifesto
swanky changes
Code notes:
* ❗ MathJax treats text between two dollar signs as math. Escaped those cases in html (`\$`) - is there a way to not run mathjax on fishbowls instead?
* Limited embed image sizes to match Discord
* Fixed replies to a quote wrapping on a new line
Content notes:
* Moved intros to the top, untangled the discussions (hopefully without significant loss), pulled in audience comments
* Most book links are to Amazon as the promo websites are shitty or non-functioning
* Demetri had interesting points in -audience afterwards but they tie to Allen and may be hard to pull in without a lot of context
* Catchy title and description are TBD as usual
Co-authored-by: Ilia Demianenko <ilia.demianenko@gmail.com>
Reviewed-on: #99
Co-authored-by: ilidemi <belk94@gmail.com>
Co-committed-by: ilidemi <belk94@gmail.com>
It didn't work when creating a new project or editing personal projects,
due to routing issues. I also took this opportunity to make the script
support multiple form submit buttons, since in some cases we will have a
submit button on each tab, and I figured they all should respect the
fact that you have an upload in progress.
I migrated the relevant parts of `editor.html` and `forums.go` (via `blogs.go`) into `project_edit.html` and `projects.go`.
Let me know if you would prefer pulling the shared javascript into a shared file. Only some variable names were changed.
I did not test the case where the upload fails.
Co-authored-by: mark.dev <mark@mark.dev>
Reviewed-on: #77
Co-authored-by: mark.dev <mark.dev@noreply.localhost>
Co-committed-by: mark.dev <mark.dev@noreply.localhost>
Only needs someone with creative juices to write a description and good to go!
Co-authored-by: Ilia Demianenko <ilia.demianenko@gmail.com>
Reviewed-on: #78
Co-authored-by: ilidemi <belk94@gmail.com>
Co-committed-by: ilidemi <belk94@gmail.com>
#33 progress: 9/10
Pulled a couple of conversations from the audience
Co-authored-by: Ilia Demianenko <ilia.demianenko@gmail.com>
Reviewed-on: #61
Co-authored-by: ilidemi <belk94@gmail.com>
Co-committed-by: ilidemi <belk94@gmail.com>
#33 progress: 7/10
Oh boy, this one has a good amount of links
Also updated bumbo's discord id in skimmability fishbowl
Co-authored-by: Ilia Demianenko <ilia.demianenko@gmail.com>
Reviewed-on: #58
Co-authored-by: ilidemi <belk94@gmail.com>
Co-committed-by: ilidemi <belk94@gmail.com>
#33 progress: 3/10
Significant changes:
Moved pre-intro discussion after intros, cleaned up what I saw as noise
Pointed bumbo to his current discord id - if a different one is linked to the website, lmk
Co-authored-by: Ilia Demianenko <ilia.demianenko@gmail.com>
Reviewed-on: #45
Co-authored-by: ilidemi <belk94@gmail.com>
Co-committed-by: ilidemi <belk94@gmail.com>
This takes advantage of generics, and generally clears up a lot of
inconsistencies and quality-of-life issues.
Start of db rework: clean up, start generics, improve tests
Write some nice aspirational package docs
Rework and document the db API
Tests still pass, at least...now for everything else
Update all callsites of db functions
Finish converting all callsites
Not too bad actually! Centralizing access into the helpers makes a big
difference.
wtf it works
The code of conduct has historically not been of much use, while the
communication guidelines are more tangible. The two are also just kind
of redundant.