How jmalarcon/miis works
Project type and purpose
• MIIS is a file-based CMS / dynamic static-site-generator hybrid running on IIS or Azure Web Apps.
• It intercepts HTTP requests, parses Markdown/HTML files with front-matter, applies Liquid templates (via MIISdotliquid), and serves rendered HTML on the fly—no database or pre-build step required.
High-level file structure analysis
• Root
• .gitmodules → two Git submodules: IISHelpers (IIS integration helpers) and MIISdotliquid (Liquid engine integration).
• IISHelpers, MIISdotliquid folders
• src/MIISHandler → core HTTP-module / handler, configuration (Web.config), filters, field resolvers, renderer, FMSources interfaces.
• src/Extensions → pluggable extensions:
– Filters (e.g., Concat, Reverse, IfNull, UrlFilters, Where)
– ParamSources (file enumeration, paginator, custom query/cookie param sourcing)
– Tags (e.g., YouTube embed tag)
• src/SampleExtensions → examples of how to build extensions (sample filter, sample param source).
• src/Tests → end-to-end tests, sample templates, sample Markdown content.
• Solution file MIIS.sln glues all projects together.
Key README insights
• .NET Framework 4.5+, IIS URL Rewrite required.
• No DB; caching at file/template level.
• Supports Liquid tags, template inheritance, includes, fragments, dynamic parameters.
• Custom per-folder configuration via Web.config location files.
Main components
a. Client & Browser
b. IIS / Azure Web App
• IIS URL Rewrite module
• IISHelpers integration (module registration, caching hooks)
c. MIIS HTTP Handler / Module (MIISHandler assembly)
• Request pipeline: routing → front-matter resolver → Markdown parser → Renderer
d. MIISdotliquid engine (submodule)
• Template parsing, variable resolution, tag/filter execution
e. Extensions layer (dynamically loaded assemblies)
• Filters, Tags, ParamSources projects
f. File Store (content repository)
• Markdown (.md/.mdh), HTML templates, Web.config per folder, assets
g. Cache subsystem
• Template cache, file cache, folder-tree cache
h. Response output to client
Relationships and data flows
• Handler → reads Web.config and front-matter → loads content file → passes raw Markdown/HTML to parser
• Parser → hands AST to MIISdotliquid → applies templates, includes, tags, filters (from Extensions)
• Renderer → final HTML → cache if enabled → HTTP Response → Browser
Architectural patterns and design principles
• Pipeline pattern in the HTTP request/response flow
• Plugin architecture for filters, tags, param sources (each extension is a separate assembly loaded by convention)
• Separation of concerns:
• Hosting concerns (IISHelpers)
• Core parsing/rendering (MIISHandler + MIISdotliquid)
• Extensions (Filters/Tags/ParamSources)
• Tests and samples kept in separate projects
• Configuration-by-convention with override via folder Web.config
Technologies, frameworks, and libraries
• .NET Framework 4.5+, ASP.NET HTTP Module/Handler
• Liquid templating engine (via MIISdotliquid, itself built on DotLiquid)
• Git submodules for dependency code sharing
• URL Rewrite extension for clean URLs
• C# projects (.csproj), NuGet packages (packages.config)
Detail level
• Assembly/project as its own node if clarity demands (e.g., IISHelpers vs. MIISdotliquid vs. MIISHandler).
• Integration points: “Loads Filters via reflection from ~/Extensions/Filters”, “Reads per-folder configuration from Web.config”.