joakimthorsen.github.io

Joa's Website is a personal site hosted on GitHub Pages. The page evidence available shows only a greeting ("Hi") and the phrase "MC Property Encyclopedia," so the site should be treated as a minimal personal homepage rather than a commercial service or product site. If you are looking for a company, store, or official documentation portal, this is not the place to find it.

What the site actually contains

The visible content is very limited. Based on the page evidence:

• Heading: "Hi"
• Excerpt: "Hi MC Property Encyclopedia"

There is no indication of pricing, payment platforms, or a product catalog. The site does not present itself as a business, so you should not assume any commercial offering, account system, or support channel exists.

Who maintains it and how it is hosted

The hostname joakimthorsen.github.io follows GitHub Pages' user-site pattern, which means the site is published from a GitHub account named joakimthorsen. This tells you two useful things:

1. It is a personal project. GitHub Pages user sites are typically maintained by an individual, not an organization with a dedicated support team.
2. The content is likely to change or stay sparse. Personal pages often serve as placeholders, link hubs, or experiments, and they may not be updated regularly.

What "MC Property Encyclopedia" might mean

The only content clue is the phrase "MC Property Encyclopedia." The available evidence does not explain what this refers to, so treat it as a label or section name on the page rather than a confirmed feature. If you arrived expecting an encyclopedia, check whether the page links to it; if no link is visible, the reference may be a placeholder or work in progress.

When this site is useful to you

Practical next steps

• If you need the owner's other work: search GitHub for the joakimthorsen account, since the Pages site is tied to that username.
• If you expected specific content: reload the page and check for links; the visible text is minimal, so any deeper content would need to be linked from it.
• If you need to cite the site: quote only what is visible ("Hi" and "MC Property Encyclopedia") and avoid inferring purpose beyond a personal homepage.

The main takeaway: this is a sparse personal GitHub Pages site. Use it to identify the owner's GitHub presence, not as a source for products, pricing, or detailed reference material.

Joa's Website (joakimthorsen.github.io) currently presents a minimal landing page: the visible content is a short greeting ("Hi") and a single reference to "MC Property Encyclopedia." There is no evidence in the available page data of a navigation menu, sidebar, or link list pointing to other sections. In practice, that means the most reliable way to reach other content is to use the one named reference on the page, or to check whether your view of the page is hiding links that exist in the underlying HTML.

What the homepage actually shows

The page evidence for the site is limited to:

• A heading reading "Hi"
• An excerpt reading "Hi MC Property Encyclopedia"

No additional headings, menus, or navigation links are documented. If you are looking for a directory of pages, a blog index, or an about section, none of these appear in the recorded page content.

Step 1: Check the visible page for links

Open joakimthorsen.github.io in a browser and look at the greeting area. If "MC Property Encyclopedia" is rendered as a hyperlink, clicking it is the intended path to that content. If it appears as plain text, there is no clickable destination on the page itself.

Expected result: either you land on the MC Property Encyclopedia content, or you confirm the page offers no outbound links.

Step 2: Inspect the page source if nothing is clickable

If the page looks empty apart from the greeting, the links may exist in the HTML but not be styled obviously.

1. Right-click the page and choose "View Page Source" (or press Ctrl+U / Cmd+U).
2. Search the source for href= to list every link the page defines.
3. Look for paths such as /mc-property-encyclopedia, /about, or similar.

Expected result: a list of any internal pages the site actually links to. If the search returns no href values beyond stylesheets or scripts, the site genuinely has no other linked pages at this time.

Step 3: Try likely direct URLs

Because the site is hosted on GitHub Pages, content often lives at predictable paths. If the source inspection reveals a path segment, append it to the hostname directly, for example joakimthorsen.github.io/<path>. Only use paths you actually found in the source; guessing arbitrary URLs is unlikely to help and may return a 404.

Common sticking points

• The page looks blank or nearly blank. This is consistent with the recorded content: a greeting and one reference. It is not necessarily a loading error.
• "MC Property Encyclopedia" is not a link. In that case the reference is informational only, and there is no on-site route to further content.
• You expected a blog or portfolio. Nothing in the available page data indicates one exists on this hostname.

What to conclude

If your goal is to browse more of Joa's Website, start with the "MC Property Encyclopedia" reference and the page source check above. If neither yields links, the site currently consists of this landing content alone, and there is no documented navigation to other pages. In that situation, the honest answer is that no other content entry points are available from the homepage.

The "MC Property Encyclopedia" is the only content reference visible on Joa's Website (joakimthorsen.github.io): the page shows the greeting "Hi" followed by the words "MC Property Encyclopedia." The site itself provides no explanation of what the encyclopedia covers, so the label is best treated as a pointer to a resource rather than a described product. To confirm its scope, open the page and follow that reference directly.

What the page actually shows

The visible page evidence is minimal:

• A heading reading "Hi"
• The text "MC Property Encyclopedia"

There are no menus, descriptions, categories, or links documented in the available page evidence. That means you should not assume a topic, format, or level of completeness from the name alone.

How to read the name

The label suggests an encyclopedia-style collection organized around "MC" properties. "MC" is ambiguous on its own, and the site does not define it, so the safest reading is:

• Encyclopedia-style: a reference collection of entries rather than a tutorial or blog.
• "MC" properties: a category the site has not spelled out; the page is the place to check what it means in context.

If you need to know whether "MC" refers to a game, a data format, a modeling tool, or something else, verify it on the page itself rather than inferring from the abbreviation.

What to do next

1. Open joakimthorsen.github.io.
2. Look for the "MC Property Encyclopedia" reference and any link attached to it.
3. Check the linked page's headings and entry list to see what topics it covers.
4. If no link exists, treat the phrase as a title only and look for related pages under the same hostname.

Expected result: you should be able to state what the encyclopedia covers and whether it is a finished resource or a placeholder.

Common sticking points

• Assuming a topic from "MC." The site gives no definition; confirm before relying on it.
• Expecting a full site structure. The page evidence shows only a greeting and the title, so navigation may be absent or undocumented.
• Treating it as a product page. Nothing in the available material indicates pricing, accounts, or downloads; do not assume any of these exist.

In short, the "MC Property Encyclopedia" is the single content reference on Joa's Website, and its actual scope is only verifiable by visiting the page.