golang type aliases for documentation purposes

Question

Is it considered good practice to use type aliases to make go code more self documenting? An example:

type User struct {
    // user stuff
}

type Username =