Roll-out plan for the new Website

[benjagm]

As soon as #45 is completed and #44 merged we should start the new website roll-out plan. This has to be an MVP approach to have it released ASAP and being able to iterate.

The action plan goes as follow:

• Provide planning dates.
• Development completed.
• Current site content freeze.
• Validate no broken links
• Validate no missing content
• Site setup on Cloudflare
• Disable old site pipelines
• CI/CD setup. Github Actions
• Release
• Comms

The dates goes as follows:

1. Close the Landing design: Friday, May 12th
2. Landing Development: From May to Sept 17th
3. Current site content freeze. Sept 25th to Oct 1st
4. Last content checks: Sept 25th to Oct 1st
5. Site setup: Sept 25th to Oct 1st
6. CI/CD setup: Sept 25th to Oct 1st
7. Disable old site pipelines: Sept 25th to Oct 1st
8. Release: Oct 2nd
9. Comms: Oct 2nd

[Julian]

Very minor feedback I see, likely all of which can be ignored/deferred if need be -- obviously feel free to hide this comment / move wherever if here isn't a good spot:

White / inverted links also need at least some hover CSS or something, because it's quite unobvious that they're links, e.g.:

The same sort of applies to the hero buttons to me, a button fill would be nice I suspect, right now all that indicates they're buttons is the hand cursor switch:

At least on dark themed browsers, the favicon is a bit wonky:

In the hero text:

I'm definitely one to usually be careful with claims but here I feel like the caution is probably unneeded, it seems pretty safe to say JSON is the most used format for exchanging data.

The grammar is slightly off there too I think, it seems like it should be "... that allows for JSON ..." or slightly less awkward might be "enables", not sure.

The "learn JSON Schema" button:

seems like the sort of thing an absolute beginner will click, but the first prominent section on that page:

deals with JSON Schema History, which is sort of a weird thing to start with for a beginner IMHO. Perhaps to me would be a bit better to link directly to the "Getting Started" page instead.

The homepage uses the word "trusted" in:

Discover trusted JSON Schema tooling to help your organization leverage the benefits of JSON Schema.

But the implementation page (and common sense :) says:

Listing does not signify a recommendation or endorsement of any kind.

I'd possibly try to reword to not use a word like "trusted".

Also:

Even I don't know what number that 60 million installs refers to! At very least it could use a footnote, but it seems slightly misleading / likely to make someone think JSON Schema is a piece of software. Perhaps, assuming it refers to aggregate installs of tools in the ecosystem, it should just have that extra word or something (and the footnote IMHO).

Also, the headings here look slightly weird to me (too small? or not enough spacing?):

I'd also replace the "Welcome to our Blog" heading which I'm guessing might be from the template, to something more like "The JSON Schema Blog" or "Official Blog" or something.

The typography on the calendar looks off to me too personally:

it doesn't quite look like a "cohesive widget" per se, the body text looks a bit large, dunno.

There's also an extra "the" here:

The Orbit logo somehow looks blurry to me... especially next to the tack-sharp Slack logo. Not sure if that's really the source image that's blurry or if some funny compression artifacts are happening. Screenshot, though might be hard to tell:

Also, the line wrapping on the paragraph above is a bit weird:

and to me there is a tiny bit too much padding between there and the "Sponsors" section above it.

I guess finally (at least for the homepage which is all I flipped through for now), the Code of Conduct links to the OpenJS CoC rather than ours -- that whole footer looks like canned OpenJS footer, but that's a bit confusing. It seems it should link to ours to me.

[benjagm]

This is great feedback @Julian and makes lot of sense. As soon as we are done with the content migration/validation I'll try to implement most for the launch.

[Relequestual]

I've disabled github pages for the repos:
json-schema-org/json-schema-org.github.io
json-schema-org/understanding-json-schema
The blog was run in json-schema-org/blog was run through Cloudflare.

I propose we do the following to sunset these repos.

• Check if anything from the readme's needs to be migrated
• Update the readme from each repo to explain what has happened (maybe just link to a blog post)
• Check each Issue and PR and assess if they should be migrated to the new website repo or be closed.
• Archive each of the three repos mentioned above this list

[benjagm]

I propose we do the following to sunset these repos.

Sounds great to me.

[gregsdennis]

Also, the headings here look slightly weird to me (too small? or not enough spacing?): - @Julian

They're properly space, but they're left-aligned. The middle should be centered, and the right needs to be right aligned.

[gregsdennis]

Also, the line wrapping on the paragraph above is a bit weird: - @Julian

I don't see this wrapping in desktop. Are you on mobile?

[benjagm]

Closed as completed.