Awesome Open Source
Awesome Open Source

Mixcore CMS Become a Backer

backer Donate Buy us a coffee

Fully Open Source UI Tools to create multi-purpose Web Apps, Mobile Apps & Application Services

CMS and Dashboards built on top of ASP.Net Core / Dotnet Core, SignalR, Angular.JS and Bootstrap.

Mixcore CMS

Services Result Services Result
Travis CI Build Status AppVeyor CI Build status
Gitter Join the chat at https://gitter.im/mix-core/Lobby Licenses status FOSSA Status
Codefactor CodeFactor Azure Build Status

References

Links
STAG / Demo https://demo.mixcore.org or https://mochahost.demo.mixcore.org/portal (administrator / [email protected]) Ref: How to install Mixcore CMS with Azure Docker Composer
Dev docs https://docs.mixcore.org / https://mixcore.dev
Community https://community.mixcore.org
Youtube https://www.youtube.com/channel/UChqzh6JnC8HBUSQ9AWIcZAw
Twitter https://twitter.com/mixcore_cms
Medium https://medium.com/mixcore

Run with Docker

Latest Docker Image

docker pull mixcore/mix.core:latest
docker run -it --rm -p 5000:80 --name mixcore_cms mixcore/mix.core:latest

Or with Docker Compose

docker-compose build
docker-compose up

GITs clone

mkdir mixcore
cd mixcore

git clone https://github.com/mixcore/mix.core.git

Optional:

Optional steps as those packages are Nuget Library

git clone https://github.com/mixcore/mix.heart.git
git clone https://github.com/mixcore/mix.identity.git

Build & Run with Dotnet SDK

Build & Run Mixcore CMS

REM Make sure you already read and download Dotnet Core SDK here https://dotnet.microsoft.com/download

cd mix.core/src/Mix.Cms.Web

dotnet restore
dotnet build
dotnet run

Modify & Build Portal Front-End source (Optional)

This step is optional and only needed in case you would like to modify the portal front-end code

cd mix.core/src/portal-app

npm install
npm install --global gulp-cli
gulp build

Note: If you facing any System.Data.SqlClient.SqlException error, please replace all content inside "appsettings.json" file with "{}".

Special features (Out of the box)

  • [x] Reliability - Member roles and permissions.
  • [x] High Security - Strong Data Encryption and Security compliance.
  • [x] Multilingual - Flexible multilingual content migration.
  • [x] High Performance - Millisecond response time.
  • [x] Cross Platforms - Powered by .NET Core and run everywhere.
  • [x] Online Coding - Visual Studio Code's heart inside.
  • [x] Customizable Designs - Build any kinds of website.
  • [x] SEO Friendly - No extra plugin required.
  • [x] Media Management - Multiple file formats for your website / application.
  • [x] Manage On The Go - Manage and Code everywhere you want.
  • [x] Easy and Accessible - Non deep tech knowledge required.
  • [x] Analytics - Inside Google Analytics dashboard & no extra plugin required.
  • [x] Dynamic Modular Architecture - Powerful module layers & Attribute sets feature.
  • [x] Extensibility - API-first architecture for Plug & Play.
  • [x] Easy Backup - Powerful 1 step export.
  • [x] More Coffee time! - You can relax and explore more ton of features are not listed here...

UI Screenshots

Default Theme:

Shards UI Kit Shards is a modern design system based on Bootstrap 4 that comes packed with 10 extra custom components and two pre-built landing pages. It’s also lightweight with its stylesheet weighting only ~13kb minified and gzipped.

Mixcore CMS default template with Shards UI Kit

Admin Portal

Mixcore CMS Back-office is built on top of the much awaited Bootstrap 4. This makes starting a new project very simple. It also provides benefits if you are already working on a Bootstrap 4 project.

Mixcore Admin Portal Bootstrap 4.x

Thanks to

This project has been developed using:

License

Mixcore CMS is licensed under the MIT

Permissions Limitations Conditions
✔ Commercial use ✖ Liability ℹ License and copyright notice
✔ Modification ✖ Warranty
✔ Distribution
✔ Private use

FOSSA Status

How to contribute

Fork this repo to your GitHub account, clone it locally and try to follow the following simple guidelines.

  • Never write any code in the master branch
  • When writing code, do it in a specific feature branch
  • Send your pull request from that feature branch
  • After your pull request has been accepted, sync the changes into master from the upstream remote
  • Delete you feature branch
  • Again, NEVER write any code in the master branch ;)
  • Ref: https://datasift.github.io/gitflow/IntroducingGitFlow.html

Get A Weekly Email With Trending Projects For These Topics
No Spam. Unsubscribe easily at any time.
c-sharp (11,959
docker (2,805
angular (1,284
vuejs (1,087
dotnet (868
bootstrap (656
cms (436
dotnet-core (396
vuejs2 (373
pwa (329
ecommerce (216
asp-net-core (189
dotnetcore (180
progressive-web-app (122
forum (103
headless (98
asp (70
headless-cms (55

Find Open Source By Browsing 7,000 Topics Across 59 Categories