This is a very basic pluggable site generator I wrote in go to learn a little bit about the language. It's based very heavily off of the functionality of metalsmith since I think it hit a nice minimal level of necessary functionality.
I simplified the structure a bit based off of what I found using metalsmith on a previous project: metadata is gone since I think it's not that useful, also the asynchronicity helping hand of metalsmith is gone since go and javascript are different languages...
An example exists in the creatively named /example folder which can be run and will do very minimal work to the set of files defined in /example/source to move them into /example/destination.
Go seems to have good potential for this kind of build system (although I suspect it has less library support) since it has a strong concurrency model and a focus on speed. It also doesn't lose too many of javascript's strengths since it treats functions as first class citizens and isn't too verbose.
- Benchmarking
- Switch to using a logging framework
- fast filter function using ordered list of files, and indexes on extensions/paths to quickly filter
- Implement mock fileinfo object for each file which can be checked, modify on changing content
- since gosnap is a boundary zone between files as they are seen by a computer and files as they are seen by a browser it should maybe not just have a mock file info object but also have some kind of mock headers that can be read and manipulated
- Plugin parallelism
- Ability to mark files not to be read. They exist in filemap but their content is unusable. Can be copied, renamed, deleted within gosnap. At write phase write them out responsibly to avoid impacting memory with huge files we don't need to process.