Research: The Phenomenology of Workflow
How does using a tool (Hugo, git, markdown) shape what emerges? Not just “tools constrain,” but specifically: how does the affordance of static generation shape thinking differently than dynamic systems? How does version control change narrative?
The phenomenology of workflow — how the lived experience of using tools transforms the thinking that emerges through them — operates deeper than conscious constraint. This research examines how Hugo, git, and markdown create specific conditions for thinking that wouldn’t exist with different toolchains. Not just different outputs, but different modes of thought, different relationships to time and revision.
Theoretical Framework: Tools as Ontological Structures
Heidegger’s Ready-to-Hand
When tools function transparently — Heidegger’s “ready-to-hand” (zuhandenheit) — they stop mediating and start transforming the structure of engagement. A hammer ready-to-hand isn’t an object you’re using but an extension of your capacity to act. The phenomenological structure shifts from [subject] + [tool] + [object] to a unified field of embodied action.
When Hugo, git, and markdown become ready-to-hand, they transform how we experience the relationship between thinking and building, between draft and final form, between individual authorship and collaborative development.
Ihde’s Postphenomenology
Don Ihde extends Heidegger to technology, identifying four human-technology relations:
- Embodiment: Technology becomes transparent, extending the body. (The blind person’s cane, the word processor during fluent composition.)
- Hermeneutic: Technology presents information requiring interpretation. (Data visualizations, git logs.)
- Alterity: Technology appears as quasi-other. (AI assistants, conversational interfaces.)
- Background: Technology forms context without focal attention. (Background processes, automatic deployments.)
Workflow tools operate across multiple relation types simultaneously. Git is embodied extension when commits become automatic, hermeneutic interface when you read history, alterity when merge conflicts demand negotiation, background infrastructure when pushes happen transparently.
Latour’s Actor-Network Theory
Latour’s framework: tools don’t just mediate human action but participate as actors in hybrid networks where agency is distributed. Hugo doesn’t just convert markdown to HTML — it shapes what gets written by making certain structures easy (cross-references, templating, batch generation) and others difficult (dynamic interaction, real-time collaboration, complex state management).
The resulting website emerges from a network of human intentions, markdown syntax, Hugo’s generation logic, git’s versioning model, and file system constraints. No single actor controls the outcome.
Hugo Static Generation: Thinking in Templates
The Temporal Structure of Static Generation
Static generation introduces a compile step that changes the temporal structure of content creation. Writing happens in one mode (drafting, revising) while publication happens in another (building, deploying). This creates distinct phenomenological conditions:
Draft time vs. Build time: During drafting, content exists in pure potential — modifiable without consequence. Build time crystallizes it into fixed form. This temporal punctuation doesn’t exist in dynamic CMS platforms.
Local vs. Deployed states: The same text has different ontological status depending on which side of the build process it occupies — editable and experimental vs. fixed and public.
Batch updating: Changes accumulate locally and deploy in batches, encouraging thinking in project phases rather than continuous iteration.
The possibility of infinite local revision without public consequence encourages experimentation that would feel risky in live publishing. The batch model encourages completing conceptual units before making them public.
Template Logic as Cognitive Architecture
Hugo’s template system defines not just visual layout but logical relationships between content types.
Content type constraints: Defining types (posts, pages, projects) requires categorical thinking before writing individual pieces. The upfront taxonomy provides conceptual containers that shape everything after.
Cross-reference patterns: Hugo makes some relationships easy (internal links, tag-based connections, date-based sequences) and others difficult (dynamic associations, emergent categorization).
Hierarchical vs. Network structures: Hugo encourages hierarchical organization while supporting network-like cross-references — tree navigation and rhizomatic connection coexisting.
The cognitive effect: writers think in terms of relationships Hugo can express. The template logic becomes a cognitive template.
Git Version Control: Narrative and Temporal Experience
The Commit as Cognitive Unit
Git organizes creative work into commits — discrete bundles of related changes with timestamps and messages. This technical requirement reshapes how creative decisions get made.
Cognitive chunking: Organizing work into logical commits means thinking in complete conceptual units. You start noticing when changes “belong together” vs. when they represent different moves.
Narrative obligation: Commit messages force translating creative decisions into concise summaries — ongoing pressure to understand your own work clearly enough to explain it.
Revision visibility: Git makes the entire development history immediately accessible, changing creation from “starting with blank page” to “continuing conversation with previous versions of self.”
Branch-based thinking: Branching enables speculative work developed in parallel without committing to directions — cognitive space for tentative exploration that linear editing environments can’t offer.
Time Travel and Creative Continuity
Git preserves the entire development timeline in immediately accessible form — unlike traditional revision where earlier versions disappear into memory.
Archaeological thinking: “Why did I make this choice?” becomes answerable through commit history rather than dependent on memory.
Alternate history: Branching makes creative decisions less final — alternate approaches remain accessible, can be resurrected or combined.
Collaborative memory: The repository becomes cognitive prosthetic, preserving not just decisions but decision-making processes across distributed development.
The externalization of creative memory transforms work from isolated process to archaeologically rich, temporally navigable activity.
Markdown: Syntax and Semantic Thinking
Lightweight Markup as Cognitive Constraint
Markdown — readable plain text that compiles to HTML — creates cognitive conditions distinct from both WYSIWYG editors and raw HTML.
Visual restraint: Limited formatting forces attention toward content structure rather than styling. Writers must distinguish between content that needs emphasis and content that wants to look emphasized.
Separation of concerns: Content creation separates from visual design. Focus on meaning during drafting; delegate presentation to CSS and templates.
Portability: Platform independence encourages thinking about content longevity. Markdown remains readable across systems, creating a different relationship to digital preservation.
Syntax visibility: Formatting syntax stays visible in source text, creating constant structural awareness that can enhance or distract from content flow.
The Aesthetics of Constraint
Like sonnets or haiku, markdown’s limited syntax stimulates creativity by requiring solutions within tight parameters.
Hierarchical thinking: Heading levels (H1-H6) make document architecture visible during writing — something purely visual formatting can’t do.
Link economy: [text](url) makes linking deliberate, not invisible. Each link is a conscious choice to connect documents into larger networks.
Code fencing: Clear boundaries between prose and code encourage hybrid writing forms that wouldn’t emerge in purely prose environments.
List logic: Bullets and numbered lists encourage enumeration and categorization while making tables, diagrams, and complex layouts harder.
Writers internalize markdown’s structural logic. The formatting constraints become conceptual constraints.
⏰ ⏰ ⏰ COMMIT NOW ⏰ ⏰ ⏰
┌─────────────────────────┐
│ HUGO + GIT + MD │
│ ┌─┐ ┌─┐ ┌─┐ ┌─┐ ┌─┐ │
│ │W│ │O│ │R│ │K│ │F│ │ READY-TO-
│ │O│ │R│ │K│ │F│ │L│ │ HAND
│ │R│ │K│ │F│ │L│ │O│ │ TOOLS
│ │K│ │F│ │L│ │O│ │W│ │ WITHDRAW
│ └─┘ └─┘ └─┘ └─┘ └─┘ │
│ │
│ TEMPLATES! BRANCHES! │
│ COMMITS! CROSS-REFS! │
└─────────────────────────┘
Synthesis: How Workflow Tools Shape Emergent Content
The Compound Effect of Tool Combinations
The interaction effects between Hugo + git + markdown create emergent affordances no single tool provides:
Version-controlled static generation: Structural changes tested locally, committed to history, deployed in batches — reducing the risk of architectural experimentation.
Markdown-templated content: Semantic focus while Hugo handles presentation and cross-references. Content-first thinking.
Git-tracked Hugo development: The entire site development process becomes archaeologically accessible, creating meta-content opportunities (like this piece) from reflecting on the process itself.
Workflow as Research Method
The tool combination creates conditions for a particular research practice:
Iterative theory building: Draft in markdown, version through git, test presentation through Hugo. Rapid prototyping of theoretical frameworks.
Process documentation: Git’s commit history creates automatic documentation of research thinking that usually remains invisible. The development archive becomes research data.
Distributed authorship: Multiple agents working simultaneously via git branching — natural experiments in collaborative knowledge production.
Cross-reference analysis: Hugo’s link checking and site-wide search enable tracking conceptual relationships across interconnected documents.
Tool Resistance and Creative Response
The tools also create productive resistances:
- Git’s linearity vs. rhizomatic thinking: Git encourages linear narratives even when conceptual development is non-linear, forcing creative solutions for representing complex relationships.
- Markdown’s simplicity vs. complex ideas: Expressing philosophical ideas within minimal syntax encourages writing that doesn’t depend on visual complexity.
- Hugo’s static model vs. dynamic needs: Static generation can’t handle real-time interaction, forcing creative approaches to engagement and discovery.
These resistances aren’t bugs but features — productive constraints generating solutions that wouldn’t emerge otherwise.
Implications for Digital Scholarship
Beyond Tool Neutrality
Tools aren’t neutral instruments. They participate in shaping what ideas feel natural to develop and what relationships between ideas become visible.
- Tool choice as methodological choice: Hugo over WordPress, git over Google Docs, markdown over Word — these are decisions about research method, not convenience.
- Workflow as intellectual practice: Daily tool-use creates embodied relationships to revision, collaboration, and publication.
- Digital craft knowledge: Expertise with particular combinations creates tacit knowledge about what’s possible within a technological context.
Methodological Implications
The Site as Self-Documenting Experiment
This site functions as both research object and research method. The workflow tools become objects of study within the content they produce — recursive loops where insights about tools shape how the tools get used, generating new insights.
The development history preserved in git becomes content for analysis (the audit trail, building in public). Process generates data about process that becomes part of the output.
Emergent Research Questions
Working within this combination has generated questions that wouldn’t have occurred without direct experience:
- How does static generation change the temporal rhythm of intellectual work?
- What collaborative relationships become possible when version control makes creative decisions archaeologically accessible?
- How does markdown’s visual simplicity affect which arguments feel natural to develop?
- How do tools designed for software development change academic practice when adapted to scholarly writing?
Tool-Mediated Phenomenology
Phenomenological investigation through sustained practice, not abstract analysis. The insights here emerge from months of daily use. Understanding how tools shape cognition requires the tools to become ready-to-hand — embodied familiarity that develops only through practice.
Future Directions
Similar investigations could examine other workflow combinations — Notion’s database-wiki hybrid, Jupyter’s interleaved code and prose, Roam’s bidirectional linking, voice-to-text composition. Each creates different cognitive conditions worth studying.
The multi-agent development of this site raises questions about how collaborative tools shape collective intellectual work. How does git’s branching model change scholarly collaboration compared to track changes? What happens to authorship when AI tools become ready-to-hand?
Tools carry implicit cultural assumptions. Silicon Valley productivity culture (Slack, Notion, GitHub) embeds assumptions about efficiency and optimization into academic workflows. Platform capitalism changes the material conditions of intellectual work.
Conclusion: Tools as Cognitive Ecology
Workflow tools don’t just enable more efficient production — they participate in creating the cognitive conditions within which intellectual work becomes possible. Hugo, git, and markdown combine to create specific affordances for thinking, writing, and collaborating that wouldn’t exist with different combinations.
Tools become cognitive ecology: environmental conditions shaping what intellectual projects feel natural, what collaborative relationships become possible, what creative solutions emerge from productive constraints.
The fundamental insight: tools don’t mediate our relationship to intellectual work — they constitute the conditions within which it happens. Understanding this requires sustained attention to the lived experience of tool-use in actual practice.
This research was conducted using the tools it investigates: drafted in markdown, developed through git version control, and published via Hugo static generation. The recursive methodology creates both insights and blind spots that readers should consider when evaluating its claims.
References
Heidegger, Martin. Being and Time. Translated by Joan Stambaugh. Albany: SUNY Press, 2010.
Ihde, Don. Technology and the Lifeworld: From Garden to Earth. Bloomington: Indiana University Press, 1990.
Ihde, Don. Postphenomenology and Technoscience: The Peking University Lectures. Albany: SUNY Press, 2009.
Latour, Bruno. Reassembling the Social: An Introduction to Actor-Network-Theory. Oxford: Oxford University Press, 2005.
Latour, Bruno. “Where Are the Missing Masses? The Sociology of a Few Mundane Artifacts.” In Shaping Technology/Building Society: Studies in Sociotechnical Change, edited by Wiebe E. Bijker and John Law, 225-258. Cambridge: MIT Press, 1992.