subdomains or subdirectories? (see e.g., this post)
Currently leaning towards subdomains, such as blog., volunteer., subscriber., etc. for example. The latter 2 are justified as these will be distinct apps (TODO: make sure about this): one for volunteers and one for subscribers (or readers). The first one should probably be a subdirectory (e.g., accessnews.org/blog)
NOTE 2022-11-11 11:53 Subdirectories can also be routed to different web applications, so my point above is moot. Do more research.
static main site (accessnews.org)?
It should only be hosting information and if people want to log in to volunteer, listen to content, etc. they should be redirected to the respective web applications.
[ ] TODO: choose a static website engine (current choice is styx, because it is based on Nix, but it is undocumented and will take some time to decipher; keep looking)
storage (related: #4): IPFS would be a perfect fit
Closing this and creating new issues with these items labeled with accessnews.org. This issue served its purpose by making it possible to quickly jot down ideas, but we are now starting to implement the site.
subdomains or subdirectories? (see e.g., this post)
Currently leaning towards subdomains, such as
blog.
,volunteer.
,subscriber.
, etc. for example. The latter 2 are justified as these will be distinct apps (TODO: make sure about this): one for volunteers and one for subscribers (or readers). The first one should probably be a subdirectory (e.g.,accessnews.org/blog
)NOTE 2022-11-11 11:53 Subdirectories can also be routed to different web applications, so my point above is moot. Do more research.
static main site (
accessnews.org
)?It should only be hosting information and if people want to log in to volunteer, listen to content, etc. they should be redirected to the respective web applications.
storage (related: #4): IPFS would be a perfect fit