summaryrefslogtreecommitdiff
path: root/web
AgeCommit message (Collapse)Author
19 hoursSimplify website structure and drop HugoHEADmainxengineering
A static site generator is currently not really required. A static index.html is currently sufficient.
45 hoursweb: Structure index pagexengineering
46 hoursfw: app: Add image signing to Meson buildxengineering
This automates signing the application firmware image for the MCUboot bootloader.
46 hoursfw: sim: Integrate into Meson buildxengineering
This adds a build for the native_sim board of the application firmware to the default Meson build. The resulting Linux binary is also added to the webpage.
47 hoursfw: app: Build with Mesonxengineering
2 daysBuild bootloader and add to websitexengineering
Meson makes this relatively easy. The current approach is nevertheless a bit hacky. For the first attempt it is still way better than CMake ExternalProject.
3 daysweb: Replace file copying by Meson installationxengineering
This makes the build system code way less hacky and more modular.
3 daysDeploy schematic and BOM to websitexengineering
These important design files should be deployed with the website.
3 daysweb: Depend on schematic and bom targetsxengineering
This triggers a website rebuild when schematic files are updated.
3 daysweb: Remove CMakexengineering
Trying meson worked so well that CMake is no longer needed.
5 daysweb: Add simple.css to websitexengineering
This uses meson to copy the simple.css file to the build dir and references the CSS file in the HTML code.
5 daysweb: Add meson build systemxengineering
CMake has some disadvantages when building subprojects like with `ExternalProject`. Furthermore the language is sometimes hard to read, hard to write and not so much appreciated. This is a little test if meson might perform better. If successful this project might switch to meson for all parts except the Zephyr builds.
6 daysweb: Fix dependencies in CMakexengineering
This makes sure incremental builds work properly for the web page.
7 daysweb: Embed into CMake buildxengineering
The website should be part of the regular CMake build for convenience. Later the dependencies might be set up in a way that the site automatically and incrementally updates with a ninja call.
7 daysweb: Add minimal Hugo-based sitexengineering
Hugo [1] is a common static site generator. It should be used to generate a site where build artifacts of this project can be presented and deployed. [1]: https://gohugo.io
7 daysweb: Add CC-BY-SA as LICENSE.txtxengineering
The generated website should contain everything which will be deployed to the user. This site contains material based on multiple licenses to meet the matching domain like software, hardware or documentation. All the content of the website which is not installed from other directories is licensed via the given license. This keeps the usual folder-based licensing scheme for the source repository. Mixing the licenses in the deploy tree seems to be necessary at the moment.