With v0.4, the AppErgo.com website had its first real public release. It finally existed online, even though it was still very simple and largely perfectible.

Version 0.5 then made it possible to improve the design, revise the content and its organization on the homepage, and further strengthen the site architecture, notably through a clearer internal folder structure. I presented that version in more detail in the article AppErgo v0.5: the project starts taking shape.

With v0.6, the work continues in the same spirit: moving forward step by step, consolidating the foundations laid by v0.5, and preparing the ground for future content and the first AppErgo tools.

Staying on course: a light and fast website

The direction chosen with v0.5 was quite clear: AppErgo had to remain a simple, clean, light and fast website. Version 0.6 therefore continues in that direction, but with more focused work on performance and technical cleanliness.

A major effort was made to reduce loading times, limit the number of requests and keep pages as light as possible. To do this, I used different tools such as Lighthouse, KeyCDN and Uptrends, in order to measure the site’s behavior more precisely depending on the pages, loaded files and geographic locations.

The goal was not only to get good scores, but above all to understand what could still be improved: file weight, number of requested resources, display speed, response time, and the overall behavior of the page while loading.

Lighter pages thanks to minification

Version 0.6 notably introduces HTML and CSS minification. This is not necessarily visible to visitors, but it is the kind of small improvement that helps make a website cleaner and faster.

This minification did require a few precautions. It was not only about reducing file size, but also about doing so without breaking the original code after processing. It was also important to keep human-readable source files, so that the site remains easy to modify and evolve.

Across the whole site, the HTML went from about 742.6 KB to 527.1 KB, a reduction of around 29%. With gzip compression, the actual transfer gain is obviously less spectacular, but it is still useful: less code to load, less code to parse, and therefore a more efficient base.

The homepage was also optimized, with a very small weight despite the presence of several images. These are small improvements, but taken together, they help keep AppErgo fast and pleasant to browse.

Fewer requests, less noise

Beyond file size, I also worked on the number of requests. A website can be light on paper, yet still multiply files, scripts or external resources. With AppErgo, I try instead to keep a sober approach: few files, few dependencies, and only what is really necessary.

This logic fits well with the spirit of the project. If AppErgo is meant to offer simple and efficient software, the website itself must already respect that philosophy: not doing too much, getting to the point, and remaining pleasant to use.

Keeping the code clean

This requirement for clean code had already started with v0.5. Since v0.6 adds new pages, new templates and new sections, it was important to maintain that direction instead of letting the site become more complex with each addition.

I notably used the W3C validator to check pages, fix errors and improve the overall consistency of the HTML. This work is sometimes discreet, even invisible to visitors, but it remains important.

Despite these efforts, a larger cleanup will probably be needed starting with v0.8, especially around templates and CSS. This is already work I had done during v0.5, but successive additions gradually make a new phase of factorization both possible and useful.

The idea will then be to group what can be grouped, simplify some CSS rules, and reduce repetition between the different page templates. This will make the site even lighter, while also helping maintain a consistent design across AppErgo.

Cleaner code makes future changes easier, reduces the risk of errors, and helps keep a healthier foundation over time. This is especially useful because AppErgo is not meant to remain only a small presentation website. It is intended to gradually host articles, software pages, files, versions, and then online tools starting with v0.7.

Icons, manifest and web identity

Another cleanup concerned the site icons: favicons, touch icons and the web app manifest. These are small elements, but they help give the site a more complete and consistent identity across browsers, devices and use cases.

I notably chose not to tick every theoretical checkbox. For example, I prefer keeping small, clean and well-rendered PNG icons rather than adding an SVG favicon if the visual result is less satisfying. A sharp and consistent display is better than a perfect checklist.

The web app manifest also makes more sense in the perspective of AppErgo. The site is not meant to remain only a showcase for downloadable software or a blog with articles: it must also host online tools. Having this base in place now helps prepare that evolution gradually.

New page templates

Version 0.6 also prepares what comes next with new page templates. “Software”, “version” and “file” page templates are ready to be used, in order to present future AppErgo tools and associated files more cleanly. These templates already existed in v0.5, but they were still imperfect and have therefore been greatly improved.

The version pages required more work, because they are more complex. They include several subsections: files, screenshots, FAQ, bugs, and probably other useful information in the future. They will need to clearly present a software’s evolution, the changes made, the available files and important information for users.

Even if all this is not yet fully visible, this step is important: before publishing tools, the pages that will present them must be properly prepared. Tests with a few executable files have already been done internally.

AppErgo Hello: a general rehearsal

Version 0.6 should also see the arrival of a first software project: AppErgo Hello. It is not yet a real user tool, but rather a small test application inspired by the classic “Hello World”.

Its goal is to validate AppErgo’s entire software publishing chain before the arrival of the first real tools. AppErgo Hello will notably be used to test a first simple Windows application, C++ compilation, the creation of a portable executable, the preparation of an installer with Inno Setup, ZIP archives, downloads, SHA256 hashes, as well as the associated publication pages.

It is therefore a kind of general rehearsal. Before publishing truly useful software, I prefer to check that everything works correctly: compilation, installation, uninstallation, available files, visuals, screenshots, Forge, Utilities and Downloads sections.

This project will make it possible to fix technical details without taking risks, with an intentionally simple application that is easy to compile, package, download and replace if necessary. It also marks an important step for AppErgo: the site is gradually moving from a simple showcase to a base capable of hosting real software.

Preparing future AppErgo tools

Version 0.6 is still very focused on web development. There is cleanup, optimization, page templates, structure, articles and, very soon, a first software test project. But all this prepares a more important step: the arrival of the first real AppErgo tools.

The idea remains the same: first build a clean base, then enrich the content, then develop the applications. In short: web first, articles next, tools after.

It may seem slow, but it is intentional. I prefer moving forward gradually, with a healthy structure, rather than publishing too quickly tools that are poorly presented or integrated into a still fragile website.

Conclusion

AppErgo v0.6 may not be the most spectacular version for visitors, but it is an important step for the project. The site becomes lighter, faster, cleaner and better structured.

The direction chosen with v0.5 is therefore maintained with v0.6: building a simple, fast and pleasant website, capable of gradually hosting new articles and, very soon, a first software test project.

Version 0.7 should probably bring more visible new features, especially with the arrival of the first online tools. The following versions will then have a more discreet, but equally important role: consolidating, improving and polishing everything that has been put in place so far, in order to offer a reliable, coherent and pleasant v1 for visitors to consult.