There’s an old writing adage that advises writers, whenever possible, to “show, don’t tell” when bringing characters to life. The goal is to reveal the story through the character’s own experiences instead of the author’s.
Since day 1, I drive all the way from Cavite to UP, Diliman. It’s a 46km-drive and given the traffic condition in Manila, it takes me almost 3 hours each way, every day.
It’s like going to work and to school at the same time – I have my laptop for work and I participate in discussions and exercises.
With a little bit of effort, I am hoping to be an accredited contributor to the design and development of GWT. Eventually, with more training, I could go into training and assisting government branches that need help transitioning their websites to GWT.
While being stuck in traffic, I realized something. We, as the people, tend to complain about subpar quality of services the government provides for us. In some areas, we are sure that we deserve better. In some, we know that we can do better. In general, we exactly know how to solve all the problems our city is facing.
But what are we doing exactly aside from paying our taxes? Our professions are devoted to the private sector – I know, it puts more food on the table but we’ve got to do something towards a direct solution to the same problems that are bugging us.
This is my own way of contributing towards a direct solution to the problems that we are facing when accessing government websites. Now I can complain all I want and shut myself up.
The biggest risk of creating a product is ‘making something no one wants.’
We’re actually using the Government Web Template – fitting in the content of a typical government agency. It sure has a lot of bugs – that’s why we’re here to help as contributors to the repo.
An Active Element is a user interface element that can be interacted with. It’s something you do something on (like click, tap, type on). A very basic example is a text link like this:
Or a button like this:
Also a text input like this: