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

Migrate site to Jekyll / Netlify #1

Closed
cbeams opened this issue Jul 25, 2017 · 1 comment
Closed

Migrate site to Jekyll / Netlify #1

cbeams opened this issue Jul 25, 2017 · 1 comment
Assignees
Labels

Comments

@cbeams
Copy link
Member

cbeams commented Jul 25, 2017

The bisq.io site has recently been ported from WordPress to a static site. These assets can now be found in the wordpress branch of this repository.

In its current form, the site is a serious maintenance burden, because there is no templating or static site generation framework in place. This means lots of copying and pasting, and all the problems that follow.

This issue is about porting those static assets to Jekyll, removing duplication, etc, along the way.

No visual / layout redesign work will be done in the process, but certain pages / assets may be culled, especially those that are effectively dead / orphaned anyway.

When complete, the site will be hosted via GH Pages and will take advantage of the usual push-to-publish workflow that GH Pages offers.

@cbeams cbeams self-assigned this Jul 25, 2017
@cbeams cbeams changed the title Port site to Jekyll Migrate site to Jekyll Jul 25, 2017
@cbeams cbeams added this to the 2017.30 milestone Jul 26, 2017
cbeams added a commit that referenced this issue Jul 28, 2017
Using command:

    git ls-files | xargs dos2unix

Note that this change also strips trailing whitespace.

See: #1
cbeams added a commit that referenced this issue Jul 28, 2017
Using command:

    git ls-files \
        | egrep -v '(jpg|png|ttf|pdf|ico|gif)$' \
        | xargs -I file tab2space -lf file file

And verified with `git diff -w` to ensure only whitespace changes were
made and that no binary files were modified.
cbeams added a commit that referenced this issue Jul 28, 2017
This had been set to `display: none` anyway, so was already dead code,
but the site is indeed no longer powered by WordPress at all, thus the
removal.
cbeams added a commit that referenced this issue Jul 28, 2017
cbeams added a commit that referenced this issue Jul 28, 2017
cbeams added a commit that referenced this issue Jul 28, 2017
To match exact spacing of current https://bisq.io page. This can be
adjusted later.
cbeams added a commit that referenced this issue Jul 28, 2017
cbeams added a commit that referenced this issue Jul 28, 2017
cbeams added a commit that referenced this issue Jul 28, 2017
The formatting changes in the previous commit broke layout of header and
footer navs. This change puts the previous formatting back in place.
cbeams added a commit that referenced this issue Jul 28, 2017
cbeams added a commit that referenced this issue Jul 31, 2017
cbeams added a commit that referenced this issue Jul 31, 2017
cbeams added a commit that referenced this issue Jul 31, 2017
@cbeams cbeams modified the milestones: 2017.31, 2017.30 Jul 31, 2017
@cbeams cbeams changed the title Migrate site to Jekyll Migrate site to Jekyll / GH Pages Aug 2, 2017
@cbeams cbeams added the Epic label Aug 2, 2017
@cbeams cbeams changed the title Migrate site to Jekyll / GH Pages Migrate site to Jekyll / Netlify Aug 4, 2017
cbeams added a commit that referenced this issue Aug 9, 2017
@cbeams
Copy link
Member Author

cbeams commented Aug 9, 2017

Closing as complete!

@cbeams cbeams closed this as completed Aug 9, 2017
cbeams added a commit that referenced this issue Sep 9, 2017
Problem #1: we were linking to outdated arbitration-system and
risk-assessment PDFs.

Solution #1: introduce /docs/exchange/arbitration-system and
/docs/exchange/risk-analysis redirects pointing to more up-to-date GDoc
versions

Problem #2: we were linking to newly transcribed exchange and dao docs with
full GitHub URLs, which are long and hard to read at a glance when
mousing over.

Solution #2: introduce /docs/exchange/whitepaper, /docs/dao/overview,
/docs/dao/specification redirects pointing to correct URL for these
docs in GitHub (and in GDocs for the latter).
m52go pushed a commit that referenced this issue Jun 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant