Show HN: Contentlab – Run a GraphQL Content Management API on Top of Git

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
  • graphql-api

    GraphQL API for the Commitspark CMS (by commitspark)

  • example-code-serverless

  • Hi HN! After working on several larger Content Management System (CMS) integrations, I noticed that existing commercial CMSs suffer from workflow issues that are similar to developing software in a team without using a version control system. This is because today's CMSs typically rely on a shared folder-like approach, where editors work in a single shared space and then publish content to production “file by file”.

    However, as software development and content management essentially share the same workflows (create -> iterate -> release/publish -> maintain), I started looking for ways to build the usual Create, Read, Update, Delete CMS APIs on top of Git. At the same time, there is a market trend in ecommerce away from using large systems that do many things to architectures consisting of smaller systems that are easier to maintain and integrate ("composable commerce").

    I can address both of these aspects with Contentlab (https://github.com/contentlab-sh/contentlab):

    It is an Open Source library I developed to generate and run a GraphQL content management API on the fly, exclusively from data in a Git repository. This enables content to be stored and managed with all Git features (branching, merging, immutability, etc.) and should allow for vastly improved editing workflows. By stripping out all non-essential features like user management and an editing UI, I think the library also fits really well into "composable" architectures.

    Functionality and code quality is not yet where I want it to be but it is working well enough to power my own website.

    A really simple example application using Contentlab is at https://github.com/contentlab-sh/example-code-serverless and an example content model for a multilanguage website is at https://github.com/contentlab-sh/example-content-multilangua...

    I appreciate any feedback and absolutely encourage questions. Thanks!

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • example-content-website

    Commitspark example content for a component-based website

  • Hi HN! After working on several larger Content Management System (CMS) integrations, I noticed that existing commercial CMSs suffer from workflow issues that are similar to developing software in a team without using a version control system. This is because today's CMSs typically rely on a shared folder-like approach, where editors work in a single shared space and then publish content to production “file by file”.

    However, as software development and content management essentially share the same workflows (create -> iterate -> release/publish -> maintain), I started looking for ways to build the usual Create, Read, Update, Delete CMS APIs on top of Git. At the same time, there is a market trend in ecommerce away from using large systems that do many things to architectures consisting of smaller systems that are easier to maintain and integrate ("composable commerce").

    I can address both of these aspects with Contentlab (https://github.com/contentlab-sh/contentlab):

    It is an Open Source library I developed to generate and run a GraphQL content management API on the fly, exclusively from data in a Git repository. This enables content to be stored and managed with all Git features (branching, merging, immutability, etc.) and should allow for vastly improved editing workflows. By stripping out all non-essential features like user management and an editing UI, I think the library also fits really well into "composable" architectures.

    Functionality and code quality is not yet where I want it to be but it is working well enough to power my own website.

    A really simple example application using Contentlab is at https://github.com/contentlab-sh/example-code-serverless and an example content model for a multilanguage website is at https://github.com/contentlab-sh/example-content-multilangua...

    I appreciate any feedback and absolutely encourage questions. Thanks!

  • Hi HN! After working on several larger Content Management System (CMS) integrations, I noticed that existing commercial CMSs suffer from workflow issues that are similar to developing software in a team without using a version control system. This is because today's CMSs typically rely on a shared folder-like approach, where editors work in a single shared space and then publish content to production “file by file”.

    However, as software development and content management essentially share the same workflows (create -> iterate -> release/publish -> maintain), I started looking for ways to build the usual Create, Read, Update, Delete CMS APIs on top of Git. At the same time, there is a market trend in ecommerce away from using large systems that do many things to architectures consisting of smaller systems that are easier to maintain and integrate ("composable commerce").

    I can address both of these aspects with Contentlab (https://github.com/contentlab-sh/contentlab):

    It is an Open Source library I developed to generate and run a GraphQL content management API on the fly, exclusively from data in a Git repository. This enables content to be stored and managed with all Git features (branching, merging, immutability, etc.) and should allow for vastly improved editing workflows. By stripping out all non-essential features like user management and an editing UI, I think the library also fits really well into "composable" architectures.

    Functionality and code quality is not yet where I want it to be but it is working well enough to power my own website.

    A really simple example application using Contentlab is at https://github.com/contentlab-sh/example-code-serverless and an example content model for a multilanguage website is at https://github.com/contentlab-sh/example-content-multilangua...

    I appreciate any feedback and absolutely encourage questions. Thanks!

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • How about a JSON Resume web component with configurable microdata?

    3 projects | dev.to | 17 May 2024
  • DeepNotes – open-source, end-to-end encrypted note-taking and realtime collab

    2 projects | news.ycombinator.com | 17 May 2024
  • HugeMCE forks the last TinyMCE MIT license

    2 projects | news.ycombinator.com | 17 May 2024
  • Show HN: I built an open-source answer engine that runs local LLMs

    2 projects | news.ycombinator.com | 17 May 2024
  • I built an answer engine that runs local LLMs

    1 project | news.ycombinator.com | 17 May 2024