Truly proper website
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
DutchEllie 083f560e1a
continuous-integration/drone/push Build is passing Details
Add destroy step?
1 year ago
.drone/helm Deprecate to old 1 year ago
api For now disable sending UUID with comment 1 year ago
entity Add spyware module 1 year ago
src For now disable sending UUID with comment 1 year ago
test-website Rewrote guestbook 2 years ago
ui MOBILE 1 year ago
web Messed up desktop 1 year ago
.drone.yml Add destroy step? 1 year ago
.gitignore Shit, fucked up cluster-issuer 1 year ago
Dockerfile CI update 1 year ago
LICENSE Initial commit 2 years ago
Makefile Made generating static site possible 1 year ago [SKIP CI] 1 year ago
comments.go.old Last 2 years ago
go.mod Add spyware module 1 year ago
go.sum Add spyware module 1 year ago


Build Status

A truly proper website this time™


  • Change domain to and
  • Dynamically make domains for other branches
  • Make a generic page component, so that you don't have to add the standard panels every time (such as navbar, leftbar, header, etc)

App notes:

  • leftbar (under nav) is default always the same. This is in a standardized "page" component. it can be changed by specifying it when creating the "page" component, or maybe in a prerender/onnav (or both). Structure will be: Generic page component IS IMPLEMENTED BY "specific page" WHERE OnNav/OnPreRender specify its details WHICH IS CREATED with its own "newXPage()" function. See for example.
  • "main content" is an array of app.UI elements. This can also be further abstracted using "block" components (the ones with the cool color)
  • THOSE BLOCK COMPONENTS' CONTENT can be set manually on creation, OR by passing HTML/MarkDown (not decided yet)

This website will be done with this:

  • Backend written in Golang
  • Templating with Go
  • Database connection for comments and such
  • Markdown article writing

It will be done in the following order:

  • First get up a working simple proof of concept
  • Then make the comments better
  • Database better
  • Layout
  • Markdown article writing
  • Layout