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

Split website and wiki #167

Open
SuperQ opened this issue Mar 25, 2019 · 10 comments
Open

Split website and wiki #167

SuperQ opened this issue Mar 25, 2019 · 10 comments

Comments

@SuperQ
Copy link
Collaborator

SuperQ commented Mar 25, 2019

There was a proposal to split the website into two sites:

  • One official static content site.
  • The wiki.

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
Copy link
Contributor

marcidy commented May 8, 2019

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

@marcidy
Copy link
Contributor

marcidy commented May 10, 2019

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

@marcidy marcidy closed this as completed May 10, 2019
@SuperQ
Copy link
Collaborator Author

SuperQ commented May 10, 2019

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.

@SuperQ SuperQ reopened this May 10, 2019
@marcidy
Copy link
Contributor

marcidy commented May 10, 2019

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
Copy link
Contributor

sunjam commented Oct 22, 2021

Are we ok to close this issue?

@mcint
Copy link
Contributor

mcint commented Dec 15, 2023

@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
Copy link
Collaborator Author

SuperQ commented Dec 15, 2023

@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
Copy link
Member

jof commented Dec 15, 2023

+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
Copy link
Collaborator Author

SuperQ commented Dec 15, 2023

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
Copy link
Contributor

mcint commented Dec 15, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@jof @mcint @SuperQ @sunjam @marcidy and others