Skip to main content

Oxite - Microsoft's answer to Wordpress

As the year 2009 draws to a close, let us take a look back at a product which Microsoft launched ealier this year as its answer to Wordpress - Oxite.


Oxite is an is an "open source, standards compliant, and extensible content management sample that can run anything from blogs to big web sites." This is how Microsoft describes it. (To see Oxite in action, click here)

Oxite provides you with a strong foundation you can build upon - pingbacks, trackbacks, anonymous or authenticated commenting (with optional moderation), gravatar support, RSS feeds at any page level, support for MetaWebLog API (think Windows Live Writer integration made easy), web admin panel, support for Open Search format allowing users to search your site using their browser's search box, and more - so, you can spend time on designing a great experience.
Oxite is a blog engine based on ASP.NET MVC. So this is basically for developers who know a little bit of .NET framework. One of the biggest argument that I have heard against Oxite is that most web hosting providers have a Linux box which comes pre-loaded with Apache/MySQL/PHP, all free. Many (like www.godaddy.com) provide a complete Wordpress-integrated hosting service. So why should anyone go for Oxite which needs Microsoft software which are not free? This is a myth which I want to break here.

To deploy Oxite, you need a server which supports ASP.NET. If you do a quick search, you will find many providers who provide these services for the same price of a Linux box. Plus if you need Visual Studio, there is a free Express Edition available. If you have ever worked with Visual Studio, you will appreciate its power and ease of use over other rival tools.

Oxite is still not a finished product. It has no install, it has no documentation. If you are a tech enthusiast and like to play around with code, this is for you.

I have put together some links for ready reference -


Let me know about your experience of using Oxite.

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo