apache / openwhisk-website Goto Github PK

There is an "Imprint" page in the footer nav at the moment.

• Confirm whether or not this page is legally required.
• Write content for the page.

After discussion with @nauerz-ibm and @yumeforever, this page is no longer necessary.

That would be my preference. Might help responsiveness for smaller screens as well. Thoughts?

Options:

• Medium
• Apache blogging platform
• ???

The original site was under the Apache license. I assume that's still valid, but wanted to add it to our launch checklist.

• Add Apache logo
• Add SiteSpirit logo

@yumeforever here are the logo files:

• Adobe_standard_logo_RGB.pdf
• LOGO-SITESPIRIT.ai.zip

Currently blocked by #28. Once we get the content, we need the following from @yumeforever:

• Illustration for section 1
• Illustration for section 2
• Illustration for section 3

(We should update these todos with actual feature/section headlines once we have them.)

Per @yumeforever:

For the question I would use:
links:

text-decoration: none;
color: #29648F;
font-size: 18px;

and no margin on the left
hover:
text-decoration: underline; (I guess)

• Design bottom CTA (@yumeforever)
• Update top CTA button text: "Create Your First Action"
• Link the CTA buttons to https://github.com/openwhisk/openwhisk/blob/master/docs/actions.md

Any instance of "OpenWhisk" in the copy should be updated to "Apache OpenWhisk".

This epic collects all issues related to design for the Dec 8 launch of the site.

• Decide on home page CTA text
• Decide on home page CTA link (https://github.com/openwhisk/openwhisk/tree/master/docs#getting-started-with-openwhisk)

• Choose 10–25 words of praise or review from two reviews
• Provide citation (name, source link, publication)

If possible, it would be great to include an avatar or publication logo. See #21 for discussion about legality of doing so.

• Personas on home page
• All yet-to-be-developed pages

What would this take?

Putting this in the icebox to revisit post-launch.

Should link to https://medium.com/openwhisk

Can we update the page via API?

Even better, could we use OpenWhisk to do this?

Something to think about post-launch.

Should this be the same video from the home page?

This epic collects all development-related issues for the initial release of the site.

• Choose 10–25 words of praise or review from two reviews
• Provide citation (name, source link, publication)

If possible, it would be great to include an avatar or publication logo. @krook @mrutkows who do we need to ask to make sure it's legal to do that?

After launch, we need to make this happen.

• Edit copy for main section.
• Edit copy for Architecture Overview section.
• Swap out video with the one chosen in #27.

This epic collects issues relating to the launch + marketing needs of the new site.

I haven't touched the README from the original OpenWhisk site. Does this need to be updated with Apache branding, new license, etc.?

Initial ideas from @nauerz-ibm:

Serverless computing is already showing its potential to become a game-changer for cloud-native application development.

Are you interested to become part of a strong community & work on a bleeding edge technology?

It does not matter whether you are an application developer, a service integrator or someone keen to help us working on the core engine itself. We welcome everybody willing to help…

If you are an application developer show us what you have already build or what you plan to build with OpenWhisk and we will promote your solution within our community so you can get feedback for free to make your solution even better. We even welcome you to share your rules, actions, and triggers and – in return – benefit from others doing the same preventing people from reinventing the wheel.

If you are a service integrator you should definitely consider enabling your service for OpenWhisk to let it become part of a growing ecosystem. Being part of our ecosystem will make your service more attractive to other developers building OpenWhisk-based serverless & event-driven solutions. This will drive traffic & usage of your service.

If you are an open-source contributor working with us is your chance to learn something new & broaden your skillset. Help us to drive & accelerate the development of this technology. Help us proposing or even adding more cool features. Start participating today - in something that itself has been built upon open technologies like Scala, Docker, Consul, Kafka…

In any case: We are looking forward to hear about your ideas and benefit from your contributions. Join the community and become part of the OpenWhisk game.

Should link to: https://github.com/openwhisk/openwhisk/blob/master/docs/README.md#setting-up-the-openwhisk-cli

We need to review the FAQ Questions and Answers. Bluemix is everywhere and we might want to change.

This is a list of upcoming events where the OpenWhisk team will be, plus a list of past events.

• Design listing of upcoming and past events (@yumeforever)

For now, we can probably stay pretty close to this general layout (but prettier): https://developer.ibm.com/openwhisk/events/

For later, we can discuss combining this with the updates page that @krook and @mrutkows mentioned.

For community updates, discussion, and announcements.

• Choose 10–25 words of praise or review from two reviews
• Provide citation (name, source link, publication)

If possible, it would be great to include an avatar or publication logo. See #21 for discussion about legality of doing so.

• Update main heading and lede (@nauerz-ibm)
• Create illustration for header (@yumeforever)
• Code it all up (@jlengstorf)

It should be clear how content can be added to OpenWhisk social media accounts.

That includes adding the relevant collaboration users to those accounts, or at least defining how content can be suggested to someone with access.

This would include adding videos to YouTube, adding presentations to SlideShare, articles to Medium, etc.

Maybe a FAQ item describes the recommended process?

• Choose 10–25 words of praise or review from two reviews
• Provide citation (name, source link, publication)

If possible, it would be great to include an avatar or publication logo. See #21 for discussion about legality of doing so.

Needs illustration from @yumeforever.

Not needed as discussed in issue #45

• Add "Apache" into the OpenWhisk logo in the top nav

@yumeforever: see the Cordova site for inspiration on this.

Currently we have a placeholder from the OpenWhisk YouTube channel.

• Record a new video to be played on the home page. (@nauerz-ibm)
• Write a script for the video (@nauerz-ibm)
• Add voice-over to the new video (@krook)
• Replace the current video on the home page (@jlengstorf)

• Update content
• Create illustration (@yumeforever)
• Add illustration
• Choose pull quote w/citation and link
• Add use cases

@yumeforever, once you've got the illustration, please add it here and assign this to me. I will knock the rest of these out.

After the initial launch, let's revisit documentation and look at options for making it a more cohesive experience.

Update configuration variables in openwhisk.github.io/bin/develop

Currently blocked by #29. Once we get the content, we need the following from @yumeforever:

• Illustration for section 1
• Illustration for section 2
• Illustration for section 3

(We should update these todos with actual feature/section headlines once we have them.)

This epic collects issues for the Dec 8 relaunch of the site.

This repo has lots of good stuff that each of the personas might like as getting started material: https://github.com/openwhisk/awesome-openwhisk

Integrations won't be ready by Dec 8 launch date, so leaving off for now.

• Write a title that's SEO-friendly
• Write a description that's SEO-friendly
• Add SEO tags for sharing (Google, OpenGraph, Twitter)
• Request Twitter cards verification

• Design where to start animation (@yumeforever)
• Add animation to the home page

I just revisited the About Page with the new informations and realized it was still following the previous color patterns.

First section background color is: #F0F8FD
Last section: #FFFFFF

Following reference:

From @nauerz-ibm:

How about this (pls rephrase a bit, 1st sentence is too long):

OpenWhisk relies on an open ecosystem of services provided by different vendors and falling into
different domains like analytics, cognitive, data, IoT, and mobile. These services represent
powerful building blocks - fostering re-use and avoiding reinventing the wheel, hence accelerating
overall development - providing totally different capabilities developers can make use of to build
compelling serverless event-driven solutions.

Evem better, OpenWhisk provides an open event provider interface that allows it everybody to let
his own service become part of OpenWhisk’s ecosystem to drive traffic & usage.