Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration to CMS + New Site #95

Open
nergmada opened this issue Oct 12, 2021 · 1 comment
Open

Migration to CMS + New Site #95

nergmada opened this issue Oct 12, 2021 · 1 comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested

Comments

@nergmada
Copy link
Owner

Hi All,

Firstly thank you so much for your continued interest in this resource, and please accept my apologies for being such a poor steward to it over the 3+ years that the wiki has been available. Particularly, my apologies to those of you who have taken the time to fork this repo, create a PR and fix issues.

That said there are evident flaws in the way this system currently works, and indeed scales. The markdown structure we currently use has a lot of benefits. It, among other things, means that our entire content base can remain free, open-source and available offline. This guide is free and I intend to preserve that as best I can.

However, this makes it much harder to contribute. Forking, editing and pushing content is hard, it's further bottlenecked by my total absence for extended periods where PRs do not get closed. It's not practical to ask experts in this field to spend time going through this process. Conversely, it's inappropriate not to vet content at least for suitability if not for accuracy.

For these reasons, I have taken the time to build a new prototype version of Planning.wiki. Being the ever prepared soul that I am, I happen to also hold the Domain registration for https://aiplanning.wiki and have published an initial example of my vision for this new and improved wiki.

Despite its new frontend, which I intend to make more mobile friendly and suitable for audiences who - like myself - have poor eyesight or other sensory issues, the biggest changes are in how content is created.

This version sits on top of a headless CMS called Strapi (screenshots included for illustrative purposes).

image

This CMS provides a fully interfaced editor and API, allows me to create additional user accounts and is completely integrated with the front end. It is open-source and both the front end and cms can be found on my public repos right now (https://github.com/nergmada/planning-wiki-cms and https://github.com/nergmada/planning-wiki-web).

It's not perfect. It may not be what those who follow this project desire, and if that is the case, I invite you to make that clear here. What is abundantly clear is that I cannot manage this project alone, nor does interest in this project seem to be abating.

Therefore please make your thoughts, opinions, support and ideas known.

Yours Faithfully
-Adam

@nergmada nergmada added help wanted Extra attention is needed good first issue Good for newcomers question Further information is requested labels Oct 12, 2021
@OfficiallySomeGuy
Copy link
Collaborator

Feel some of the issues related to the above could be resolved by adding more maintainers -- you don't need to be so hard on yourself to make yourself responsible for the project alone 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants