----
-layout: post
-title: "cecs"
-tags:
- - cecs
- - c
- - programming
-hero: https://owens.tech/uploads/programming-hero.jpg
-overlay: purple
-published: true
+# cecs
+## cecs is a small, simple entity component system written in c.
----
-cecs is a small, simple entity component system written in c.
-{: .lead}
-<!–-break-–>
The goal of the project is to be small and managable in terms of the actual
code-base itself, as well as to utilise CI via GitHub actions and git best
with the GitHub Flow.
----
-layout: post
-title: "clogs"
-tags:
- - clogs
- - c
- - programming
-hero: https://owens.tech/uploads/programming-hero.jpg
-overlay: purple
-published: true
+# clogs
+## clogs is a thread-safe logger for c programs
----
-clogs is a thread-safe logger for c programs
-{: .lead}
-<!–-break-–>
The goal of clogs is to create a lightweight logging system that is easy to integrate
with other projects. Clogs is designed to be easily integrated with other Make projects,
including the module.mk file will add the clogs sources to the Make SRC variable.
----
-layout: post
-title: "cecse deliberations"
-tags:
- - cecse
- - cecs
- - clogs
- - c
- - programming
-hero: https://owens.tech/uploads/programming-hero.jpg
-overlay: purple
-published: true
-
----
# Deliberations on cecse, the sexy game engine.
-{: .lead}
-<!–-break-–>
Over the past few months, I've been working on [cecse][cecse-gh], a game engine
built on [cecs][cecs-gh].
-<!–-break-–>
+
Overall architecture for this has gone from having seperate git submodules for
cecs and cecse, to bringing cecs in as part of the cecse repo, to seperating out
cecse into a GitHub organisation as I restarted with the intention of a complete