Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a pricing table to the website #460

Open
DefProc opened this issue Feb 27, 2017 · 13 comments

Comments

Projects
None yet
7 participants
@DefProc
Copy link

commented Feb 27, 2017

I've had a quick go in the Services page (from #19 ) with a pricing table plugin.

Services:

  • Free Events
  • Friends
  • Friends with benefits
  • Hotdesking
  • Monthly Workshop
  • Permanent Desk
  • Registered Business Address

There's still a bit of tidying up and clarification to do.

@zarino

This comment has been minimized.

Copy link
Member

commented Mar 13, 2017

FWIW, this morning I was looking for the pricing page (I could remember having seen it in the past!) but I couldn't find it anywhere in the nav:

screen shot 2017-03-13 at 09 34 01

I tried "Workshop", but that just led to a Wiki page. Same for "Co-working".

It took me a while to realise that the top-level "Services" nav item was itself a link to the pricing page. I’d assumed that clicking "Services" would just open up the dropdown menu, so I never bothered clicking it.

I wonder whether you could add a "Pricing" option into the dropdown menu, that just links to the pricing page?

screen shot 2017-03-13 at 09 37 25

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Mar 13, 2017

@DefProc

This comment has been minimized.

Copy link
Author

commented Mar 13, 2017

Added the Pricing link.

@zarino I'd actually like to change the Co-working and Laser Cutting links to point to website pages that summarise them, rather than to a catch-all page on the wiki, but that's probably best in a separate issue.

@aubergine10

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2017

@DefProc Do you have text images available? If so let me know and I'll add those pages. There's a bunch of stuff I want to move from wiki to website; links unexpectedly dumping website users in github wiki is bad UX.

@JimSparrow

This comment has been minimized.

Copy link

commented Apr 29, 2017

@aubergine10

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2017

Yup - afternoons/evenings are easiest for me (trains are PITA in mornings).

@Red-Violet

This comment has been minimized.

Copy link

commented Apr 29, 2017

@aubergine10

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2017

Yes, definitely. I was just thinking in the interim it would be worth moving some of the github content on to the website (same information - different place) to avoid sending end-users in to github randomly when they click things on website.

In terms of design, I wasn't going to change anything - we still need that DoES "vision" work to be done, in order to work out what specifically the website needs to deliver.

@Red-Violet

This comment has been minimized.

Copy link

commented Apr 29, 2017

@aubergine10

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2017

@Red-Violet I'd like to arrange a meeting regarding the website as soon as possible so we can get some clear action points and timescales. See also: #480

@stevesparrow Are you OK for me to clone some git wiki content (probably about 4 pages) on to the WP site in the interim just so that visitors aren't being dumped randomly in to git wiki? Mainly just something to tide us over while the bigger changes are being discussed.

@JimSparrow

This comment has been minimized.

Copy link

commented Apr 30, 2017

@aubergine10

This comment has been minimized.

Copy link
Contributor

commented May 2, 2017

Yup, good plan. My email address is guy.fraser1@gmail.com

Another topic that might be worth discussing is whether to stick with WP or not? Having looked through existing content on the site it's mostly blog posts which would be relatively easy to convert to some other format. We could also take markdown from the wiki and render it as HTML (although that poses various limitations on formatting).

Just seen a post by Alex in the google group - he's requesting ability to blog / microsite on the DoES website and it might be worth adding him to the meeting as well?

@aubergine10 aubergine10 modified the milestone: Website 2.0 May 3, 2017

@DoESsean

This comment has been minimized.

Copy link
Contributor

commented Dec 14, 2017

#19 needs to look at this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.