Wrap everything in a theme provider to allow for dark theme etc..

Need to make the logo smaller in normal web-browsers but keep it the current size for mobile.

Output from build:

12:27:29 AM: warning Query takes too long:
12:27:29 AM: File path: /opt/build/repo/src/templates/blog-post.js
12:27:29 AM: URL path: /notes/INF143/
12:27:29 AM: Context: {
12:27:29 AM:     "slug": "/notes/INF143/",
12:27:29 AM:     "previous": {
12:27:29 AM:         "fields": {
12:27:29 AM:             "slug": "/notes/INF226/"
12:27:29 AM:         },
12:27:29 AM:         "frontmatter": {
12:27:29 AM:             "title": "INF226 notes - Software Security"
12:27:29 AM:         }
12:27:29 AM:     },
12:27:29 AM:     "next": {
12:27:29 AM:         "fields": {
12:27:29 AM:             "slug": "/other/helloworld/"
12:27:29 AM:         },
12:27:29 AM:         "frontmatter": {
12:27:29 AM:             "title": "Hello World"
12:27:29 AM:         }
12:27:29 AM:     }
12:27:29 AM: }
12:27:34 AM: warning Query takes too long:
12:27:34 AM: File path: /opt/build/repo/src/templates/blog-post.js
12:27:34 AM: URL path: /notes/INF142/
12:27:34 AM: Context: {
12:27:34 AM:     "slug": "/notes/INF142/",
12:27:34 AM:     "previous": {
12:27:34 AM:         "fields": {
12:27:34 AM:             "slug": "/notes/DAT103/"
12:27:34 AM:         },
12:27:34 AM:         "frontmatter": {
12:27:34 AM:             "title": "DAT103 notes"
12:27:34 AM:         }
12:27:34 AM:     },
12:27:34 AM:     "next": {
12:27:34 AM:         "fields": {
12:27:34 AM:             "slug": "/notes/INF226/"
12:27:34 AM:         },
12:27:34 AM:         "frontmatter": {
12:27:34 AM:             "title": "INF226 notes - Software Security"
12:27:34 AM:         }
12:27:34 AM:     }
12:27:34 AM: }
12:27:34 AM: warning Query takes too long:
12:27:34 AM: File path: /opt/build/repo/src/templates/blog-post.js
12:27:34 AM: URL path: /notes/DAT103/
12:27:34 AM: Context: {
12:27:34 AM:     "slug": "/notes/DAT103/",
12:27:34 AM:     "previous": {
12:27:34 AM:         "fields": {
12:27:34 AM:             "slug": "/notes/inf102/"
12:27:34 AM:         },
12:27:34 AM:         "frontmatter": {
12:27:34 AM:             "title": "INF102 notes"
12:27:34 AM:         }
12:27:34 AM:     },
12:27:34 AM:     "next": {
12:27:34 AM:         "fields": {
12:27:34 AM:             "slug": "/notes/INF142/"
12:27:34 AM:         },
12:27:34 AM:         "frontmatter": {
12:27:34 AM:             "title": "INF142 notes - Eksamensforberedelse"
12:27:34 AM:         }
12:27:34 AM:     }
12:27:34 AM: }

Currently the card component is structured poorly. We can make the title into props and pass them into the card component like so
<Card title={node.frontmatter.title} /> etc

This means that the card components itself can have more styling options according to this design:

We want a color in the top right corner of the card to make it possible to easily see the different types of posts on the all posts page.

There is a nice little guide here on how to restructure the code in blogpostCard component: https://medium.com/better-programming/build-a-reusable-responsive-card-component-with-styled-components-3ca14933f7e5

On mobile you get a sideways scrollbar on the whole page when you have wide tables. Need to figure out a way to make them scrollable sideways so it doesn't affect the whole page.

@sondr3 suggested creating a authors.yml or similar file in #67 (comment) with further author information and the possibility to link to custom work and such, and I think it's a good idea so I made it an issue.

We could for example add a link on the author name to the file if information exist, or add it as a drop down or something to clicking on an author.

Need a review of accessibility features. I dont know if headings have the right labels if they have one. Can we tab through the website? Does the tab wording make sense?

We need to document how to make pull requests. How to write markdown files. What our markdown files support etc.

This might be good for people who just want to try and see if you are able to make some changes to this website. Have something you want to talk about with other students? Make a PR and post your info on this website. We would like to hear your opinion, this website is opensource, so go ahead, we want your input.

We need to set up proper contributions, licence, build info.

We want to be able to share lesesalen links with some flair to draw more users in. I have no idea how that works, so someone take a look at this please ❤️

Table of contents is wider than the screen width if you have large headings. Might only affect gatsby-develop. Worth investigating.

We need a table of contents menu for large markdown files on mobile. Currently we have none.

Card component should render author information. To do that we need to make author information available through metadata in the .md/.mdx files.

Vi bør starte å sette opp styled components så raskt som mulig. For der er en litt spesiell struktur ved det. Etter kvart som vi får mange komponenta så kan vi dra ut komponenta i et eget "komponentbibliotek" slik at dette repoet ikkje blir overfyllt med komponenta.

Slik bør det sjå ut inne i src mappa vår.

Inne i components mappa bør vi ha det slik:

Du kan sjå korleis dette er gjort her: https://github.com/mrboen94/aasgard/tree/master/src/components
eller på dokumentasjonen til styled components. Det er index filene som eksportera kvar komponent, og då kan du importere dei i toppen av fila slik at du ikkje får kode som dette:

Men meir som dette:

<StyledDiv>
      <h1>Velkommen til lesesalen!</h1>
      <p>Det beste sted på jord...</p>
</StyledDiv>

We probably want to be able to click on "notes" to view notes, without having to scroll back down on the page. Essentially locking the scroll position at the navbar. Such that the header logo will not take up space at the top and annoy people whenever they click links.

Rockwell looks real nice, but does not work on every device. Need suggestions please.
Add screenshots to this issue and we will put it to a vote 🙇‍♂️

Create your first pullrequest and join the hacktoberfest bonanza!

this does not work

this works

Do we want to fix this? (Probably not, as you want only one heading in a markdown file according to the docs.

We need a new logo to use as a favico. Make a pr with your suggestion.