The new Ripple frontend.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Giuseppe Guerra 3fc0620d69 Merge branch 'master' of zxq.co:ripple/hanayo 11 mesi fa
data Ranking criteria fixes 1 anno fa
modules Updated hardcoded server ips 1 anno fa
routers Bancho API privs, Bancho OAuth, update api vendor 1 anno fa
scripts Update locales 2 anni fa
semantic Fix placeholder color being completely white 3 anni fa
services Finish token creation pages 3 anni fa
static Bancho API privs, Bancho OAuth, update api vendor 1 anno fa
templates Ranking criteria fixes 1 anno fa
vendor Bancho API privs, Bancho OAuth, update api vendor 1 anno fa
website-docs @ 1bd4238f62 Updated submodule website-docs 11 mesi fa
.drone.yml add drone 2 anni fa
.editorconfig add drone 2 anni fa
.eslintrc eslint config 2 anni fa
.gitignore Add basic oauth flow 3 anni fa
.gitmodules Add submodule website-docs 3 anni fa
2fa.go append query to redir URL in 2fa 3 anni fa
Gopkg.lock Bancho API privs, Bancho OAuth, update api vendor 1 anno fa
Gopkg.toml require license to be agreed before starting hanayo 2 anni fa
LICENSE Forgetting we are using GNU AGPL: check 3 anni fa
README.md Explain why you shouldn't write code like hanayo in the README 2 anni fa
avatar.go ADD EVERYTHING TO TEMPLATES FILE OH YEAH 3 anni fa
beatmap.go merge appends and remove shiet 2 anni fa
context.go fix breaking changes 2 anni fa
dev.go Bancho API privs, Bancho OAuth, update api vendor 1 anno fa
doc.go ⬆️ v1.8.6 ⬆️ 2 anni fa
errors.go ADD EVERYTHING TO TEMPLATES FILE OH YEAH 3 anni fa
funcmap.go Play Time 1 anno fa
gulpfile.js make dark site a real setting instead of an easter egg 2 anni fa
helpers.go pass valid context to Exchange code 2 anni fa
irc.go ADD EVERYTHING TO TEMPLATES FILE OH YEAH 3 anni fa
loadchangelog.go Support for new changelog format 1 anno fa
localisation.go Make website show localised text 3 anni fa
login.go ADD EVERYTHING TO TEMPLATES FILE OH YEAH 3 anni fa
main.go require license to be agreed before starting hanayo 2 anni fa
messages.go Add messages system (for {error,success,info,...} messages) 4 anni fa
oauth.go Add X-Frame-Options: deny to OAuth token requests 3 anni fa
package.json Start implementing localisation in JavaScript 3 anni fa
profbackground.go Slight increase of 13% of profile background quality 3 anni fa
profile.go ADD EVERYTHING TO TEMPLATES FILE OH YEAH 3 anni fa
pw.go Create token revocation page 3 anni fa
rate_limiter.go use getContext instead of MustGet("context").(context) 3 anni fa
recovery.go Update vendor 3 anni fa
register.go Don't add user to leaderboard when they register 3 anni fa
semantic.json Display achievements on user profiles 2 anni fa
sessions.go Make Language set in the Context, not by the template 3 anni fa
simple.go ADD EVERYTHING TO TEMPLATES FILE OH YEAH 3 anni fa
startuato_linux.go deploy a specific branch 3 anni fa
startuato_windows.go When refreshing templates, restart the entire webserver 3 anni fa
templates.go ignore non-html files while loading templates 2 anni fa
tracking.go Move from git.zxq.co to zxq.co 3 anni fa
yarn.lock Start implementing localisation in JavaScript 3 anni fa

README.md

Hanayo build status

This repository has a mirror here. The original repo is still here.

To fellow developers: this is not how you do it!

The biggest flaw of hanayo are that when I set out to create it, I wanted to create a template system that:

  • Created a handler by simply having the file “be there”
  • Could fetch the data it needed on its own, often from the Ripple API
  • Had the actual Go code be as little as possible

This was not immediately evident to me, a Go beginner, but what I did there was basically make Go be PHP.

The biggest lesson I learned on how to properly do templates, was learning to use Vue. Yes, Vue can be used for the frontend and not really for server-rendered stuff, but even just learning how to do stuff with it can help you understand what a template is actually supposed to be in order to be maintainable.

The key concepts and insights for me where:

  • Separating clearly code and markup, making the template declarative and keeping as little code in the template
  • A template should be purely functional. Its mere creation should not generate side effects, nor should it be dependent on things that are not its precise inputs: for a given input there is a specific output.
  • The concept of component as a single self-contained entity which is the same wherever you use it is very powerful.
  • Once a template/component starts becoming too big, split it into more components.

But don't stop here. Actually making a project using Vue helps you to understand this much more easily than using mere words. Go ahead and build something, even if just to play around!