Walcron
Loading Shell command...

Welcome to Walcron website

This is a sandbox website for us to explore real-time Web Development.

This sandbox is for real-time testing for web environment and ofcourse to sometimes by-pass coorporate networks for private communication.

Walcron Web Authors
Us in Portugal

What is truely important for Walcron development?

This site was up since 2014 and had many iterations [Learn More of our history] and have evolved from Pure Server Render to Non-Javascript Accessible site.

As of 2024, the importance of Walcron website are:

Reliability

Being a self-maintained site, how do one...
  • "Validate his own changes ?"
  • "Ensure changes doesn't break anything ?"
  • "A hassle to deploy changes ?"
Github workflows
In Walcron we implement GitHub workflow to do our biddings. A full CI/CD:
  • Testing - ensure safety in modification. [GitHub Actions]
  • Integration - API doesn't break. [Smoke and E2E]
  • Release - Deploys ONLY successful pull-request.
Comparing latest image
User Interface verification:
  • Layout verification - Production layout are compared with preview. [Snapshots]
  • Approval workflow - Integrated approval process. [Snapshots]
Code coverage
We up-keep coding standards and security compliance:
  • Coverage - 99.9% lines of code covered.[CodeCov]
  • Linting - Coding checks to ensure proper coding styles.
  • Compliance - Security and Lint checks. [OWASP check and Dependabots]
"So what if something really breaks ?"
Github workflows
In reality this will happen, and there are fallbacks options :
  • Every pull-request is tracked via Release [list of releases] . Checkout the release tag and create a new pull-request.
  • Revert via Vercel, but not applicable to GitHub Pages. Useful for API break changes.

Accessibility and Readability (WCAG)

"Our Homepage can now be browsed WITHOUT JAVASCRIPT!!"

We did it by relying on both PureCSS, Server Side Generation and ensuring non-critical usage for Javascript. The old homepage was Javascript heavy(Parallax Effect) and we encountered performance and accessibility issues.

This site can also be browsed with keyboard and text-readers.

We are going now commited with Web Accessibility; eventhough we are still in the learning phase. The best reliance is to run periodically test with Accessibility Checker and Chrome built-in Lighthouse.

Monitoring
"Ensure what we develop are standard."

As a self-maintained website, it is hard to know what is right. So we start to use tools, such as Google Analytics and Google Search Console to check on general usage to up-keep the standard guidelines.

View Checklists
Performance
Google Page Speed

We use Lighthouse and Google Page Speed to check on our webpage performance. The ultimate goal is to test frequently and keep the page simple.