This is going to be a continuation, spiritual successor, call it what you will of my AdminDev Labs thread. I am going to revamp my website to be officially version 2.0 and change from Node.js to Golang. I’ll likely keep the CSS (trim it up, maybe) and use the HTML of the existing EJS.
It’s been around for a while and it’s starting to show, I think. Lately I’ve been focusing on software delivery and infrastructure as code (Groovy, Python, Ruby, Bash) so I’ve lost a bit of my webdev 31337 skillz I think.
This will be an all around refactoring, retooling, and relearning
Web server will be in Go, content will be CSS/HTML, and I’ll have a script to deploy/push changes to the server.
So far I’ve done a lot!
package main
import "fmt"
func main() {
fmt.Println("vim-go")
}
Lmao. That’s the boilerplate that comes with the vim plugin
Milligram looks cool. Their water drop “loading” is really what I’m trying to do.
My issue isn’t really not knowing what to use it’s what to do. I want the loading screen to have a black hole effect, where all the contents on the page “suck in” towards the center and the new page loads.
Just weird to conceptualize in something that I’m not terribly familiar with.
Few of my co-workers are getting into Go too, although we look at it from the C++ perspective. All this activity around it makes me think I need to look into it too, but I also need to learn modern C++.
Definitely worth it. Especially if you want in on embedded development stuff. Go has been fun.
It’s CSS that is killing me right now lol. Trying to get rid of the scroll bar on Firefox. It’s apparently not possible (not giving up).
I updated the about and podcast pages. It’s was pretty easy, basically copied and paste. I want to get some sort of caching going, too. Right now when I click between pages the “hero image” flashes. I’m hoping caching will remedy that (it did with Node.js).
Rough To-Do
+ Caching
+ Logging
+ Finish pages
+ Redirection/Error handling
+ Throw it on Heroku/DigitalOcean/AWS/Whatever