GraphQL-First Application Framework and CMS for rapid software development: Serverless, declarative and extensible.
Slicknode is an all-in-one GraphQL backend, gateway and Headless CMS for creating custom backends and digital products with content management. It consist of 3 main components:
Deploy to the managed Slicknode Cloud with a single command (with auto scaling, global GraphQL CDN, serverless infrastructure), or self-host in any data center with any cloud provider.
Links:
Most content management systems are isolated systems. Combining them with your own or 3rd party APIs usually requires extensive knowledge about the CMS architecture and is time consuming. You can do it in the frontend using a headless CMS, but that adds complexity, is limited and has to be done by hand. Exending core functionality, for example as "simple" as adding a stripeCustomerId to the user object, is often hard or impossible. If you need to add custom business logic or need advanced access control, you usually need to write a custom backend, which is time consuming.
On the other hand, there are solutions to create backends with business logic, but they often lack content managment features like localization, non destructive editing of live content (Draft → Review → Published), Admin UI, version history etc.
Slicknode combines both by providing reusable building blocks, a modular architecture and a declarative programming model. An open-source framework to create custom backends and content management infrastructure with minimal code and minimal knowledge, while at the same time providing functionality to extend and customize everything.
Here are some of the problems that Slicknode solves:
This is a quickstart tutorial to create a Slicknode project from scratch. If you would rather start with a fullstack application, check out our NextJS blog starter
To get started with Slicknode, you need a Slicknode Cloud account. You can sign up for free here (No credit card required)
Check out this 10-minute tutorial which walks you through everything you need to get started:
The Slicknode CLI can be installed via the terminal using npm. (How to get npm?)
npm install -g slicknode@latest
To create a new Slicknode project, navigate to the folder where you want to create your new project and run:
slicknode init quickstart-project
# Change into the newly created project directory
cd ./quickstart-project
This will ask for your Slicknode login information when run for the first time. Enter the login information that you used when you signed up.
Modules are the top level building blocks that let you organize your project in a modular way. They allow you to reuse functionality across multiple projects or to share them publicly with the community.
Now, add some builtin modules for content management and image handling to your project:
slicknode module add image content
Then deploy the changes:
slicknode deploy
Your own types will be added in your own modules. To create a blog for example, run:
slicknode module create blog
It will suggest a namespace and the label that will be displayed in the data browser. Just hit enter to use the suggested values for now.
This will create the following file structure in your project folder:
modules/
blog/
slicknode.yml
schema.graphql
slicknode.yml
You can model your schema using the GraphQL SDL.
In your favorite editor, open the file
modules/blog/schema.graphql and enter your schema, for example:
"""
A blog article
"""
type Blog_Article implements Content & Node {
id: ID!
title: String!
image: Image
slug: String! @unique
text: String @input(type: MARKDOWN)
category: Blog_Category
createdAt: DateTime!
lastUpdatedAt: DateTime
# Content interface fields to enable content management
contentNode: ContentNode!
locale: Locale!
status: ContentStatus!
publishedAt: DateTime
publishedBy: User
createdAt: DateTime!
createdBy: User
lastUpdatedAt: DateTime
lastUpdatedBy: User
}
type Blog_Category implements Content & Node {
id: ID!
name: String
slug: String! @unique
# Content interface fields to enable content management
contentNode: ContentNode!
locale: Locale!
status: ContentStatus!
publishedAt: DateTime
publishedBy: User
createdAt: DateTime!
createdBy: User
lastUpdatedAt: DateTime
lastUpdatedBy: User
}
Save the file and check if you have any errors in your project by printing the project status. Run the status command from the project folder:
slicknode status
To deploy the changes to the cloud, simply run:
slicknode deploy
Now you have a production ready content HUB with GraphQL API.
To explore your newly created GraphQL API, open the playground:
slicknode playground
This will open the GraphiQL playground for your API. (It might ask you for your login credentials)
To open the CMS data browser of your project:
slicknode console
Show the GraphQL endpoint that you can use with your GraphQL clients:
slicknode endpoint
Explore the full potential of Slicknode. Here are a few topics that can get you started:
FAQs
GraphQL-First Application Framework and CMS for rapid software development: Serverless, declarative and extensible.
The npm package slicknode receives a total of 31 weekly downloads. As such, slicknode popularity was classified as not popular.
We found that slicknode demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.