Website Operator/Maintainer #12
Comments
2017.12 reportWe (@ripcurlx, @csacher and I) kicked off a project to redesign the website this month, but had to drop it just as quickly as we started it due to the massive ramp up in volume and the bandwidth issues it caused for me. See bisq-network/bisq-website#35 for details. Otherwise, with regard to changes, it was an uneventful month on the website. I updated and dramatically simplified the https://bisq.network/community page, and added some convenience redirects like https://bisq.network/calendar and https://bisq.network/phase-zero. That's about it. In terms of traffic, we had a big month, with e.g. nearly 2x growth in pageviews.
As an aside, I'm not sure if I'll continue reporting on Google Analytics here in the future, or if that's better left to @ripcurlx in the context of Analytics (#40). |
2018.01 reportNothing to report. Just basic maintenance on the website this month, updates for new releases, typo fixes and the like. No analytics from this point forward, I'm leaving that to @ripcurlx in #40 as mentioned above. Generally, the website is still a source of pain for me, and I'd love to see progress on the redesign, but there was just no opportunity for it over the last month or two being so busy. Let's see what we can do in the months to come. Not sure whether this'll be able to get priority, at least from my side. |
2018.02 reportNo major changes this month. A couple version updates and a single pull request. |
2018.03 reportNo major changes this month. |
2018.04 reportNo major changes this month, but changes may be on the way soon with @pedromvpg's new brand refresh proposal, which includes a fairly detailed treatment of the website. See https://github.com/bisq-network/bisq-design/blob/master/bisq-refresh.pdf for details. |
2018.05 reportNo major changes to the Bisq website this month. Focus is on building the docs site out (see #35 (comment)), which will make it possible to completely refresh and radically simplify the website when executing @pedromvpg's design proposal. |
2018.06 reportNothing to report. |
2018.07 reportNothing to report. |
Cycle 12 ReportThere were a couple of new blog posts. The new getting-started page was supposed to go in motion during this cycle, and probably still will, but not until after the proposal phase is over. Along with that new page, we'll probably start testing a new front page (numerous people have said the primary call-to-action is confusing) as well as some basic refactoring.
|
Cycle 13 ReportPR for a new getting-started guide is reviewed and ready to be merged, just need to update some documentation on the wiki beforehand. Also during this cycle, the website underwent a thorough structural refactoring to eliminate a lot of cruft, make it easier to maintain overall, and to prepare the site for an overhaul in the translations workflow.
|
Cycle 14 ReportNew getting-started guide was finally merged. Traffic snapshot for month of May:
|
Cycle 15 ReportNot much activity on the website until the past week, when we had a Slovak translation PR submitted and a dark mode PR submitted (both are currently under review). Traffic snapshot for month of June (getting-started page on docs got 5000+ impressions per month, which means that the call-to-action on the front page drives most of them—it's still pointing to docs!):
|
Cycle 16 ReportIn this cycle I merged a small handful of updates either suggested or implemented by Pedro:
I also spearheaded a long-overdue initiative to overhaul the translations workflow. Until now, there was no automated connection between Transifex and the website (aside from Transifex regularly pulling updated English source files from GitHub). This resulted in translations work being done but not actually showing on the website. Without an automated workflow in both directions, the status quo was either bound to continue indefinitely and/or any attempts to update the website would have been error-prone and disjointed. The workflow I created is much like the one for bisq-desktop...there's just one script that pulls everything from Transifex and does all the necessary language updates in the source code. It's partially merged. I'm working with bayeratoor to review the remaining pull requests, put the workflow into action, and get translations going again. Documentation will be added to the wiki once all relevant pull requests are merged. This workflow isn't mission-critical at the moment, but will be critical when we launch initiatives in new markets. Traffic snapshot for month of July (updated links to the getting-started page were merged a couple weeks in, which explains why traffic to getting-started page is starting to spike):
|
Cycle 17 ReportWebsite translations are now live again, as the new workflow has now been merged and documented. Other notable changes:
Below is a traffic snapshot for month of August. Notice that the getting-started page is now getting ~9,000 views per month, which is almost double the views the old one was getting. It's now the #1 entry point for the whole website (see chart below).
|
Cycle 18 ReportNo changes aside from routine changes: stats page update and cycle 17 report. Below is a traffic snapshot for month of September.
|
Cycle 19 ReportMerged a relatively minor PR to only show active markets in the dropdown on the markets page, and also merged a post covering v1.5.0 highlights. Couldn't do the routine cycle 18 report and BSQ supply update because of issues with obtaining DAO data via my usual script, which, as I understand it, is the result of some pending refactoring. October Traffic
November Traffic
|
Cycle 20 ReportIt was a quiet cycle for the website -- not much to report. December Traffic
|
Cycle 21 ReportNot much to report...just added a couple of overdue cycle reports. January Traffic
|
Cycle 22 ReportThere was another important error discovered by a user on the FAQ page earlier this cycle...it's been a couple of times now that page ends up not being properly updated (another example: trading fees). I will be moving this page to the wiki. Traffic stats are high across the board...I assume this is a result of the bull market making all numbers look rosy. February Traffic
|
Cycle 23 ReportNot much to report for this cycle. March Traffic
|
Cycle 24 ReportThe FAQ page was overhauled, and the overhaul was posted on the wiki. The website FAQ page will be removed soon and redirect to the wiki; all links to the FAQ page in the software are already removed. wiz and softsimon are putting finishing touches on a brand-new markets page that will supplant the website's markets page. The semi-automated DAO reporting project had to be paused as much of my time this cycle went toward Bitcoin 2021 preparations. April Traffic
|
Cycle 25 ReportNo notable updates on the site in this cycle. Traffic was down significantly from last month...perhaps because of market dip? May Traffic
|
Cycle 26 ReportRemoved FAQ page on website and redirected to FAQ page on wiki, removed markets page and redirected to https://bisq.markets, removed vision page, and updated a series of links to point to the wiki. Traffic was down again significantly...will keep an eye to see if it has to do with market, analytics mishap, or something else. Traffic sources analysis doesn't reveal anything insightful; traffic across all sources was consistently down. June Traffic
|
Cycle 27 ReportUpdated ripcurlx's public key. July Traffic
|
Cycle 28 ReportMerged a handful of pull requests to fix typos. August Traffic
|
Cycle 29 ReportNo notable changes. September Traffic
|
Cycle 30 ReportA semi-automated dashboard is now available showing basic supply metrics and proposal details. Documentation and further details are in the The dashboard probably does not cover 100% of what people would want to see on such reports...it's intended to be a foundation for others to build on. October Traffic
|
This role is responsible for the Bisq website at https://bisq.network, including maintaining its source in the https://github.com/bisq-network/website repository and its operation / hosting on Netlify's static site hosting infrastructure.
Docs: none, other than the above
Team: @bisq-network/website-maintainers
Primary owner: @m52go
The text was updated successfully, but these errors were encountered: