Design/implement landing page for beta-site content stubs

[jessicaschilling]

This issue is part of Epic 1A: Launch docs beta.

The new nav structure being designed for the docs beta (see #313) will result in stub pages for which content doesn't yet exist. Until it does, create and implement a common landing page to convey ...

• The content that should be on this page doesn't exist yet, because the site is in beta
• We'd love to work with contributors who would be interested in helping create this content sooner rather than later
• If this missing content is crucial to you, we'd like to know
• If you'd like to be part of collaborating on/testing/creating this content, here's how to join us (likely a link to a Google form or similar contact mechanism)

[ericronne]

I'll start wiring this up. Additionally, we might be able to populate some of these pages with very-rough "starter content" — or at least simple "Click at Own Risk, There Be Demons" — pointers to third-party material, where a user might be able to find help until the content is ready to launch. I've started a hackmd doc to organize information surrounding all NEW content to be created.

NEW IPFS docs content to generate

[jessicaschilling]

Thank you for linking to the related issues!

[cwaring]

A cute (animated) illustration will be the secret ingredient here. Diffuse disappointment with the delight of warm n' fuzzies™

[ericronne]

Here's a somewhat high-fi draft for discussion. Let's discuss the content here, first and foremost. This doesn't represent the design, but i'm curious to hear feedback on the illustration. Time permitting, it would be fun to animate it.

[jessicaschilling]

I love this so much 😄
A few thoughts?

• Under "Other resources", I believe it's "that" rather than "which" (since not preceded by comma)
• Under "Help us write this page", we may want to lead with something that's more explicitly community-powered: "Community contributors are invaluable to making IPFS docs great!" rather than "work with" language? We may also want to be more specific at the end: "... visit this page's GitHub issue and comment with how you'd like to get involved."
• Maybe "Be a docs beta tester" instead of "Be a tester"?
• In the "be a tester" content, the link can go to this form with the text "Sign up now"

More generic question and request:

• I believe all the content here will need to be manually generated (progress "subway map" imagery, related resources, etc). Are we OK to manually support this during the transition period? (My inclination is yes, since it adds a lot of value.)
• Re animation ... using SVG animation to move the bubbles under the pencil-ship around wouldn't be too tough. Also subtle enough to be charming without annoying.
• Would you be amenable to making the pencil-ship pilot a little more gender-neutral?

[ericronne]

Requests sound 👌to me … ☑️

• No specific gender was intended, but made them more masculine.
• The paper animation would be the tricky part. Not sure if those make sense when the rocket is in space, but we can pick up the ani Q later

[jessicaschilling]

@ericronne Thanks!

[jessicaschilling]

We had some input on this page as part of our IPFS Colorado user testing (see #355) and @ericronne is making some minor edits. 😊

[ericronne]

Here's an update with rearrangements and minor copy edits. (Reminder: this doesn't reflect final page design.) Here's the illustration. Animation would be great, but for now, i think it would be more useful to prioritize other issues.

[jessicaschilling]

Awesome! Going to move this one into "blocked" at the moment until we're able to actually develop on it.

[jessicaschilling]

Update: @cwaring is implementing, but needs related items for each stub from @johnnymatthews and @jessicaschilling. These should be stored in front matter -- @cwaring, can you think about pinning the format down exactly? Something like ...

related_items:
"ProtoSchool video tutorial on a thing": https://foo.bar
"Another link title": https://link.here

[jessicaschilling]

@cwaring - this Google sheet should contain all the personalized info you need for each content stub:

• Link to the GitHub issue for readers to track progress
• 3-5 relevant links and their titles

(cc @johnnymatthews - if any content comes to mind that I've left out, please add it!)

[johnnymatthews]

Just ran through that sheet. Nothing is glaringly wrong from my perspective, you know the content better than I do at the point. One thing we should do is mark external links with an external-links-icon.

[jessicaschilling]

@johnnymatthews I believe those external links should all auto-add the external-links icon because VuePress witchery, but @cwaring can confirm?

[ericronne]

@cwaring take with a salt grain if you've already crafted one of your characteristically brilliant solutions, but here's some visual food for thought and discussion among all. For the sake of easy implementation — and Occam's Razor-izing things — I've removed the status bar in favor of a simple text invite to follow the progress on github. …

Personally leaning toward the text-only approach ☝️ for the alt-resources list

[cwaring]

@ericronne thank you, this is great and very similar to what I had in mind :). I'm implementing the visual layout now and after experimenting with the voting options I've settled on a way to merge the functionality with the "was this helpful" widget.

[johnnymatthews]

@ericronne
Personally leaning toward the text-only approach ☝️ for the alt-resources list.

Yeah me to. Not a fan of a bunch of icons in the copy.

[cwaring]

With ipfs/ipfs-docs/pull/28 merged has everything been captured to close/complete this issue?

💁‍♀️Live preview url for your convenience.

[ericronne]

🚀

[jessicaschilling]

Re-opening, because I need to actually implement the content for those landing page stubs.

[jessicaschilling]

Also, two other quick modifications from our sync call - @cwaring, are you still OK to implement these?

• Remove "edit on GitHub" footer content from these pages only
• Interaction logic for the "important?" buttons
• Links for "check status" and "help with this page" (both the same destination, and driven from front matter) need to be a URL rather than a GitHub issue number, because they may refer to issues in other repos This one is fixed in Add related links to content stubs ipfs/ipfs-docs#29

[jessicaschilling]

Closing this issue via ipfs/ipfs-docs#41 😊