servicemeshinterface / smi-spec.io Goto Github PK

The original setup has the front-page content mixed with theme files. Let's separate those in case page-editors aren't familiar with Hugo conventions.

https://github.com/servicemeshinterface/smi-spec.io/tree/master/themes/smi has a number of items which would work better in https://github.com/servicemeshinterface/smi-spec.io/tree/master/content or a static folder at that level.

https://github.com/cncf/foundation/blob/master/website-guidelines.md

Small tidy up issue following #24

Thanks for fixing the layout in #31, @flynnduism! A minor formatting issue remains; the blog index page has truncated text (look at the right margin) at any width:

A blog entry in a moderately sized browser window has very large title text and has the body text cut off on the right margin:

Meanwhile, a narrow viewport for the blog entries looks fine:

This is visible for me both locally and in the PR for the draft blog post at #30.

Here are the updated details - https://github.com/servicemeshinterface/smi-spec#slack

You want to replace deislabs with servicemeshinterface in all github repo links

Description:

The text at Ecosystem & In Partnership sections overlaps the <hr>

Screenshots:

In Partnership Section

Ecosystem

It's exciting to see the work people are doing in this space! In an initial discussion on Cloud Native Slack #smi, we talked about the goal of the blog: to share work happening in the SMI space.

We thought about rules for blog posts:

1. be useful and informative for readers, who won't need to buy specific commercial offerings in order to learn something
2. does not need to exclusively cover open source software, but also should not be primarily product pitches
3. should disclose and link to the employer of the person writing the blog post

Some questions to consider:

1. do we want blog posts to have the usual number of spec reviewers (two)?
2. do we want to specify these reviewers should be from different employers?

These are ecosystem logos for implementations, integrations, etc. Let's get members of the relevant projects to let us know if they want their logos to appear on https://smi-spec.io:

• Consul - @nicholasjackson
• Flagger - @stefanprodan - approved in #7 (comment)
• Istio
• Linkerd - @grampelberg - approved in #20 (comment)
• Maesh - @dtomcej @SantoDE - approved in #20 (comment)
• Meshery - @leecalcote said to include them in #7 (comment)
• Rio - approved by @smw355 in #20 (comment)
• Service Mesh Hub - @ilevine @bettyjunod - approved in #20 (comment)
  SuperGloo

• Add banner to the home page - #70
• Add note to README - #71
• Set repo status to Archived (optional)

Ref.: cncf/techdocs#194

/cc @nate-double-u

SMI Conformance tooling has landed and initial results are being published. A blog post explaining this tooling and conformance report is warranted.

I noticed that tweets linking to this site are using the Hugo default instead of the SMI logo:

https://twitter.com/SMI_spec/status/1248655059627290624

Maybe adding the logo in the right place in the theme would work?

The current link points people to the smi slack channel on the cncf slack org but they have to request to be part of the cncf slack and it's not super clear where to do that. We should add some info on how to join the CNCF slack. here is the link: https://slack.cncf.io/

Issue Description:
The Meshery logo on the smp-spec.io main page has dull colors. This must have occurred during an image resizing.

Proposed Fix:
Upload a fresh copy of the Meshery logo.