search

DoESLiverpool / somebody-should

A place to document practices on the wiki and collect issues/suggestions/to-do items for the physical space at DoES Liverpool
31 stars 11 forks source link

The website could look much nicer #19

Closed amcewen closed 5 years ago

amcewen commented 10 years ago

We'd like to update the website, so it does a better job of telling new visitors what we are, and also looks much nicer.

(When we're doing a refresh anyway, it might be a good point to move it onto some hosting that DoES owns - as outlined in issue #18).

From that then prepping a list of features/pages/etc. that we need (the requirements), which can be used by the developer and designer to create the site.

DoESsean commented 9 years ago

Right...

There is a short list of questions and things we need to think about for the website on the whiteboard. Whether or not anyone ever looks at the whiteboard is another matter. People should be adding their own thoughts if they're relevant.

Also, it's worth thinking about the questions and how we want to address them, otherwise we may miss something important when building the site, which would then necessitate a re-jig.

Ideally, I'd like to get moving on this soon, as we've been dragging our feet on it for a couple of months, so will put in a deadline for suggestions, ideas and comments very soon.

zarino commented 9 years ago

Happy to help with this if you need a designer / frontend developer. The DoES site's written in WordPress right?

DoESsean commented 9 years ago

Yes, Zarino, it's a WordPress site, so shouldn't be too much difficulty to glam up a little bit. It's just gathering all the content that will be tricky.

amcewen commented 9 years ago

Should issue #91 go in the requirements list for the website?

It doesn't have to live at status.doesliverpool.com, but should be at an easy to remember URL, and could be on the main site somewhere. However, status.doesliverpool.com would let it sit on different hosting and allow notification of whether http://doesliverpool.com was up or not, in the future... :-s

zarino commented 9 years ago

@amcewen – Looks to me like #91 is a separate ticket. This one is already overly broad, I wouldn't want to add yet more considerations into it. The status page can be thought about completely separately, no?

(See, for example, status.github.com and status.heroku.com, which have completely different styling and markup to their parent sites)

amcewen commented 9 years ago

@DoESsean to audit our existing site(s) to build a list of pages, etc. Then we can have a meeting to work out what we still need, and we'll (I expect) generate a list of additional requirements too (at least to get us moving on it)

jamieisboss commented 8 years ago

@amcewen Nothing happened on this for a long time so I did a bunch of it one day and took photos, I'll finish it soon and then you can not like it and iterate or whatever until you do but you might as well assign this one to me for the time being

skos-ninja commented 8 years ago

Turns out, I can't assign you for some reason

amcewen commented 8 years ago

I think it's because @jamieisboss isn't a member of the @DoESLiverpool organisation - yet. I've just sent him an invite, so assuming he accepts then we'll be able to assign it to him :-)

jamieisboss commented 8 years ago

Hi

jamieisboss commented 8 years ago

Ok, so i have a half done wordpress site somewhere but as decided in #273, it's unneeded overhead, so will use the design, rip out the WP bits and change with a view to being auto-regen html pages.

@amcewen did you take a look at those photos yet? Any that you specifically don't want used? Also i think you said you were getting some back from that photo thing while ago, did you? if so can you pls give me access somehow, removing any you don't want used from the share, and if there's loads, and people like some in particular, you pick 5 now then we can set up some more fair system for people to vote if anyone wants to have a say.

Half the time you end up needing text where the detail is and stuff so it's usually better to get a version going so people can see the restricting factors, then iterate with input that's already been refined by the person inputting IM(nv)HO

I'm going to find that cloud thread to see if the answers o my questions are there before i ask tthem

amcewen commented 8 years ago

