BlueInk™ began in late 2005 from ideas gathered from previous projects, problems, and paper sketches. Over the years it grew into a unique and powerful CMS.
Using the current commercial Software-as-a-Service BlueInk CMS as the conceptual prototype, BlueInk is being rewritten into an Open Source CMS built on Apache CouchDB and Cloudant mostly as a CouchApp.
It's a bit rough in here still...but improving!
- copy
config.json.sampletoconfig.json - update it with your settings
- copy
config_ui.json.sampletoconfig_ui.json - update it with your settings
npm installnpm run prosemirrorto build & install ProseMirrornpm run semanticto install Semantic-UI for rework to reworkgulp reworkto "namespace" Semantic-UI under.blueink-uigulp- visit the URL you stored in
config.jsonsans login info plus/_design/blueink/_rewrite/
That should load the home (see home.json) page.
The site contents (content, templates, schemas, the whole shootin' match)
lives in _docs. The BlueInk editing UI and CouchDB views live in
_design/blueink.
The default gulp task will run browserify and push the resulting contents of
the various Design Docs which make up BlueInk to the database you configured.
If you're working with CSS changes you'll need to re-run gulp rework as it is
not (by design) part of the default gulp task. Also npm run semantic can be
used in conjunction with a package.json tweak to update the underlying
Semantic-UI code. If you've made changes to src/semantic/src/theme.config,
you can use npm run styles to rebuild the CSS and then gulp rework.
Note: plans exist in my brain to restructure the top-level gulpfile.js and
leverage Semantic's gulp stuff directly. Patches welcome! 😺
BlueInk on CouchDB is release under the Apache License 2.0