Skip to content

Conversation

@LePhenix47
Copy link

Description:

I made some changes to the HTML header of the SPWN documentation website to improve its SEO and accessibility.

Specifically, I updated the meta tags to include a proper description, title, and Open Graph tags, and I added missing elements such as the page icon.
These changes make it easier for search engines to crawl and index the website.

Changes made:

New and improved HTML <head> tag

<head>
  <!-- Meta tags-->
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
  <meta name="viewport"
    content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0">
  <meta property="description" content="SPWN is a programming language that compiles to Geometry Dash levels. This means that you can create levels not only by using the visual representation in the GD-editor, but also by using a
    verbal and abstracted representation. This is particularly useful for using GD triggers, which are not suited for
    the graphical workflow of the in-game editor, especially if you want to make complicated stuff." />

  <!--   Themes   -->
  <meta content="#72cf5f" data-react-helmet="true" name="theme-color">
  <meta property="theme-color" content="#72cf5f">

  <!-- Open Graph     -->
  <meta property="og:type" content="website" />
  <meta property="og:url" content="https://spu7nix.net/spwn" />
  <meta property="og:title" content="SPWN Documentation" />
  <meta property="og:description" content="SPWN is a programming language that compiles to Geometry Dash levels. This means that you can create levels not only by using the visual representation in the GD-editor, but also by using a
    verbal and abstracted representation. This is particularly useful for using GD triggers, which are not suited for
    the graphical workflow of the in-game editor, especially if you want to make complicated stuff." />

  <meta property="og:image" content="./assets/spwn_logo_smol.png" />
  <meta property="og:image:width" content="256" />
  <meta property="og:image:height" content="256" />

  <!-- Title -->
  <title>SPWN Documentation</title>

  <!-- Page Icon -->
  <link rel="icon" type="image/png" href="./assets/spwn_logo_smol.png" />

  <!--  Libraries and vendors  -->
  <link rel="stylesheet" href="https://unpkg.com/[email protected]/dist/css/theme-simple-dark.css">
  <link rel="stylesheet" href="//cdn.jsdelivr.net/npm/docsify-sidebar-collapse/dist/sidebar.min.css" />


  <!-- CSS -->

  <style>...</style>
</head>

@SpeckyYT
Copy link
Contributor

SpeckyYT commented May 6, 2023

connor

@LePhenix47
Copy link
Author

Images to for proof (taken from the discussion #38) :

Example from Mozilla Firefox:
image

Another one from Brave:
image

@ggodpl
Copy link

ggodpl commented May 6, 2023

i hope this gets merged, although it wont be that suprising if it doesnt since sputnix doesnt really pay much attention to docs

@LePhenix47
Copy link
Author

connor

image

Specky ciao, fa un bel po' di tempo che non ci siamo visti!

Come stai e anche cosa fai quì?

@SpeckyYT
Copy link
Contributor

SpeckyYT commented May 6, 2023

connor

image

Specky ciao, fa un bel po' di tempo che non ci siamo visti!

Come stai e anche cosa fai quì?

Ciao, io sto bene. Faccio parte della community di SPWN già da un pezzo, e sono abbastanza attivo in essa. Proprio oggi ho iniziato a programmare Pacman in SPWN 😂

@sertdfyguhi
Copy link
Contributor

balls

@itsmebombie
Copy link

⚽️

@m1kadev
Copy link
Contributor

m1kadev commented May 7, 2023

tags ??

@neeko-cat
Copy link

shouldn't the favicon use a different format? @LePhenix47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants