-
Notifications
You must be signed in to change notification settings - Fork 19
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
Split website and wiki #167
Comments
Ignoring the comment above which is irrelevant to this issue, I believe this split is complete? |
No, it's not done. We still have a static site on noisebridge.net. We wanted to move the static content to noisebridge.org and put the wiki home page back on noisebridge.net. |
Ah, ok, i misunderstood. The original requirement is "if an organization googles Noisebridge, they find a clean page" not "a static page somewhere". I want to be sure we don't lose focus on that. |
Are we ok to close this issue? |
@rlew631 mentioned this goal to me. I want a CMS that or a way to quickly and easily update from just the web, for the .org site. |
+1 for a static site generator like Hugo or Jekyll; a very hacker-friendly choice. I will also mention Netlify and Vercel as some nice static site generation as-a-service platforms. I think the Vercel free hobby or the Netlify free starter plans might work, but would be limited to a single admin on the web interface, but could allow for unlimited folks to push commits in git that trigger a build-and-deploy workflow. |
Netlify is pretty great. Not sure if we would want to use their actual hosting platform since we want to keep the logs of users visiting the site relatively anonymous. We have a standard web log filter that makes sure to not log too much. |
I want more than just github users to modify it. Although version control also seems essential to me, which most likely means github or another database-backed system. |
There was a proposal to split the website into two sites:
This would bring us back to having useful wiki as a top-level thing. At the same time allowing for a more "professional" site for the organization.
The text was updated successfully, but these errors were encountered: