noisebridge / infrastructure

The Noisebridge Infrastucture
GNU General Public License v3.0
29 stars 19 forks source link

Split website and wiki #167

Open SuperQ opened 5 years ago

SuperQ commented 5 years ago

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.

marcidy commented 5 years ago

Ignoring the comment above which is irrelevant to this issue, I believe this split is complete?

marcidy commented 5 years ago

@rizend @SuperQ sorry, didn't tag anyone, this is done right?

SuperQ commented 5 years ago

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.

marcidy commented 5 years ago

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.

sunjam commented 3 years ago

Are we ok to close this issue?

mcint commented 11 months ago

@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.

SuperQ commented 11 months ago

@mcint What about something like Hugo? We could have a noisebridge.org website repo. People can make quick and easy web updates via github. We can have a GitHub action to publish the hugo site.

jof commented 11 months ago

+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.

SuperQ commented 11 months ago

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.

mcint commented 11 months ago

@mcint What about something like Hugo? We could have a noisebridge.org website repo. People can make quick and easy web updates via github. We can have a GitHub action to publish the hugo site.

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.