Have sent the ones the LEP took over to you, and forwarded the email about the ones you took to the rest of the organisers (they look pretty good to me, and we can always complain about ones you pick and suggest alternatives once they're on a website ;-)

jamieisboss commented 8 years ago

Ok cool, I'll go for it then and once there's something sans-wordpress, (i can't remember what i got up to, it's probably be better to start fresh anyway, there's new stuff since I started it.)

I'll pop a staging server somewhere for a few rounds of picking at it before it goes live.

I dont know if there's any copy people about who would want to get involved with the creation of a few alluring passages or who'd be alright with goin o'er what i write. My copy is usually pretty good for a muggle but of all the things that I'm good at, copy is somewhere in he middle, so if anything was going to benefit to benefit from a professional touch, words is it.

ghost commented 8 years ago

Happy to help out with a copy-edit. Bang down what you want to say, and, subject to any additional guidance as to what you want, I can shape it/make suggestions for it.

jamieisboss commented 8 years ago

@ReddbridgeMark Awesome, will let you know when there's something for you to look at.

@amcewen A broader marketing type question. (And maybe a bit more difficult to answer unless the organisers have already discussed it, because really it should be consistent throughout all the outward facing communication) is there a voice that you guys have in mind for DoES. I found a decent article explaining so i dont try and we're on the same page with the definintion.

Personally I've always thought the secret acronym and the Days since last explosion sign (accurate as it is) and other little touches make the place feel personal and able to be funny in an introspective way. (and for this bit, I'd also met a few of you before DoES was born, so I cant use myself as an example anyway) That's all real world stuff though so ideally, we want to mirror the real word feeling as much as possible in/on anything that is meant to be attracting people to DoES. Doing so should minimise wasted time and maximise conversions, or to not sound like a Salesperson, people feeling what they expected to feel on their first visit means they'll probably join or they wouldn't have bothered coming.

skos-ninja commented 8 years ago

The only issue I see with moving away from wordpress is that we will either have to import all the old blog posts or keep an old version of the site

jamieisboss commented 8 years ago

Thats not an issue, im guessing the weekenotes thing generates a blog post then, you can export them all from the backened as json anyway, or use the new API to pull them across. No neeed to worry about that stuff, I'll have the new site running in a staging environment before we switch so any/everyone can check it's all alright, and I'll keep the old one running with the name changed for a few weeks after the switchover ideally so a rollback will be a DNS change and 2 wordpress database fields (if we put you on cloudflare, that stops th 48hour dns propogation thing so would be useful here, should be discussed but ive started a new repo for the website as of 30 mins ago so these things can be seperated out into their own issues list)

skos-ninja commented 8 years ago

I will also need an api that I can ping so that the status system can detect if it is offline

jamieisboss commented 8 years ago

it'll be a static html site fro the user perspective so just getting a couple of pages return 200 would be ok id have thought; unless you say otherwise in which case let me know what you need. From the other side some extra tests would fire after any generators run as part of the generation process? Would that be cool?

skos-ninja commented 8 years ago

If it's going to be a static site wouldn't something on github pages using jekyll be a smart idea then? This would also solve any hosting issues as it's run for free by github

jamieisboss commented 8 years ago

It would, but I don't know if the concept can be implemented in jekyll alone, I don't know it particularly well, though I've not heard anything negative about it so I assume it's pretty good I'll explain what I've been thinking in a sec, plus, in usual transparency, wordpress would have been easy, but if we weren't doing that, which I still agree with for speed (and adding that Google AMP), I wanted to do some stuff in systems that I've wanted to work on for a while so I can get one under my belt for the future, until a couple of days ago I thinking to use aws, (s3, lambda, cloudfront, etc) But after all the new firebase features were announced, that seems like an equally important technology which supports the breif, so I don't really want to do it that way given my current knowledge , but I'd like to have some more knowledge and that could well pull me into full agreement, I'll have a look at the Jekyll docs, but I'd like to also open this back up a bit and check I'm still going in the right direction, and that no one else is wanting in on the site design and build, because I probably would have just started ploughing through it sometime soon, as it seemed quite settled, I thought I might be rocking the boat with the idea outlined below, but maybe I'm not, or I'm not enough @amcewen

Where I'm coming from: The breif was that this new site was meant to be a separation of concern. Moving away from focusing on existing members, as better solutions like everyone was using github anyway.

The plan then was to use the freed up 'purpose space' on the main site to market DoES in a more approachable way * which allows for a more welcoming onboarding, after giving them time and answers, and whatever else the data would show demand for, guiding visitors to the information or whatever content they were looking for, then continuing to shape the site to match the successful inbound search terms and social media referrals to ensure that the site was providing the right information, encouragement and feeling to move from the website to a maker day/night or a cake hotdesk day. Originally the idea was to stay with wordpress, but it seemed to be unnecessary bloat when most of the content is pulled, embedded or autogenerated to use wordpress where we'd be undoing it's core functions anyway, hence the whovian-static idea, serving static content that was regenerated in response to a range of different events (or the appearance of Karen Gillen)

_*(as the feeling of needing to already belong was repeated in the feedback I got about the existing site when I asked some people a while back (scientific I know) , it's also the feedback I hear most about the space after people visit, usually something like " everyone seems lovely and it was fun, but... [I don't feel like I know enough] | [I don't know know what I'd do after the thing I'm thinking about now] | [Everyone seems to know about this stuff, how would I learn? ] ".

Perhaps a look at how onboarding members could counter some of these things would be beneficial? I have only seen a heavily biased sample and have no idea how many visitors convert so Im only commenting on the off chance that it's a good idea, because I don't actually have a clue and I'm aware of that. )_

Anyhoo, To that end, I was thinking for the site to change regularly , but for those changes to be almost entirely data driven (from referral, search term, advert {I know but it works with ssl and you only need a bit to get a ratio then you can jib it off } plus reported local search volume for key terms and feedback, Maybe also twitter if there's anything useful there } not necessarily taking into account anything other than machine guided effectiveness and some proof reading'. Potentially even automated split tests with victory conditions cycling nightly or faster to adapt to changing trends

For all that, I really wanted to use aws and lambda, service workers, geolocation, visitor identification and any other cool things that could alter the site to mould it to the user, eventually leading them to the community here (or perhaps away to somewhere more appropriate if they aren't looking for a DoES right now) when they have had their 7ish comfort interactions with the website, which I think I've now made sound like a like a machine learning powered personal seduction engine (which as a marketer, sounds just about perfect. As a human, mildly terrifying, but if it becomes self aware, I think it'll just travel through time seducing it's way through history until it eventually creates itself 😉 ) So this idea has been bubbling for some time, but no one asked until now so I hadn't wanted to commit to this until I was more sure it was achievable in the time I have coming up to do it in.

Firebase is a bit 'spanner in the works' after I/O because of the integration with analytics/adwords and the expanded free tier, plus the whole realtime concept could facilitate a very dynamic type of static site but I haven't played with that since the IO changes so I was going to try and do that before someone said this, but I apparently haven't checked github for a few days and you've beaten me to it

However, I need to start planning things soon, so either I've just convinced you, or you've mentally been countering my points, and I'm about learn that jekyll or something else completely that you know about that's a better fit is pretty freakin sweet.

Second however it's been said so many times now about different systems; I need to know if it's going to be policy of some sort that no 3rd party soley manages a service that something of DoES ' lives on as it will be a design constraint if that's the case, probably not a problem one, but one to be taken into account when planning.

From my perspective, the website was something that no-one particularly wanted to manage or jumped on whenever this process started, so I tried to come up with a concept that did a similar thing for advertising as the site does for content now, but github seems to be much better at getting people interested, which is cool, but should I change my underlying assumptions and the concept built on them, dialling back the automation aspects, or are people concerned about certain specifics which I should account for? Or something else?

zarino commented 8 years ago

@jamieisboss – Eeek, starting to sound quite complex. Maybe before you jump into a big project like this, we should make sure we're solving the right problems? It would be a shame for you to build something nobody uses!

My suggestion would be for someone to talk to the DoES organisers, members, and visitors, find out what they like and don't like about the current site, and use that information to draw up some quick personas / user needs documents. Then you've got something concrete to base your improvements on, and you can make sure you don't spend time implementing features nobody needs.

You might be surprised to find that most people's requirements can actually be met by just a super simple site with some well crafted copy and a clear layout. Or the research might point at something more complex, in which case, great, at least you've now got some clear user needs to base it on.

Anyway, if you think some user stories like this might be useful, but none of the DoES regulars want to conduct them, I can do them for you. Just let me know. It'd probably take a week or two.

jamieisboss commented 8 years ago

Anyway, if you think some user stories like this might be useful, but none of the DoES regulars want to conduct them, I can do them for you. Just let me know. It'd probably take a week or two.

@zarino That would be awesome thank you, i was a bit tired writing my last response and jumped in a bit heavy and at the wrong end, worry not; Simple, clear and good copy (and good images!) are the starting point from which here might not be a reason to go anywhere. The Rest is just me wanting to make something clever, but that comes last, sometimes never at all. :innocent:

My suggestion would be for someone to talk to the DoES organisers, members, and visitors, find out what they like and don't like about the current site, and use that information to draw up some quick personas / user needs documents. Then you've got something concrete to base your improvements on, and you can make sure you don't spend time implementing features nobody needs.

This i did but there's a lack of consistency in that everyone wants different stuff, or not to change anything, or less stuff, or doesn't care. Though that was a while ago, with the github quicksand, it will almost definitely be worth re-vistitng this now the site isn't the only option for a lot of things.

Next then:

(but they aren't the target any more so also:)

amcewen commented 8 years ago

@zarino: If you could do some user stories that would be fantastic.

@jamieisboss: that sounds like either (a) an attempt to use every web service from AWS all at once or (b) a completely different startup all of its own. Or probably both of those things :-D We'll have a better idea once we've got some user stories, but my gut feel is that @zarino's right and a simple clear site will probably meet our requirements.

And if the user stories are written down somewhere (maybe that's what we missed when - as you say - you asked around about what was wanted) that will effectively form a spec for what's wanted (and is easier for people to argue with/suggest additions to)

goatchurchprime commented 7 years ago

Nothing left on wordpress site except the weeknotes, some deep-links from the menubar into the wiki

DefProc commented 7 years ago

Probably worth keeping this open, as the website is still running on a basic theme. So the original issue is still valid.

zarino commented 7 years ago

The new main nav—especially with that “Services” menu—is so much better! Well done everyone involved!

DefProc commented 7 years ago

I think the biggest improvement we could make in the short term would be to have a better overview of the services that DoES offers. As there is currently a menu item, but no page, a services page with some kind of table breakdown listing services, cost and benefits would be easier for a new viewer to see what we offer them, and what it costs.

e.g. things like:

goatchurchprime commented 7 years ago

Done that: https://github.com/DoESLiverpool/wiki/wiki/Membership-and-access#rates

goatchurchprime commented 7 years ago

Perhaps we could close this and replace it with a slightly more closable ticket -- ie one that can be satisfied.

Now that all the changeable content is moved to the github wiki (where folks can efficiently self-manage their accounts and therefore do stuff), the wordpress page is only holding deep-links to the github wiki and the weeknotes.

Do we want to specifically improve the decoration and banners on the wordpress page with a photo or something? Do we want to fiddle with the layout and decoration on particular core pages on the github wiki? Either of these (or both) would define a ticket that's a bit more soluble and has a greater likelihood of getting closed.

DefProc commented 7 years ago

@goatchurchprime I've reverted some of the wiki links for the website, specifically dropping the Membership and Access link because it's a page that does everything-in-a-giant-page, and separating out:

amcewen commented 7 years ago

Organisers' meeting notes: There's an ongoing group looking at this and covered in the last meeting minutes.

DoESsean commented 7 years ago

Helen has agreed to help with the website. @amcewen or @johnmckerrell , can you please put her in touch with Will (as she's not sure who he is) and see if they can coordinate together?

DefProc commented 6 years ago

Update on this:

We've got a working group on this consisting of:

The expected work will split into two parts:

1) revise the current website to make DoES offering more prominent, and explain where DoES is currently/will be located for prospective users. 2) A larger redesign to better present DoES through the website.

We're creating a spec for the outcome at the moment, so are currently collecting input on features, recomendations and warnings, either below, or on the whiteboard in the main room. This is based there being two main user types for the website:

goatchurchprime commented 6 years ago

Where is this document? (Maybe on the wiki?)

I've put some notes on the whiteboard, mostly about a really good "how to find us" printable page, and inlining feeds of events, twitter, issues, personal github commits and equipment status on the front page.

Also, @paulfurley has tech for syndicating other events into the main feed.
https://github.com/DoESLiverpool/somebody-should/issues/573

Oh, and we should use Bret's plugin that dumps your websurfing history into a daily stream of links. Use this feature whenever looking up technical stuff or searching for electronic sensors you're thinking of buying (or writing drivers for) to more easily get to know when someone is sizing up for an order.

I'd like to be able to publish my RS shopping cart before I pay so other people can add stuff to it.

DoESsean commented 6 years ago

@willcrobinson and @Helen-8, any idea when you guys will be available to get together again?

I don't know if there has been any movement on the discussion we had last time - and we should probably include any notes that were made in this issue so that people can see where we're up to - but it might be worth seeing if we can fit something in before Christmas if you have chance, although I do appreciate that this is a busy time for everyone so that might not be possible.

ajlennon commented 5 years ago

Website looks lovely to me. Can we close this?

zarino commented 5 years ago

Yes! If there are outstanding issues with the website, it’s much better to raise them as new tickets, than keep this old one open.