Update the theme of the TabFern web site

[cxw42]

If you have HTML and CSS chops, roll a new Jekyll theme for the TabFern web site! Please check it on mobile and desktop before finalizing your PR. I am happy to try out and discuss a draft PR if you wish.

[sarthakpranesh]

Hey, I would like to help you get a new website running. Please do let me know what are you looking for and how should I start the work ( by making a new branch or forking )

[cxw42]

Thank you! Please fork gh-pages. The only visual guidance I have, unfortunately, is the TF logo and font - see #137 . @Yasujizr any suggestions?

Please leave the site content largely as it is for this issue. It can be broken into multiple pages if you wish.

[cxw42]

Please see updated contribution guidelines. Thanks!

[sarthakpranesh]

Sorry for taking too long, was taken up by some academic stuff

I have updated the site but I wasn't able to understand the already existing environment the previous site was hosted on so I only did changes to the following folders and files:-

• index.html
• assets

*for testing purpose I used the live server extension on vsCode

Also attaching a video link showing the current site ( please let me know of any changes ) https://drive.google.com/file/d/1qtq4edMutjkD9D3wbGqdBdy8BMRDL82R/view?usp=sharing

If you give a go-ahead I'll open the PR Warm regards

[cxw42]

There video looks good - the theme is nice and clean! I would be happy to have a PR.

Development is on the jekyll branch. Sorry I hadn't documented the process yet!

• Clone TF and git checkout -b newsite origin/jekyll.
• Make a GitHub personal access token, e.g., following the instructions here.

• Set the JEKYLL_GITHUB_TOKEN environment variable to the value of the new token. E.g., on Cygwin, I have a token.sh that just says

  export JEKYLL_GITHUB_TOKEN=

  and I run . token.sh to load the environment.

• Install Jekyll
• Run make build. This will build the site to _site.
• Run make test to see the site on localhost.

When ready, commit your changes to jekyll and send the PR! After it is merged, I will update the gh-pages branch (which holds the live site) by running make deploy and committing.

Edit If you would like to propose a non-Jekyll solution, that's fine too - feel free to submit a PR directly against the gh-pages branch in that case. I only ask that the site be easy to maintain.

[sarthakpranesh]

Sorry for taking so long..........

I'll like to propose a non-Jekyll solution. The site is fairly simple and hence I believe it's deployment should be kept even more simple. I would like ZEIT solution ( https://zeit.co/ ). Deployment on ZEIT is quite simple and does not require any prior configuration. Plus no code will be required to be maintained for any deployment making the site liter and easier to maintain. (If you say I can deploy a test version)

For now, I am opening the PR on gh-pages. Hoping to hear from you soon.

[cxw42]

@sarthakpranesh Thank you for telling me about ZEIT! For now I will stay with GitHub pages, but I may use ZEIT in the future.