Shiohara – Open-Source CMS | Hacker News Reader

Shiohara – Open-Source CMS

github.com

82 pointsalegauss27 comments

We've been building a lot of content systems lately and found Wagtail to be pretty useful (https://wagtail.io/). We build pretty much everything on Django so it's a natural fit for us.

Understanding the models and the way they show up in the admin takes a bit but it's pretty smooth after that, and very programmable. And its built-in API uses DRF, so you can expand on it with that easily. Our frontends are all React-based and it works out very nicely.

Looking at this I kind of checked out once I saw Java, which I'm not inclined to deal with these days. To each their own of course.

I like this specifically because it’s written in Java. To each their own indeed.

Completely fair! Just not the right tool for us & our work.

Java has the fastest Virtual Machine language on the market. In addition, it is possible to use GraalVM, which makes it possible to use several languages.

The Shiohara CMS currently uses Nashorn to create Javascript templates. But it is also compatible with GraalVM and we intend to add more languages supported by GraalVM to create templates.

I have to chime in, as far as open source projects go, the branding is fantastic and feels very refreshing.

Go the website and look at https://shiohara.org/. Top right, there are other projects and they have icons like Period Table of Elements symbols.

Example: https://github.com/openturing, https://viglet.com/turing

On all the projects, you can bounce straight to the release notes. Well organized, you can bounce straight into API docs. And a demo: https://demo.shiohara.org/welcome

Almost feels like Python projects that use Flask-style docs.

Any thing planned to integrate graphql alongside/as an alternative to REST?

Seems like at least two of the projects are just ideas/placeholders though:

https://openbanking.net.br/ with empty repo here: https://github.com/openbanking-net-br/open-banking

https://viglet.com/nakamoto with empty repo here: https://github.com/opennakamoto/nakamoto

IMO it'd be better to just not include them in the header if there is no code or even a TODO list to show yet.

Hi SahAssar,

You are right, I will remove this project from site.

Thanks,

The branding does look nice, but borrows liberally from Adobe.

Adobe borrows from the periodic table. The use of a periodic table was a way of demonstrating how products are integrated. The idea at the time was to show that AI (Artificial Intelligence) that is equal to Aluminium in the periodic table was the integration between products.

https://pbs.twimg.com/media/DDbBTqEXUAEcKii?format=jpg&name=...

Tony thanks for the words! I really liked your comment.

Yes we are creating a set of Rest API and GraphQL to function as Headless CMS

I'm trying to do that Post Types are displayed dynamically in GraphQL. The forecast is that by the middle of the year it will be ready

So I have bit of a use case of having some sort of cataloguing tool.

Essentially I want to create something that can export a row in a table or a item in a JSON array. Where I can have a set of enums and fields.

And then view every with an editor but also be able to upload an MP3, have it, uploaded to backblaze and then the URL put into the field.

I could make some quick web app that does this. But I wonder if a CMS solution would help there?

Hey

You can try out daptin. It is a headless CMS in golang. Except for the "enums" I think it should be able to help you achieve the flow you described.

Daptin has rclone integrated in it, so it can sync with BlackBlaze. Essentially you will need to do the following:

1. Declare one table

2. Make a asset column in that

3. Bind that asset column to a cloud storage(blackblaze here)

4. Daptin will expose assests as urls, but you can choose to write another action to fetch BlackBlaze url and put it in another column

If this sounds too complicated or docs are not enough (which probably would be the case) feel free to create an issue on github and ping on slack. I would be happy to help you out with your first few projects.

[1] https://github.com/daptin/daptin

Recommend adding phonetic pronunciation to the README. In practical terms, being uncertain as to the correct pronunciation is an adoption hurdle.

If it’s like a Japanese word, pronounced “Sheeo Hara” without space. Literal meaning would be “salt flats” but this pronunciation implies a surname (like “McNamara” do)

Hair-uh or harr-uh or -ah?

harr-ah. With short As, and a somewhat Spanish R.

that is right! :-)

Hi, Thanks! I will add the correct pronunciation: Sheeoo Hara in README.md

Anglophones read "oo" as /u:/.

Thanks for the correction

https://en-audio.howtopronounce.com/shiohara-in-us1-voice-71...

Added phonetic pronunciation into https://github.com/ShioharaCMS/shiohara/blob/master/README.m...

Where does the name come from?

It is the name of a great friend named Enrico Shiohara who worked with me at the Vignette Company. But he was in a plane crash

Headless-CMS makes this platform obsolete from the get go. The modern approach of separating responsibilities dictates that a CMS should not handle the rendering of pages, but rather provide a publishing interface and "content-as-a-Service" for whatever frontend/edge-device the site is presented on.

I'm pretty sure there are cases where people don't want to have the modern approach and run two services for it. Having a random CMS taking care of these tasks is good enough for a lot of use cases.

Great! We are creating a set of Rest APIs and GraphQL to also use Shiohara CMS as Headless CMS

Reply on news.ycombinator.com