The platform setup needs to be finalized. Experimentation is currently in progress for using VuePress. Jekyll is a bit inflexible and a bit harder to use, but great advantage and simplicity using markdowns.

• configure with Jekyll
• create simple theme.
• simple home page.
• use tailwindCSS

@jpylvanainen Which image do you think would be best to use here?

Incorporate Vue into the site build so that we can make use of single-file Vue components.

Header (navbar) and footer need updating to be brand-specific.

Layout needs to be made responsive so that it also works properly on mobile and tablet-size viewports.

https://github.com/Turku-Bioimaging/turku-bioimaging.github.io/blob/724d855072b767159cebc3d4189309e818a7d2f6/_config.yml#L14-L33

@jpylvanainen Would you like to try updating the authors list and info? Clone the repository, then checkout the dev branch. Edit the authors section of the file _config.yml Commit your changes and push to dev branch. Then create a pull request to merge dev into main

@jpylvanainen This is a Github Issue that is used to track bugs or the creation of new features. Typically, an issue is assigned a label (bug, feature, enhancement, etc.) and a person is assigned to handle an issue.

Github Pages runs on Jekyll 3.9 by default. We would like to move to Jekyll 4.2 to have more flexibility in terms of the latest themes and Jekyll features.

A Github workflow will need to be setup in order to automatically build the production site on push.

https://github.com/Turku-Bioimaging/turku-bioimaging.github.io/blob/13986939ef7d347b371767d06beada89f6772301/_includes/navbar.html#L5-L9

Change the logo to the full TBI logo.

In order to update code on your local computer:

1. clone the repository using github desktop
2. install ruby
3. bundle install
4. bundle exec jekyll serve
5. In browser, browse to http://localhost:4000
6. When satisfied with changes, commit and push to main branch.

@jpylvanainen Step 2 might be difficult - I can help you with setting that up.

Checkout the add-current-projects branch and add content to our current projects. Files follow a pattern found in the _posts directory.

These all need` to be markdown files.