Cosmic JS Blog Stay tuned for community news, company announcements and updates from the Cosmic JS team.

Three Ways to Use The Cosmic Stack



In last week's article, Tony told us about the ingredients in The Cosmic Stack, why it is so powerful and what its benefits are. Now that we've seen what The Cosmic Stack looks like, let's look at how we can customize our use of it. 

From a high level, you have three basic ways to use The Cosmic Stack. You have flexibility to use just the CMS API, the CMS API and your own app hosted on the Cosmic app server, or the CMS API with a pre-built content-ready app hosted on the Cosmic App Server.


1. Manage Content 

Stack: 

GitHub Repo
Hosting Server
Cosmic JS CMS API

This scenario will require a developer to sync the Cosmic JS API to your website or application. From then on, content managers can syndicate content to their heart's content. We've provided Client libraries to help you easily manage content for your website or app. 


2. Build, Deploy, Host & Manage Content 
Stack:
GitHub repo
Cosmic JS CMS API
Cosmic App Server

This scenario will require a developer to integrate your GitHub account with Cosmic JS & deploy the app. Content managers can get a head start in their dashboard while the dev team polishes the app's code in GitHub. Read more on app deployment and hosting through Cosmic JS. 


3. Deploy & Manage Pre-Built Apps 
Stack: 
Cosmic JS CMS API
Cosmic App Server

This scenario only requires anyone who likes an app and wants to see it online for their business, association or portfolio. Browse our content-ready apps.

The Cosmic Stack is flexible for teams & companies. Build, deploy, host, update, or simply customize your Cosmic Stack to fit your team's needs. We built Cosmic JS for one reason: to simplify the content management stack while making developers and content editors happy by putting content first. Read their testimonials here. 

You may also like


I've been thinking a lot about what makes a great product / UI / feature set.  I've narrowed it down to two words: 

Beautifully easy.

I also keep coming back to the idea of user empathy.  Whenever I hit a road block in trying to do something with Cosmic JS, I make a note of it and try to tear down the road block.  I've noticed that when I come back to the place where the roadblock was and find a nice bridge, I'm a happier user.  And I think in software development that's the highest goal you can attain.


At the request of the Cosmic JS Community, new Multi-Bucket Pricing Tiers are now Available for teams. Introducing, Cosmic Clusters. 

In this tutorial I'm going to show you how to create a simple “ToDo” app using React, Redux, a little bit of Node, and Cosmic JS.

Cosmic JS has an understandable hierarchy for content management and can be used as a stand-alone content organizer while a website is being built. Buckets, Object Types, Metafields and Files can act as a sitemap or content portal for a team wanting to organize information more effectively during the development process.  And when the site is ready for development and launch, the API is ready to begin delivering the pre-populated content saving time and money.

Variety is the spice of life and it is essential to flexible content management.  Currently I'm seeing the trend of data storage move from relational to on-the-fly structures.  Relational databases like MSSQL and MySQL are being less favored and more developers are choosing to move to NoSQL databases like MongoDB.  By more developers I include myself because this is a very flexible and intuitive way to store data.  Key / Value, or as I like to call on-the-fly, content storage is the next stage of content management.  Relational structures bind where on-the-fly sets free.  This is the theory behind Cosmic JS metafields.

Content items are like people in that they come in all shapes, sizes and colors.  Cosmic JS objects allow you to create metafields which give you the power to add on-the-fly key / value pairs.  Create infinite metafields and drag and drop them into parent / child relationships. 

I find it so much easier to keep track of my key / value pairs per object rather than managing a relational schema.  I believe this is the new way of on-the-fly content management that will allow for flexibility and scalability of future content.

We're excited to announce a new way to collaborate with your team on your digital projects. Introducing Workspaces.