cucumber-attic / website Goto Github PK
View Code? Open in Web Editor NEWCucumber website blog, plus a few other static pages
Home Page: https://cucumber.io
License: MIT License
Cucumber website blog, plus a few other static pages
Home Page: https://cucumber.io
License: MIT License
See stacruz/sinatra-assetpack#197
There's a bug (rstacruz/sinatra-assetpack#189) that prevents the CSS from being rebuilt when a LESS partial is modified.
Process:
Pages to migrate from https://github.com/cucumber/cucumber/wiki:
I wonder if a public slack channel might be easier and less intimidating for some users looking for help than IRC?
Why doesn't the site use Bootstrap's navbar? It's nice and responsive. It makes it easy to fix it to the top, which I think would be nice since many of the pages under /docs
are rather long.
I'm sure we can style it to look like the current custom navbar.
Go to https://cucumber.io/docs/reference/jvm and scroll all the way down to see it.
Right now there is a horizontal scrollbar. Also, the top nav should be a hamburger menu maybe?
The tutorial should work for any implementation of Cucumber.
Steps:
It should be suitable for people who want to implement cucumber on a new platform. It should reflect all implementations (if possible). It should also be useful fof people who want to write extensions.
Why: makes it easier for both producer and consumer of the content to find what they're looking for. It also improves search.
The links in the left nav are expanded and highlighted when the user scrolls, but the highlighting in green isn't very visible. I think it needs more contrast - maybe change the background colour? Invert the foreground/background colours?
Current problems:
Some other tools pass-through CLI options to cucumber, and had to fish them out from the code:
https://chimp.readme.io/docs/command-line-options#section-cucumber-options-
I suggest we go for https://swiftype.com/
I find the normal font (Lato, 16px) very hard to read. The "i"s and "l"s are frequently antialiased to the point where they are just a grey line.
Look at the different "i"s.
It seems improve a little if we change text colour from the branded black #1B1D1E
to #000000
and increase the font size to 18px, but it's still not great. We're currently using font weight 300. Should we increase to 400?
See "edit" link at the bottom of http://cukes.info/browser-automation. Leads to 404.
It’s just a real mixture. It’s not just exclusive to Cucumber either, which it could easily be. Instead it really embraces all of the other stuff around, and there’s no attempt at all to to push the direction down a certain path towards Cucumber stuff; in fact challenge and healthy debate seems to be really welcomed which is a really nice thing.
-- Jenny Martin
People are friendly, it’s a really nice atmosphere. Other conferences can sometimes be very technical or quite egocentric. But there’s none of that here. It’s very inviting. You learn a lot. You get to see a problem from various different angles. It’s not just all technical, it’s not just all product, it’s not all just testing. So it enlightens you and opens up your eyes to other people’s viewpoints on the same problem, so it’s really good.
-- Ingram Monk
If I think back to what I’ve learnt in the past three or four years, so many of those ideas have come from people in this community and people that have spoken at CukeUp! today. And I’m looking forward to going to the pub to carry on these discussions!
-- Pete Buckney
What is the true value of BDD?
This is a guest post by Hamish Tedeschi, Managing Director of Magentys. Hamish is also a co-organiser of CukeUp! AU, coming to Sydney at the end of 2015. Click here for more details on CukeUp! AU.
2 successful days at YOW! West have just come to a close - my first YOW! conference, but definitely not my last. I made some new friends and also learnt quite a bit - time to learn some Clojure, I think! The theme of the two days was, without doubt, microservices, but that also seemed to be surrounded by another theme of collaboration and building the right thing. This seems to be a constant recurring theme in all conferences and companies I visit. How do we build the right thing in the face of misunderstandings, miscommunications and mistakes? It is THE most difficult thing... Coding is the easy part, that is just implementation detail. Too often we get hung up on the technology stack or the tools we may be going to use to achieve the job, when it seems using post-it notes can add more value than the alternatives. Don't get me wrong, I'm a big proponent of BDD, especially when done well, as I have seen the benefits first hand. But it seems we keep getting BDD wrong, even when we talk about it at these conferences or try to deliver a project using it.
For me, BDD is a design and discovery process. A method of expressing system intent in a collaborative way. We get executable specifications out of it which we can automate, if we choose. We then call these automated tests. This is wrong. Why?
The root of the problem is that these automated "tests" aren't actually tests at all. We may do some testing in the process of creating these automated tests, but once they are written, they are not "testing" anything. Testing is the process of evaluating a product by learning about it through experimentation, which includes to some degree: questioning, study, modelling, observation and inference. Once code is written, it cannot experiment, question or study anything. It just executes and does exactly what it is told, no matter what. I propose we strip out the word "testing" or "test" completely when talking about BDD, and replace it with "checking" or "check". This will go someway in reducing misconceptions about the process, the value it provides and more importantly, the value it does NOT provide. This way, we may also stop striving for exhaustive coverage when writing scenarios, thinking of these as vehicles for regression tests. It may also mean that when we think about them as a design concept, we get more contributions from BA's and UX'ers at the time of elaboration.
BDD is HARD. It is easy to NOT to write a feature together as a team. It is easy to create a feature whilst thinking of the implementation details rather than the desired behaviour. It is easier still, to build something without a failing check or not build the check at all. BDD requires discipline, however, humans tend to take shortcuts wherever possible. I still believe, with the right blend of team, we can do it though.
Hamish Tedeschi will be speaking at CukeUp! AU later this year. To learn more about the conference, sign up to our mailing list.
There have been some really great conference talks about Cucumber & BDD over the years. I'd like these to have a prominent home on the Cucumber website, with URLs that we can easily use and will stand the test of time e.g. http://cukes.info/vidoes#mabes-imperative-declarative
We're using Swiftype for search, and they say indexing will work better if we have one: https://swiftype.com/documentation/sitemap
It might help for Google too....
Kinds of events:
Acceptance criteria:
Nice to have:
See configuration for more details.
footer in https://cukes.info/blog is missing the footer background which is present in https://cukes.info/platforms
The link on the support page to the posting rules of https://groups.google.com/forum/#!forum/cukes, that is https://cukes.info/posting-rules (which is also used in the header of the https://groups.google.com/forum/#!forum/cukes), currently returns "404 NOT FOUND".
https://cukes.info/school.html should redirect to https://cukes.info/school
e.g. http://cukes.info/cucumber/api/ruby/latest/Cucumber/RbSupport/
Linked from "The Cucumber Book"
Someone pointed out that the link to the support forums on the support page was broken. I decided to spend 2 minutes fixing that.
That ended up being a much more complicated process that I had hoped for:
There was no edit link on the page, nor was there any info about how to report incorrect content. Visitors who spot mistakes are either going to keep it to themselves or perhaps send an email somewhere (if they can find an email address) with a plea to fix it.
Since I'm one of those rare people who happen to know what GitHub repo and sub folder that page's source lives in I navigated to support.html, hoping I could just edit the source there in the GitHub editor and the website would be updated automatically.
But then I came across one of the many READMEs in the repo that suggested I have to clone the repo and rebuild the website manually.
So I gave up - I only had 5 min to do this.
This is the workflow we need:
Contributor (2 min)
Team member (1 min)
Is there a plan to achieve this?
(1) GitHub will lead the user through the signup/fork steps if needed. Try to press the edit icon to a file on GitHub that you don't have access to to see the workflow.
TODO:
@theo-england would like to be able to line up blog posts to be published in the future.
We tried this today, putting in tomorrow's date. However the post was just displayed anyway in the index with tomorrow's date on it.
We need to just add a check to filter out posts with a date stamp beyond DateTime.now
It would be really handy for Theo to still be able to preview these posts, maybe with a query string flag to turn the filter back off.
If I look at https://cukes.info/events/cukeup-australia-2015 right now it's showing a 500 error page, but I have no way of knowing what's going on.
To do:
I just had a hiccup where added Theo's first blog post, and got a weird error that turned out to be due to him not being in the authors list in the config.
It would have helped a great deal if the backtrace had pointed me to the actual line of the feed.xml
template, instead of mistakenly pointing me to some random line in page.rb
.
The footer content is very basic. I'd prefer something like the one from http://kickstartacademy.io which has rolling content from the twitter account and blog (good for SEO) and useful contact info that you can link to from any page with a #content
anchor.
We used to have one on the old Cucumber Pro page. It's a simple form that adds people to the Mailchimp list.
The blog looks very plain. Minimum things for me:
It works, so we should set up a page rule on cloudflare to redirect cukes.info/* to cucumber.io/$1 I reckon.
Create an infographic first (in Sketch). Use as a basis for a video later.
It should go into this table: https://cucumber.io/docs#installation
It should also go into the various platform-specific pages:
e.g. I'd like to be able to republish https://raw.githubusercontent.com/paulrayner/paulrayner.github.com/jekyll/_posts/2015-03-28-bdd-is-a-centered-rather-than-a-bounded-community.adoc
Try this: https://cukes.info/docs/reference#command-line
The fix in b8f5465 makes the header visible, but it breaks the left nav, which is no longer aligned with the visible header.
I think the solution for this is CSS, not JavaScript. Something like this: http://fellowtuts.com/html-css/offsetting-anchor-hash-tag-links-to-adjust-for-fixed-header/
/cc @romaingweb
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.