Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.2%) to scientific vocabulary
Keywords
Repository
Personal website built in Gatsby 5
Basic Info
- Host: GitHub
- Owner: portableant
- License: mit
- Language: JavaScript
- Default Branch: main
- Homepage: https://museologi.st
- Size: 1.69 GB
Statistics
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 0
Topics
Metadata Files
README.md
Personal website
This is a personal website created using GatsbyJS (current) and React. I have a blog that is updated very sporadically, and a portfolio on research and work projects.
It is a pretty simple system, powered off markdown files, pulling remote images occasionally and using a few plugins to render maps and iframed content.
I use:
- LeafletJS for maps
- Sketchfab embeds for 3d models
- Bootstrap 5.3 for styling
- Graphql for querying the markdown files
Text and image content is stored within the content folder, with each section having its own folder.
Images are stored in the content/images folder, with each year having its own folder. Some video is rendered
directly, but most is embedded from YouTube.
Development and deployment
Testing and building for this system is pretty easy, just follow the instructions below.
:wrench: Development
To run this system locally for development, you will need to have NodeJS installed.
Once you have that, you can run:
shell
npm install
gatsby develop
:hammer: Building
To build for production, run:
shell
gatsby build
To test the build locally, run:
shell
gatsby serve
:rocket: Deployment
To deploy to github pages, I use the following command:
shell
npm run deploy
This aliases to gh-pages -d public and will deploy the site to the gh-pages branch of the repository.
:mechanical_arm: Automation via actions
This site is automatically built and deployed using GitHub actions. The workflow is in .github/workflows/deploy-on-commit.yml and
is triggered on push to the main branch. Recently this started to fail with this error, which I found hard to track down:
ERR! npm ERR! command sh -c husky install
I have added an extra step to install husky and correct permissions.
yaml
- name: Set up Gatsby
run: |
npm install husky -g
npx husky install
chmod +x .husky/*
npm install -D @playwright/test@latest
npx playwright install
npm install --verbose
License
The code for this site is licensed under the MIT license, which you can find in the LICENSE file. The content for this site is CC0 licensed, unless otherwise stated (some images will have stronger licenses, but I will try to make this clear in the post itself).
Owner
- Name: Daniel Pett
- Login: portableant
- Kind: user
- Location: Hertfordshire
- Website: https://museologi.st
- Twitter: dejpett
- Repositories: 17
- Profile: https://github.com/portableant
I work with technology, mainly for museums, archaeology and heritage organisations - #R #PHP #Gatsby #Python #Jekyll #React and more
GitHub Events
Total
- Delete event: 10
- Issue comment event: 9
- Push event: 146
- Pull request review comment event: 2
- Pull request review event: 2
- Pull request event: 21
- Create event: 9
Last Year
- Delete event: 10
- Issue comment event: 9
- Push event: 146
- Pull request review comment event: 2
- Pull request review event: 2
- Pull request event: 21
- Create event: 9
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 0
- Total pull requests: 25
- Average time to close issues: N/A
- Average time to close pull requests: about 1 month
- Total issue authors: 0
- Total pull request authors: 2
- Average comments per issue: 0
- Average comments per pull request: 0.44
- Merged pull requests: 6
- Bot issues: 0
- Bot pull requests: 24
Past Year
- Issues: 0
- Pull requests: 8
- Average time to close issues: N/A
- Average time to close pull requests: about 1 month
- Issue authors: 0
- Pull request authors: 2
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 4
- Bot issues: 0
- Bot pull requests: 7
Top Authors
Issue Authors
Pull Request Authors
- dependabot[bot] (32)
- portableant (1)