DutchEllie
/
proper-website-2
2
3
Fork 0
Code Issues 12 Pull Requests Projects Releases Wiki Activity
Truly proper website
139 Commits 2 Branches 0 Tags 22 MiB
Go 72.6%
HTML 14.6%
CSS 11.1%
Makefile 1%
Dockerfile 0.7%
Go to file
DutchEllie 083f560e1a
continuous-integration/drone/push Build is passing Details
Add destroy step? 		2022-07-04 17:20:25 +02:00
.drone/helm Deprecate to old 2022-07-04 17:18:03 +02:00
api For now disable sending UUID with comment 2022-06-25 12:13:40 +02:00
entity Add spyware module 2022-06-25 11:28:37 +02:00
src For now disable sending UUID with comment 2022-06-25 12:13:40 +02:00
test-website Rewrote guestbook 2022-03-15 16:42:26 +01:00
ui MOBILE 2022-06-22 13:45:43 +02:00
web Messed up desktop 2022-06-22 13:49:43 +02:00
.drone.yml Add destroy step? 2022-07-04 17:20:25 +02:00
.gitignore Shit, fucked up cluster-issuer 2022-06-29 16:25:49 +02:00
Dockerfile CI update 2022-05-14 21:09:48 +02:00
LICENSE Initial commit 2022-03-01 09:00:33 +00:00
Makefile Made generating static site possible 2022-05-27 20:35:53 +02:00
README.md [SKIP CI] Readme.md 2022-05-10 08:43:28 +00:00
comments.go.old Last 2022-03-12 15:52:13 +01:00
go.mod Add spyware module 2022-06-25 11:28:37 +02:00
go.sum Add spyware module 2022-06-25 11:28:37 +02:00

README.md

proper-website-2

Build Status

A truly proper website this time™

TODO:

  • Change domain to quenten.nl and staging.quenten.nl
  • 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 https://github.com/maxence-charriere/go-app/blob/master/docs/src/actions-page.go 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