Gauge website
Pre-requisites
Install
$ git clone https://github.com/getgauge/gauge.org
$ cd gauge.org
$ bundle install
$ bundle exec middleman serve # To view the website locally
$ bundle exec middleman build # To build the website
Gauge website
Home Page: https://gauge.org
$ git clone https://github.com/getgauge/gauge.org
$ cd gauge.org
$ bundle install
$ bundle exec middleman serve # To view the website locally
$ bundle exec middleman build # To build the website
Change the paragraph text under Quickly Detect Issues to say:
Don’t waste time going through stacktraces. Gauge takes a screenshot on a test failure allowing you to get a visible picture of what went wrong. Reports are available across multiple formats (XML, JSON, HTML).
Logo at the top of https://insights.gauge.org/ is loaded from an http URL and does not load.
Please change the paragraph to:
Don’t spend time in tedious setup for parallelization of tests on your CI/CD pipelines. With Gauge's out of the box parallelization support, speed up your tests and optimally utilize your infrastructure.
The code in https://preview.gauge.org/2018/05/15/why-we-built-gauge/ is not formatted properly in parts. For example, see the closing braces in the code section after: "For example, Selenium recommends the Page Object design pattern. Let’s use it to refactor the same test".
The chosen font also doesn't look like it is monospace, though it is. It is "Source Code Pro", but looks off to me.
When I land on https://preview.gauge.org/blog/, there is no visual indication that this is the blog page. A highlight on the navigation link, or a header might help.
We should have a link to TW Privacy Policy accessible from the website. https://www.thoughtworks.com/privacy-policy
We can call it "Privacy" and add it under "Explore" in the footer
Does not feel very descriptive
Could it say what we will find - Gauge commands - instead
No rel=canonical tag on the website. Should be on every page of the website. We will need to have the ability to remove this tag on blog pages in the event we should republish someone else's content.
Some links open up in new window, other don't. This does not:
For alternate methods of installation and our nightly releases, check out our documentation.
In step 1 of getting started guide.
From @zabil on June 13, 2018 4:29
We have a lot of external contributors.
We don't want to alienate them by taking credit.
Copied from original issue: getgauge/docs.gauge.org#74
The form to subscribe to product updates is missing in the Get Started page
Please change the text to
Gauge supports data-driven testing. Keep your data sets out of your test scripts to run them repeatedly against multiple data sets. Easily test with large data sets, while keeping specifications highly readable.
This link https://preview.gauge.org/index.html#features doesn't take me to the Features section.
Can we get it to the top navigation?
I have to scroll all the way below for the blog link. Its not obvious to people landing on our website that we have a blog. Can we make it more visible?
https://docs.gauge.org/latest/index.html?404#alternate-methods does not go to alternate methods
Change the feature text here:
[Heading] Create readable and maintainable tests
Gauge tests are in markdown which makes writing and maintaining tests easier. Reuse specifications and robust refactoring to reduce duplication. Less code and readable specifications means less time spent on maintaining the test suite.
It doesn't go anywhere.
If we are going to use a different typeface for headers, we should restrict it to the URW Geometric to keep it consistent with our other marketing materials. It is still ok to use Open Sans for body copy (ie
tags).
There is no meta description or keywords on the pages
Go to /get_started/
See OSX
Click on the Zip tab in Step 1.
The Zip file is missing. Refer document for intended outcome.
https://docs.google.com/document/d/1NeNfH3xWFXxKkU70Dg6Ag53RE4T0_gvbxQq72dPDgxc/edit
The top navigation on https://preview.gauge.org/plugins/ doesn't have the /Blog link.
This what Zabil said we should expect:
A new user
- Lands on Gauge.org
- Reads about features
- Clicks “Get Started” button ti view “Get Started” page
- Reads steps to install the Gauge binary, language runner, run tests
- Downloads and installs Gauge if interested
- Sees our support for VS Code
- Reads instructions on how to install Gauge Visual Studio Plugin
- Reads our welcome page inside VS code (this links to main documentation site) (exit) or
- Clicks on a "Learn More" on the "Getting started" page. (display this at the end of the steps)
- Views main documentation
- Reads installation for other options or to troubleshoot existing installation using the “Installation” section.
- Reads “Write Specifications”
- In each category of documentation we'll add a "What next?" and link to next steps for e.g on "Write Specifications" What next will be "Run Specifications"
- Reads "Run Specifications"
The "Get Started" link is always available on the top menu for those who land directly on the documentation page.
But I don't see the "Learn More" links at the bottom of getting started.
IMO we should at least have a final pointer to the documentation.
Change paragraph here:
Gauge has a robust plugin architecture and plugin ecosystem. You can easily extend Gauge to add support for IDEs, drivers, datasources, text execution events or your favourite language.
The yellow border around getting started appears which draws the eye and the it appears to jump when going over a section. I have a .mov if you want to see what I see.
on https://gauge.org/get-started.html, the "Windows" tab is selected if when I am on windows.
on https://preview.gauge.org/get_started/ it shows the first (i.e. macOS).
The tabs should select the user's OS by default.
The link in this sentence goes to a 404 page on Medium:
Gauge automatically sends telemetry data to help us improve the product.
Please connect the "Learn More" link to "docs.gauge.org".
Also please change the text to "Documentation". Learn More makes me think I am learning more about the product in terms of features.
Please create the following redirects to this page https://preview.gauge.org/get_started/
/gettingstarted/
/getstarted/
/download/
/install/
/get-started/
/quickstart/
No schema or twitter card currently on website
The text on pages like this is difficult to read
https://preview.gauge.org/2018/05/15/why-we-built-gauge/
Can we improve the spacing/styles to they are easy to read?
It's below the first "Getting started" button in the hero section.
Won't this be a better link to use in the footer? It shows you questions rather than taking you to the login screen, if you're not logged in.
This will probably change when site is live, but just noting here that we should ensure the top navs between domains all match.
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.