| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
This implements some accessibility guidelines, as hinted at by WAVE [1]:
- labels for textareas
- fieldsets for multiple-choice answers
One thing that's still missing is a set language, which I guess will be
best implemented together with an actual language switcher.
[1] https://wave.webaim.org/
|
| |
|
|
| |
(i.e. defined charset & a main tag)
|
| |
|
|
|
|
|
| |
this includes styling error messages red, and displaying error messages
in case not all answers were answered as required (for now, this just
means that not selecting any option in radio buttons is disallowed in
general, as so far there are no corresponding config fields).
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
this includes deduplicating some code, and attempts at error messages
for files which could not be parsed as json but aren't actually valid
age-encrypted files (there doesn't seem to be some easy way to validate
that these files are valid age files without knowing the key).
|
| |
|
|
|
|
| |
After a submission, the survey will now either redirect to a "thanks for
your answers!"-site (if the POST request had status 200) or else display
some kind of error message.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(previously, it tried to use ascii encoding and would fail)
|
| | |
|
| |
|
|
|
|
|
|
| |
these can be found in site/examples. There is a simple unencrypted survey
in "example.json", and an encrypted variant of the same in "encrypted.json".
The key used for encryption can be found in "key.age"; in particular, note
that the passphrase for the encrypted survey is exactly that private key.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This can be used to write configs in dhall (instead of plain json), combined
with some input validation and (optionally) automatic encryption via the age
rust crate.
|
| |
|
|
|
|
|
|
|
| |
The idea is that it can accept surveys sent to it. Note that in an actual
deployment it should have at least some rate-limiting, since actual validation
of input is impossible if they are encrypted – i.e. this is bascially a pastbin.
It may, however, be possible to require signing answers for survey with access
restrictions, or do a challange/response type thing before allowing submission.
|
| |
|
|
|
| |
the nix tooling for rust and wasm appears to be really bad, so binary blobs
are easier for now.
|
| |
|
|
|
|
|
| |
syntax: http(s)://domain.tld/path/to/file/index.html#[upload url]
The upload url may be relative to the site's position, or absolute.
Survey results will be POSTed to [upload path]/upload.
|
| |
|
|
|
|
| |
web assembly needs its own mimetype set to work in the browser, which most
other development tools don't support — so this python script can be used
instead.
|
|
|
this depends on age stuffed into web assembly, which is not yet
part of this repository.
The idea is to have a web app (which is a static html page + js / wasm)
and a set of (optionally encrypted) json files which describe surveys,
which the main site can download on demand.
|
