Create a list of what needs to be done to start showing up in the first page of Google search results by the end of August.

How?

We have a 3-step approach to getting your idea(s) tested in the hands of real people.

1. Understand the problem that needs to be solved and ensure the intended users feel the pain and need for a solution.
2. Prototype the solution and get feedback from real people as fast as possible.
3. Review customer feedback and confirm we are making progress toward solving the problem. If

relates to: #60

http://dwyl.io/

I still cannot access the site...

Might not be too much of an issue in terms of a CSS fix as I think we need to change this picture out pretty quickly. But the issue at the moment is as follows.

1366 x 768px:

1920 x 1080px, cuts off people's heads:

Looks like I have a really fun bug to deal with for #51.

visit: https://www.dwyl.io/images/favicon.ico
tell me what you see.

Incorrect CSS here:

Is causing all of the paragraph text on the page to be grey (color: #616161;).

https://dev.twitter.com/cards/overview

Example implementation on http://www.smashingmagazine.com/

blog.dwyl.io or www.dwyl.io/blog?

@nelsonic Any preferences?

Do we want to have a contact form on our website...?

(Hint: there is a _right answer_ to this question... 😉 )

Hey, you might think this a stupid question but, what exactly is dwyl?

I was thinking about this when doing the keywords used in #41.

My question can also be furthered upon as follows: is dwyl.io the website for your app called time or is it the site for dwyl (which is an organisation of open source contributing developers and designers making things to help them make things if I am right)?

Thanks in advance for answering, I really need this cleared up 😀

To ensure the site works across all devices, particularly Kindle/e-readers.

As a variation, we'll add a temporary panel/section to the website between the email sign up and the dwyl values sections. We need to create the copy for this.

We need to have an even better notion of views opposing #dwyl (given it's our brand) so that we can form a constructive and cohesive set of thoughts on the subject.

This is an interesting piece that should be read for example.

There’s little doubt that “do what you love” (DWYL) is now the unofficial work mantra for our time. The problem is that it leads not to salvation, but to the devaluation of actual work, including the very work it pretends to elevate — and more importantly, the dehumanization of the vast majority of laborers.

While the answer this question might be _obvious_ to most of us with experience, its _not obvious_ to people without technical experience. So we need a post clarifying what this means.

The image #51 (comment) is the _First Impression_ people have of Us. It needs to be a _Great_ one.

We need a collection of logos of companies we have worked with for the site.

• Burberry
• Groupon
• OneFineStay
• Oxfam
• Santander
• CAF

Please add to this list.

Please share your homepage ideas. 💡 😉

We're currently doing basic web tracking.

But see that sidebar? We have to make sure we know it like the back of our hand. #transferableconcepts

HarpJS is total overkill for this site and following some excellent work by @harrygfox as well as the current Founders & Coders cohort, there are plenty of examples out there for future students. We need to go back to simplicity.

So we can create new routes quickly and easily, but still not use a framework.

e.g. /websummit

I'm in favour of having a Question Based Top Navigation

Why? | Who? | What? | How?

Relates to: dwyl/ateam-proposal#13 (comment)

As seen on a screenplay preview of the site on mobile, the site doesn't exactly look good in its current state for responsiveness.

I think simply making the site more responsiveness through the utilisation of media queries for the header and hero/signup area should do as the rest of the site looks pretty fine.

@iteles in case you didn't see it:
https://medium.com/@racheltho/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996

http://www.nytimes.com/2015/06/29/technology/when-a-company-goes-up-for-sale-in-many-cases-so-does-your-personal-data.html
We will never be bought/sold so your data is not going to end up in some mega-corp!

https://twitter.com/nelsonic/status/615799935720554496

So much nerd-love for how @Marak is encouraging people to join the mailing list for hook.io using a curl command ... see: https://github.com/bigcompany/hook.io/tree/60f7525475184d257206165860ef18fbabe94e1a#interested-but-too-busy-to-read-this-now

curl hook.io?[email protected]

@iteles following on from Sebastião's question:
Visiting dwyl.com today
re-directs to http://www.desiringgod.org/ which is http://www.desiringgod.org/about/overview

Sadly, no direct contact info ... http://whois.domaintools.com/dwyl.com

How much more effective is a contact form vs a simple mailto link?

Currently on the website we have 2 places with simple mailto links (and no contact forms).
One on the top right:

And one on the bottom right (both the envelope and the email address itself):

These have never been used.

Of course I suspect that the reason for this is the massive call to action, but it will be interesting to A/B test in future iterations how contact forms work vs mailto links.

Currently if we use Github Pages to host the site for convenience (hooray MVP 🎉), but this posts to dwyl.github.io. We'll need to transfer this to the www.dwyl.io URL.

A collection of places where we can possibly get the word out about dwyl. Added to as we come across new things!

• http://onboarded.co/
• https://makerba.se/

Our logo looks way better on coloured background than on a white background. Need to look at the options for what it could look like on white.

Having our Mandril API key exposed to the world is a terrible way to do things. We need to create a Mandrill endpoint (on Heroku or Firebase?) to fix this and hook the functionality of sending an email into index.html.
The form is already commented out in index.html (ID = #signup https://github.com/dwyl/dwyl.github.io/blob/master/index.html#L56) and will provide a single field so people visiting dwyl.io can enter their email address and have it sent to us.

Is it a good idea to have a separate repo with some information/discussion around emailing people? For example what the appropriate content/frequency would be, better the understanding of the reasons why people sign up to get emails from us, what the alternatives to emailing people are (blog, etc) and complimentary communication methods.
Or maybe a more general repo on communication with people who are interested in dwyl?

@nelsonic Thoughts?

There are a few issues with the website as it stands:

• It doesn't make it clear what we do
• The call to action is murky - what are people actually signing up for?
• It isn't very captivating (you get a feeling of meh when you see it)

Given that we're at the web summit in the next couple of days, this should be our top priority at the moment.

Once we start publishing content as DWYL we should submit our site to: https://github.com/kilimchoi/engineering-blogs

https://atavistinsider.atavist.com/goodbye-native-mobile-apps

https://domainr.com/boredgame.org?q=boredgame

What about?

https://placeit.net/

See: http://aycl.uie.com/

When the site moves out of alpha! https://developers.google.com/analytics/devguides/collection/gajs/

https://twitter.com/amreenaslam/status/637496610629513216 😕
(I clicked on https://twitter.com/hashtag/dwyl and read the first few tweets ....)

We've agreed to use PureCSS for the WebSummit milestone, as discussed here. We will need to debate when we're moving away from PureCSS again after the websummit.

For now, the first task is to move our existing site content into the PureCSS framework so that we can then iterate on it and have a log of all the ways we made it better. Progression screenshots #ftw 👍

Currently looks very odd on bigger screens:

I would love the image to always look like this:

But sadly, on mobile, it does this:

And even worse on tall thin phones:

Then on wide desktop screens:

There HAS to be a better solution that manually testing 20 different break points and photoshopping the image to add more and more image 'padding' to the sides every time the aspect ratio is anything short of 'perfect'. 😣

When we get above 100kb for initial page load, investigate progressively loading the scripts:
https://friendlybit.com/js/lazy-loading-asyncronous-javascript/

Should we collect a list of all the places apps get reviewed for when we get our app out?
e.g: http://www.theguardian.com/technology/2015/aug/14/best-android-apps-games-ninja-jamm-fallout-shelter