uberswe / beubo

Beubo is a free, simple, and minimal CMS with unlimited extensibility using plugins
MIT License
21 stars 4 forks source link

What is Beubo? #17

Open uberswe opened 5 years ago

uberswe commented 5 years ago

This issue is for brainstorming a description and a slogan for Beubo. Here are some initial thoughts.

Description - Beubo is a free, minimal CMS written in Go which allows users to create anything from a simple blog to a full e-commerce site with millions of users.

Slogan: ?

uberswe commented 4 years ago

At one point I wanted to make Beubo act as a server with automatic SSL but I think it's better to leave that to an existing project like https://github.com/caddyserver/caddy and then make a module to interact with their API or something if needed

uberswe commented 4 years ago

Description attempt 2: Beubo is a free, simple, and minimal CMS with unlimited extensibility using plugins.

uberswe commented 3 years ago

Beubo is similar to https://github.com/asim/nitro

We could consider using Nitro as a base for a lot of areas, especially for plugins that need to talk over RPC or gRPC. Nitro does not aim to be a CMS though so Beubo would still provide this independently.

uberswe commented 3 years ago

Another idea I have is to possibly simplify Beubo to a simple core set of functions. So Beubo itself would be more of a plugin management system which wouldn't even have a http server, it would be cli or config only at it's base. Then you would have a http plugin to run a http server and a html plugin to render templates themes. You could then have an admin plugin which has the http and html plugin as dependencies. However, someone could write their own admin plugin which might be nodejs based for example and only use the http plugin for api endpoints and have no html plugin.

uberswe commented 3 years ago

Another idea I have is to possibly simplify Beubo to a simple core set of functions. So Beubo itself would be more of a plugin management system which wouldn't even have a http server, it would be cli or config only at it's base. Then you would have a http plugin to run a http server and a html plugin to render templates themes. You could then have an admin plugin which has the http and html plugin as dependencies. However, someone could write their own admin plugin which might be nodejs based for example and only use the http plugin for api endpoints and have no html plugin.

Or use the Beubo core with something like fyne to make a desktop app https://github.com/fyne-io/fyne

Any plugins without dependencies could then be used for desktop apps as well.

uberswe commented 3 years ago

Although, making it too flexible might also defeat the point of making Beubo in the first place. Why use Beubo as a base for a game if you could just make all the code from scratch instead of making plugins. If the plugins can be reused for multiple sites or applications it makes sense. Otherwise it's probably better to find a niche such as web development and stick to it.

uberswe commented 3 years ago

Sometimes you just gotta make something and see what people say, let feedback determine what Beubo will turn into 😄