1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
`GSP` (pronounced _gee ess pee_) is a transpiler to convert a nicer to write and
more human-friendly syntax into valid HTML. Writing HTML can be made more
bearable using things like Emmet, but it’s still not great, and the syntax is
far too bloated, visually polluting your documents.
`GSP` will never support templating or other useless features. If you need
support for such things, just use a programming- or macro language such as
Python or M4.
## Why Not Use Pug or [INSERT LANGUAGE HERE]
Simply put, they are all trash. Pug has decent syntax but requires you use
JavaScript. All the others fall for the same kind of problem. As far as I
could find, there is no pre-GSP transpiler from good syntax to HTML that works
as just one binary you call on some files. All options force you into needing
to write JavaScript/Ruby/etc. scripts, which just isn’t good enough.
## Syntax Example
```gsp
html lang="en" {
head {
meta charset="UTF-8"
meta name="viewport" content="width=device-width, initial-scale=1.0"
link href="/favicon.svg" rel="shortcut icon" type="image/svg"
link href="/style.svg" rel="stylesheet"
title {-My Website Title}
}
body {
p #my-id {- This is a paragraph with the id ‘my-id’ }
p .my-cls {- This is a paragraph with the class ‘my-cls’ }
p
#some-id
.class-1
.class-2
key-1="value-1"
key-2 = "value-2"
{-
This paragraph has an ID, two classes, and two additional attributes. GSP
allows us to use the ‘#ident’ and ‘.ident’ syntaxes as shorthands for
applying IDs, and classes. This is a text node, so nothing is being
interpreted as GSP nodes, but we can include them inline if we want. As
an example, here is some @em {-emphatic} text. Your inline nodes can also
have attributes @em #id .cls {-just like a regular node}.
}
}
}
```
## Why The Name GSP?
I was originally inspired by Pug, but my dog is a GSP, not a pug.
|
