brigadecore / brigade-www Goto Github PK

Looks like this is the CosmosDB logo. This example used to read "Updated a CosmosDB database." When the text was changed, the icon was not.

We could either correct the icon or consider using an altogether different example.

Notice from Netlify

After November 15, 2022, builds for this site will fail unless you update the build image.

As reported via deploy logs:

DEPRECATION NOTICE: Builds using the Xenial build image will fail after November 15th, 2022.

The build image for this site uses Ubuntu 16.04 Xenial Xerus, which is no longer supported.
All Netlify builds using the Xenial build image will begin failing in the week of November 15th, 2022.

To avoid service disruption, please select a newer build image at the following link:
https://app.netlify.com/sites/etcd/settings/deploys#build-image-selection

For more details, visit the build image migration guide:
https://answers.netlify.com/t/please-read-end-of-support-for-xenial-build-image-everything-you-need-to-know/68239

Experience is showing this is a better way to configure things than the Netlify UI.

The build command for this site is parcel build index.html.

Do we wish to continue hosting the main landing page for brigade.sh in this separate repo? Note that all of the official documentation is in brigadecore/brigade and the blog site at brigadecore/blog. Perhaps we like the flexibility of keeping the material in this repo separate. I can also see folding the material in this repo into brigadecore/brigade itself.

For what it's worth, I don't see anything problematic with the current approach, just wanted to pose the question.

Thoughts @flynnduism @krancour ?

One of my monitors is in portrait mode, and it can't really be used to read the Brigade docs, as it's rendered as shown below:

It would be great if this was fixed, and maybe if the navigation on the left was hidden under a button or something for narrow screens.

By the way, the new docs theme is AWESOME!
Thanks!

cc @flynnduism

As mentioned by Radu in #55, we should use a highlighter library like hljs to improve the appearance of code blocks shown on the website

Update both URLs:
"Re-design" https://github.com/brigadecore/brigade/tree/master/2.0-PROPOSAL (update to https://github.com/brigadecore/brigade/tree/v1/2.0-PROPOSAL)
"Brigade 2 documentation" https://v2--brigade-docs.netlify.app/intro/quickstart (update to https://docs.brigade.sh/intro/quickstart/)

Like the rest of the brigadecore repos, we need to rename the default branch from master to main.

Note that the site currently publishes via GH pages which is set to master, so there may be a few details in addition to just renaming. cc @flynnduism to check my understanding here.

For some time now, https://slack.brigade.sh has redirected users to our Slack channel. If you're not signed into Slack in your browser, you see this:

For those of us very familiar with the project, this isn't confusing. We know that our Slack channel is part of the Kubernetes Slack workspace, but for people very new to the project who lack that context, this is like running into a brick wall -- probably in part because there's nothing on that page that tells you how to get an invite to the Kubernetes workspace. That's over at http://slack.kubernetes.io. This has tripped up at least three people (that I know of) in the past week alone.

What I'd like to do is develop a simple, static page that https://slack.brigade.sh can be pointed to in the future and this page can succinctly explain that you need to join the Kubernetes workspace and then join our channel. We can have links to get your Kubernetes workspace invite as well as the link directly to our channel.

I think we can also make the link to our channel open in the Slack client instead of the web browser, if you have it installed.

I can't see much point in deploying a whole separate site for slack.brigade.sh. Instead, I propose adding a second static page to this site, and it will live at https://brigade.sh/slack. I can update Azure Front Door configuration to redirect request from https://slack.brigade.sh to https://brigade.sh/slack.

Any thoughts, questions, concerns from @vdice or @flynnduism ?

On the brigade homepage you'll find the draft icon on the bottom and a link to it. But, the project has been archived. Should it be removed from the homepage?

Contributes to:

• brigadecore/brigade#1983

Tasks:

• Update project's CNCF-status on the homepage to be archived - #91
• Add a banner announcing that the project is now in archived status - #91
• Add a "banner" to the README - #92

/assign @chalin

I encounter a variety of issue when following the directions on my Mac. I don't know if it's all Macs or specific to my system because of varying versions of different native tools, etc. from homebrew...

Currently, I succeed on hacking on this site by doing so from within a Node 16 container like so:

$ docker run -it -p 1234:1234 -v $(pwd):/src -w /src node:16 bash

I also run into issues if I use Node 18.

I'll update the issue with specific logs next time they pop up, but I just didn't want to lose track of this.

@flynnduism @vdice I think the two of you had been collaborating in the v2 branch (@flynnduism on design and @vdice on content) on a refreshed version of the site. Glancing at it, it looks like maybe it's not quite done yet. Just wondering about status and what we need to do to get it across the finish line. We're at risk right now of the site refresh blocking the v2 release.

It would be really handy to get URLs like this - https://docs.brigade.sh/topics/storage/#azure-file-setup - directly from clicking the section.

Update the site/text/assets per Brigade v2.

Not sure if we want to create a v2 branch for this repo (similar to the approach taken by brigadecore/brigade) or if we just stage a PR with updates. Assume we'd want the updated site to launch/deploy in tandem with the forthcoming v2.0 release.

The most pertinent areas to address (may be others):

• General text
• Images/text showing Brigade scripts
• Image(s)/text showing install steps
• Remove mention of Kashti; replace w/ something else
• Updated logos/assets (?) cc @flynnduism

See also brigadecore/brigade#1508 which tracks updating the docs for https://docs.brigade.sh

This issue formally invites existing maintainers to vote on adding Ronan Flynn-Curran (@flynnduism) as a maintainer specifically on the brigadecore/brigade-www project.

Ronan has already been acting in the capacity of repo maintainer for brigadecore/brigade-www for some time, so this issue is a matter of formality.

If his nomination is ratified, he would be added to the www-maintainers group in this org. That group is already listed as a CODEOWNER for this repository.

We do not have a formally defined method of voting in new candidates but the guidelines require that we have a majority vote. The current list of eligible voters include: @technosophos @adamreese @mumoshu @vdice @radu-matei @lukepatrick @krancour.

The vote will be opened until Oct 26, 2021 or until at least 4 voters approve.

To vote, simply add a +1 comment or statement on this issue.