jamstack-cms

jamstack-cms copied to clipboard

I don't know if this is meant to be intentional or not, but the name is just awful. I fear that it will lead new developers learning about the JAMStack to think this is the defacto option for the JAMStack. And personally, trying to become popular by piggybacking off the name of an existing technology or architecture type to confuse users, just doesn't seem right.

So please, don't try to be intentionally confusing and either stick a disclaimer that this uses JAMStack philosophies and is not 'The JAMStack' or think about changing the name.

Hi @elijah-penney, first of all, thank you for submitting this issue. By bringing this to my attention, I know you are someone who cares and is interested in the community, and in particular the JAMstack community.

I have had similar experiences in different industries that go along with the concern you are showing. For example, I am very active in the GraphQL community. Before the creation of the GraphQL Foundation, companies were branding things like the GraphQL CLI, GraphQL Newsletter, and GraphQL insert thing here that were not open to including participation from outside their niche product. Instead of naming it my company CLI they named it GraphQL CLI, but did not allow outside contributors that competed with their offering. There was even a big dispute because a company actually bought GraphQL.com and linked only back to their site vs giving / making it a true community resource.

As far as JAMstack CMS goes, I initially called this project lit. I demoed it to three people in the community, two of them very involved in the JAMstack ecosystem, and none of them liked the name and asked that I name it something more clear as to what it does. Two of them actually recommended either the name JAMstack CMS or something very close to it.

After giving it some thought, I made the decision to only call it JAMstack CMS if I was going to allow the following:

1. Links back to other CMS offerings in the ecosystem along with a disclaimer / message that this is not the "Official" CMS of the community.
2. Enabling other back end providers to contribute and enable their services as to not only tie it to AWS Amplify
3. Enable agnostic web hook configuration for Netlify + any of the other providers

I still need to get a PR that links to the other CMS offerings in the ecosystem (PRs welcome), and am already on the road to enabling other back end providers.

Finally, I just want to emphasize the name is because I think it is the first actual JAMstack CMS, i.e. it provides the JavaScript, Markup, APIs, authentication, database, etc.. all bundled into a single deployment and is a perfect fit as to what it actually does and accomplishes.

This name made me believe this would be like NetlifyCMS where it can be added to any project, such as a separate React application. However, after looking into this, it looks like it's a full blog website. I'd call it more Amplify Blog with CMS as it is a niche project at the moment and not project agnostic.

Pictures of the actual content editor would be helpful as well. Also, I can find the content but I can't find where the content's schema anywhere. For NetlifyCMS, it is found in /static/admin/config.yml.

Hey @caseykey thanks for the feedback. I'm working on this and the JAMstack ecommerce over the next week, I'll see if I can address some of this.