1import { League_Spartan } from "next/font/google";
2import Image from "next/image";
3import Link from "next/link";
4import { SubscribeButton } from "./ui/subscribe-button";
5
6const league_spartan = League_Spartan({
7  subsets: ["latin"],
8  weight: ["400", "700"],
9});
10
11export default function Home() {
12  return (
13    <div
14      className={`${league_spartan.className} blog-root min-h-screen grid place-items-center`}
15    >
16      <div className={`w-full max-w-160 px-4 sm:px-8 py-4`}>
17        <div className="mb-4">
18          <Image
19            className="dark:invert"
20            src="/gitdot-long-black.svg"
21            alt="gitdot logo"
22            width={120}
23            height={57}
24            preload
25          />
26        </div>
27        <div className="mb-4">
28          <p className="font-semibold text-lg">1. What is gitdot?</p>
29          <p>
30            A better GitHub. <br />
31            An opinionated tool for quality open-source software.
32          </p>
33        </div>
34        <div className="mb-4">
35          <p className="font-semibold text-lg">2. Who is gitdot for?</p>
36          <p>
37            Open-source maintainers. <br />
38            People who see code as more than a means to an end, but as a craft
39            to perfect. The software they build serves the world &mdash; but the
40            software they use doesn&apos;t serve them.
41          </p>
42        </div>
43        <div className="mb-4">
44          <p className="font-semibold text-lg">
45            3. What problem does gitdot solve?
46          </p>
47          <p>
48            A monopoly. <br />
49            Open-source software only has one competitive platform: GitHub. And
50            while GitHub <i>is</i> an impressive product, we also know that a
51            lack of competition enables degradation over time. There&apos;s a
52            few pain points we&apos;re keenly aware of (e.g., CI) and make it
53            our mission to build a better open-source alternative.
54          </p>
55        </div>
56        <div className="mb-4">
57          <p className="font-semibold text-lg">
58            4. What features will gitdot have?
59          </p>
60          <ul className="mb-2">
61            <li>• A hyper-performant Git server written in Rust.</li>
62            <li>
63              • A sane CI/CD platform that is secure by design and locally
64              testable.
65            </li>
66            <li>
67              • An issue tracker designed to serve the maintainer, not the
68              submitter.
69            </li>
70          </ul>
71          <p>
72            We will not have feature parity, but from the get go, our product
73            will be reliable. <br />
74            It will stink of quality &mdash; and deliver a superior experience
75            for a handful of customers.
76          </p>
77        </div>
78        <div className="mb-4">
79          <p className="font-semibold text-lg">
80            5. What features will gitdot not have?
81          </p>
82          <ul className="mb-2">
83            <li>• No AI copilot.</li>
84            <li>• No vanity stars.</li>
85            <li>• No free private repos.</li>
86          </ul>
87          We view AI as an implementation detail, not as a feature. We also
88          question some of the paradigms present in open-source and ask whether
89          features like stars truly serve the maintainer. And finally, public
90          repos will be free, but private repos will be paid for.
91          <br />
92        </div>
93        <div className="mb-4">
94          <p className="font-semibold text-lg">6. When will gitdot be ready?</p>
95          <p>
96            March 31st, 2026. <br />
97            Every week, we will publish a developer log to detail not only our
98            progress, but our thinking in full. These will be strikingly
99            forthright; we want the <i>why</i> behind our product decisions to
100            be critiqued and understood.
101          </p>
102        </div>
103
104        <p>
105          We recognize that we&apos;re making some bold claims here and
106          we&apos;re not so naive as to think this will be easy. Building
107          software is hard &mdash; but it is simply what we love doing.
108        </p>
109        <p>&mdash;baepaul & mikkelk.</p>
110
111        <div className="pt-3 flex justify-end gap-1">
112          <SubscribeButton />
113          <span>•</span>
114          <Link href="/week" className="underline cursor-pointer h-5">
115            logs
116          </Link>
117        </div>
118      </div>
119    </div>
120  );
121}
122