Skip to main content

FsBlog aims to be a blog-aware static site generator, mostly built in F# for .NET and Mono developers. But don't worry, you won't even need to know any F# to get up and running. So long as you are comfortable using a command line or terminal, and have a degree of familiarity with Markdown and Razor syntax - you're already most of the way there! Inpired by the likes of Jekyll and Octopress - and greatly helped along the way by the scripts behind @tomaspetricek's personal website; FsBlog gives the average .NET or Mono dev the tools that they need to get a statically built website up and running quickly and hosted somewhere like Github Pages. This set of tools have been pulled together using some of the following community projects: FAKE for automation and scripting of the different tasks. F# Formatting for Markdown and F# literate programming, processing and colorization. RazorEngine which is used for the templating and embedded C# code. Some of the code in FsBlogLib that calls the RazorEngine has been based on F# code in Tilde. Github Pages for our default theme.

Total Downloads
3.0K
2,956
Published
Mar 7, 2014
Latest stable version

Install

.NET CLI
dotnet add package FsBlog --version 1.0.1-alpha
Package Manager Console
Install-Package FsBlog -Version 1.0.1-alpha
PackageReference
<PackageReference Include="FsBlog" Version="1.0.1-alpha" />

Frameworks

No framework metadata available.

Dependencies

No declared dependencies.

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

This version is marked prerelease. Validate its API and upgrade path before production use.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.