Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I’m building open-source headless CMS for technical content

vrite.io

Post reply on HN
Print view View original

11–20 of 54 posts

Re: Show HN: I’m building open-source headless CMS for technical content

#11

Post by arek_nawo »

michaelbuckbee wrote: post #8

I like the approach you've taken here where it's more of the complete content production and publishing service. Two things I couldn't really sort out from your docs or the site: 1. Is there support for uploading images? How is that handled? 2. Is there support for "table" data. An example: I'd like to have my headless CMS keep a list of conferences with fields for start_date, end_date and other attributes and then r…

1. Yes - currently it's just basic upload but I'm working on better asset management and optimization. 2. I don't quite understand your use-case, but: a) You can save any custom JSON metadata to an article; b) Tables in the actual content aren't supported yet;

Re: Show HN: I’m building open-source headless CMS for technical content

#14

Post by jasonlotito »

masukomi wrote: post #12

I'm .... confused. What's "headless" about it? It's got a GUI. Headless means "no GUI" or.. no visible "head". hugo, jekyll and most static blogs are "headless" CMSs. This is very explicitly setting itself apart from those by HAVING a "head".

From the Post:

"I tried to combine what can be seen as 3 separate products into one: - WYSIWYG editor (with the addition of code-specific tooling like code editor or formatter) - Kanban dashboard (inspired by my experience of tools like Trello used in larger technical content teams to manage content production process) - The actual headless CMS (content delivery via API, integrations, etc.)"

Read the last part.

Re: Show HN: I’m building open-source headless CMS for technical content

#15

Post by arek_nawo »

masukomi wrote: post #12

I'm .... confused. What's "headless" about it? It's got a GUI. Headless means "no GUI" or.. no visible "head". hugo, jekyll and most static blogs are "headless" CMSs. This is very explicitly setting itself apart from those by HAVING a "head".

Hugo, Jekyll, etc. are Static Site Generators (SSGs) Content Management Systems are likes of WordPress, Ghost, Contentful and Strapi - they help you create and manage content. From those, headless CMSs form a distinct group, which only provide a dashboard for you to manage and create content with, but no built-in frontend. Instead you have to use API and other means to create your own frontend based on the content from CMS.

Re: Show HN: I’m building open-source headless CMS for technical content

#16

Post by j45 »

masukomi wrote: post #12

I'm .... confused. What's "headless" about it? It's got a GUI. Headless means "no GUI" or.. no visible "head". hugo, jekyll and most static blogs are "headless" CMSs. This is very explicitly setting itself apart from those by HAVING a "head".

Headless means the CMS itself is an API.

It can be hard to visualize so people may ask what could this look like?

From there a headless cms can use the api to render the data as a site. It can be static, or dynamic.

Re: Show HN: I’m building open-source headless CMS for technical content

#17

Post by masukomi »

arek_nawo wrote: post #15
masukomi wrote: post #12

I'm .... confused. What's "headless" about it? It's got a GUI. Headless means "no GUI" or.. no visible "head". hugo, jekyll and most static blogs are "headless" CMSs. This is very explicitly setting itself apart from those by HAVING a "head".

Hugo, Jekyll, etc. are Static Site Generators (SSGs) Content Management Systems are likes of WordPress, Ghost, Contentful and Strapi - they help you create and manage content. From those, headless CMSs form a distinct group, which only provide a dashboard for you to manage and create content with, but no built-in frontend. Instead you have to use API and other means to create your own frontend based on the content fr…

but this DOESN'T "only provide a dashboard" or api. this SPECIFICALLY provides a GUI to manage it.

your definition makes sense to me, but since this has a GUI it doesn't fall into that definition.

Re: Show HN: I’m building open-source headless CMS for technical content

#18

Post by j45 »

creshal wrote: post #4

> I always had to move back an forth between different editors Yeah, that sucks, it's much easier when you can do everything in VSCode/emacs/vim and don't have to leave your dev environment to write about what you're developing… > WYSIWYG editor (with the addition of code-specific tooling like code editor or formatter) …wait, what? > Kanban dashboard (inspired by my experience of tools like Trello used in larger tech…

Some content tools have to be for the many and not the few.

Technical writing for example is very regularly done by non technical people who are very astute with processes, steps, input and output parameters. Kind of like a power user who can also simplify and explain.

Writing things only for a personal kanban or notebook makes it harder to invite, request or actively have some collaboration. I’m increasingly using the kanban in gitlab for this reason - there are decent enough mobile apps, and it’s ready and actionable.

Re: Show HN: I’m building open-source headless CMS for technical content

#19

Post by masukomi »

j45 wrote: post #16
masukomi wrote: post #12

I'm .... confused. What's "headless" about it? It's got a GUI. Headless means "no GUI" or.. no visible "head". hugo, jekyll and most static blogs are "headless" CMSs. This is very explicitly setting itself apart from those by HAVING a "head".

Headless means the CMS itself is an API. It can be hard to visualize so people may ask what could this look like? From there a headless cms can use the api to render the data as a site. It can be static, or dynamic.

but it specifically has a GUI. It touts the features of its GUI.

Like... i feel like i'm not understanding something obvious. I get the idea of an API only server. I've written many. BUT by shipping a GUI (as part of it or separately) and then touting the features of that gui for managing the CMS they're no longer talking about a "headless" thing. They're talking about a GUI that may talk to a "headless" cms but the entire point of the GUI is to get around the "headless" part.

Post reply on HN