yungyuc / sciwork20 Goto Github PK

Sciwork 20 conference website

Home Page: https://conf.sciwork.dev/2020/

Makefile 6.38% CSS 17.52% HTML 39.59% Python 10.14% JavaScript 26.37%

sciwork20's Introduction

Sciwork 2020 website

This repository is for the website for the sciwork 2020 conference. Check-ins to the repository will be automatically deployed to the website by github webhook.

The website is built by using pelican. The flow for contribution is:

Clone the repository
Run a local devserver
Edit the content
File a pull request (PR) against develop branch
Resolve discussions in the PR review
PR is merged, done

Note

Do NOT file PR against the master branch.

In the working copy root, run the following command for the local devserver:

env SITEURL=http://localhost:8000 make devserver

Branch convention

The master branch is automatically deployed to the official website https://conf.sciwork.dev/2020/.

The develop branch is at https://under-development.sciwork.dev/2020/. It uses password protection to avoid public access. The user name is developer. The password is sciworkdeveloper.

Other branches will not be deployed.

Changes for improvement

To add contents or website features, create a branch named like feature/your-addition.

New blog entries

To add a new blog entry (will be shown in https://conf.sciwork.dev/2020/blog.html), the branch name should be feature/blog/entry-name.

Bugfix

If you want to fix bugs or typographical errors, create a branch named like bugfix/your-fix.

sciwork20's People

Contributors

Stargazers

Watchers

Forkers

chestercheng plchao gitter-badger moskytw uranusjr

sciwork20's Issues

[reStructuredText or Markdown]

I notice that some files in the /content/pages are written in .rst and some are written in .md . Is there a propose for that ?

Disable directory listing in Apache

As title, default indexing is enabled in Apache.

We can set the Options -Indexes in Virtual Host or .htaccess file to disable it.

Add and maintain talk pages

This ticket is for adding and maintaining the talk pages. It remains open until all talk contents are stable.

Pelican {filename} for internal link doesn't work

See #38 (review) . The {filename} marker described in https://docs.getpelican.com/en/stable/content.html#ref-linking-to-internal-content doesn't work for me. I don't know how to make it work and need. @chestercheng could you please you take a look, when you have time?

For now I am using the relative link workaround. But in blog listing page the link will be broken. See the links in:

Write a blog post to announce the two tutorials

The tutorials and sprints now have their own web pages (access from https://conf.sciwork.dev/2020/program.html). I should write a blog post to announce the tutorials first:

Convention for blog entries

This issue is to track the conclusion what branch naming convention should be used for blog entries. As I brought up in #22 (comment) , the options include:

feature/blog/entry-name
blog/entry-name