A society initiative to circulate information about health facilities and devices for COVID-19.
The purpose of this website is to republish publicly accessible Google Docs to be more mobile-friendly and performant.
Why using Google Docs?
We are using Google Docs so that our content contributors can collaborate easily without the hassle of conventional CMSes.
What we're striving for:
Our website must be high-performant because our audience is spread across Indonesia with varying types of devices and network speed. A good measurement of it is Google's Core Web Vitals.
Our website must be accessible so that we can reach more users and help more people.
Any information posted on our website must be up-to-date to the latest version that our content editors published. We can tolerate delays to a certain degree for the sake of web performance, but it should be limited to less than an hour.
Software development is complex, cognitive work. The simpler we can make something, then generally the easier it is to do. Similarly, the less amount of moving parts a software component has, the less prone it is to errors, and the less maintenance burden it gives us.
One of the simplest ways to reduce complexity is to reduce the scope. We can often postpone the less valuable parts of a large issue and do them later in order to get the most valuable parts into our user's hands faster.
What we're going against:
We can't afford to hurt web performance or to provide outdated information just for the sake of the beauty of the website.
We must carefully consider any additional client-side libraries that we include on the website. Unless its benefits outweigh the trade-off that we have to pay, we should avoid adding the functionality. Even if it is proven to be beneficial, we should strive to implement it in the best possible way. An excellent example of it is Google Analytics.
For any improvements on the website, we should continuously measure its impact on the Core Web Vitals. If proven to hurt the metrics, we should revert the changes and find another way to implement them without degrading the performance.
In general, these are three guidelines that we need to pay attention to:
Please ensure that all queries and assertions in your test files comply with those testing guidelines.
To get started running the project locally, please follow the steps below.
First, clone the repository.
git clone https://github.com/kawalcovid19/wargabantuwarga.com.gitThen, install dependencies and fetch data to your local machine. Note that we use Yarn, not npm.
cd wargabantuwarga.com
yarn install
yarn mirror-boxFinally, run the development server.
yarn devOpen http://localhost:3000 with your browser to see the result.
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
- Measure Web Performance
- Measure Web Security
- Convert .ico
- Tailwind CSS
- Tailwind UI
- Testing Playground
Special thanks goes to our supporters.
See our contribution guidelines in these languages:
When contributing to our project, please use English when communicating with other people in issues and/or pull requests. Click here to read why. (Bahasa Indonesia)
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!