@micropage-sh/cli 2.0.0 → 2.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,130 @@
1
+ [site]
2
+ title: Slab Studio
3
+ description: Brand, digital, and motion design for companies that want to stand out
4
+ logo: <- logo.svg
5
+ favicon: <- favicon.svg
6
+ colors:
7
+ primary: #111111
8
+ secondary: #333333
9
+ danger: #ff6b35
10
+
11
+ [site.dark]
12
+ colors:
13
+ primary: #f5f5f5
14
+ secondary: #cccccc
15
+
16
+ [nav]
17
+ Work -> /
18
+ Studio -> /studio
19
+ Contact -> /contact
20
+
21
+ [footer]
22
+ /// section bg:dark text:light
23
+
24
+ col:
25
+ h5: SLAB STUDIO
26
+ p: Brand — Digital — Motion
27
+ p: Brooklyn, New York
28
+
29
+ col:
30
+ link: LinkedIn -> https://linkedin.com
31
+ link: Dribbble -> https://dribbble.com
32
+ link: Instagram -> https://instagram.com
33
+
34
+ col:
35
+ p: New projects: hello@slabstudio.co
36
+ p: Press: press@slabstudio.co
37
+
38
+
39
+ [Work -> /]
40
+
41
+ /// section align:center
42
+ h1: We make things look like they mean it.
43
+ p: Slab Studio is a seven-person brand and digital studio. We work with founders and creative directors who know what they want and need a team that can build it.
44
+
45
+ /// section
46
+ h2: Selected projects
47
+
48
+ col:
49
+ h3: Cinder — Brand Identity
50
+ p: End-to-end identity for a B2B fintech: wordmark, color system, motion guidelines, and a component library used across three product surfaces.
51
+ small: Fintech · 2024
52
+
53
+ col:
54
+ h3: Waypoint — Campaign
55
+ p: Product launch campaign for a logistics SaaS — visual language, video direction, and a microsite that converted at 4.2%.
56
+ small: Logistics · 2024
57
+
58
+ col:
59
+ h3: Olive & Thread — Packaging
60
+ p: Rebranded a sustainable fashion label from logo to hangtag to e-commerce photography direction.
61
+ small: Fashion · 2023
62
+
63
+ /// section bg:muted
64
+ h2: More work
65
+
66
+ col:
67
+ h3: Nova Health — Digital Product
68
+ p: Design system and patient-facing app UI for a telehealth platform. Accessibility-first, WCAG 2.1 AA.
69
+ small: Health tech · 2023
70
+
71
+ col:
72
+ h3: Paloma Records — Art Direction
73
+ p: Album artwork, lyric video direction, and social templates for four releases.
74
+ small: Music · 2023
75
+
76
+ col:
77
+ h3: Fieldwork Brewing — Web
78
+ p: Responsive marketing site with custom animations, tap room finder, and e-commerce integration.
79
+ small: Food & beverage · 2022
80
+
81
+
82
+ [Studio -> /studio]
83
+
84
+ /// section
85
+ h1: About Slab
86
+
87
+ col:
88
+ p: We started Slab in 2018 after leaving larger agencies because we wanted to do fewer projects, better. Seven people, no junior-to-senior ratio games, no account managers between you and the work.
89
+
90
+ col:
91
+ p: Everyone at Slab touches client work. Our lead designer also codes. Our strategist also writes. That's on purpose.
92
+
93
+ /// section align:center
94
+ h2: How we work
95
+
96
+ col:
97
+ icon: bi bi-chat-square-text
98
+ h3: Discovery
99
+ p: Two-week engagement to align on objectives, audiences, and success criteria before any creative begins.
100
+
101
+ col:
102
+ icon: bi bi-easel
103
+ h3: Creative development
104
+ p: Three rounds of feedback with clear decision points. No endless-revision contracts.
105
+
106
+ col:
107
+ icon: bi bi-box-arrow-up-right
108
+ h3: Handoff
109
+ p: Full source files, a brand guidelines document, and a 30-day support window after launch.
110
+
111
+ /// section bg:dark text:light align:center
112
+ h2: We work with clients who ship.
113
+ p: Not committees. Not approvals-by-committee. Founders, CPOs, and creative directors with the authority to make decisions and the taste to know a good one.
114
+ button: Start a conversation -> /contact
115
+
116
+
117
+ [Contact -> /contact]
118
+
119
+ /// section
120
+ h1: Start a project
121
+ p: Tell us what you're building and why it matters. We'll come back within 48 hours.
122
+
123
+ form: intake
124
+ input: Name*
125
+ input: Email*
126
+ input: Company
127
+ select: Project type [Brand identity, Web design, Campaign, Motion, Product design, Other]
128
+ select: Approximate budget [$20k–$50k, $50k–$100k, $100k+, Not sure yet]
129
+ text: Tell us about the project*
130
+ submit: Send brief
@@ -0,0 +1,158 @@
1
+ [site]
2
+ title: The Long Read
3
+ description: Reporting and essays on technology, cities, and the people who build them
4
+ logo: <- logo.svg
5
+ favicon: <- favicon.svg
6
+ colors:
7
+ primary: #1f2937
8
+ secondary: #374151
9
+ danger: #b91c1c
10
+
11
+ [site.dark]
12
+ colors:
13
+ primary: #f9fafb
14
+ secondary: #e5e7eb
15
+ danger: #ef4444
16
+
17
+ [nav]
18
+ Latest -> /
19
+ Archive -> /archive
20
+ About -> /about
21
+ Subscribe -> /subscribe
22
+
23
+ [footer]
24
+ /// section
25
+
26
+ col:
27
+ h5: THE LONG READ
28
+ p: Published weekly. No ads. Reader-supported.
29
+
30
+ col:
31
+ link: Twitter -> https://twitter.com
32
+ link: RSS -> /feed.xml
33
+ link: Archive -> /archive
34
+
35
+ col:
36
+ p: Tips and story ideas: tips@thelongread.io
37
+ p: Licensing: rights@thelongread.io
38
+
39
+
40
+ [Latest -> /]
41
+
42
+ /// section
43
+ h1: Latest stories
44
+
45
+ col:
46
+ h3: The Fiber Wars
47
+ p: Why three companies are spending $80 billion to wire the same neighborhoods — and who loses when they all pull back.
48
+ small: Infrastructure · 22 min read
49
+
50
+ col:
51
+ h3: What Happened to the Promise of Smart Cities
52
+ p: A decade ago, Sidewalk Toronto was supposed to prove that data could make urban life better. Here's what we learned from its failure.
53
+ small: Cities · 18 min read
54
+
55
+ col:
56
+ h3: The Engineer Who Said No
57
+ p: When Priya Nair refused to ship a feature she thought was dangerous, she lost her job. Two years later, she's not sure she'd do it differently.
58
+ small: Profile · 14 min read
59
+
60
+ /// section bg:muted
61
+ h2: From the archive
62
+
63
+ col:
64
+ h3: The Last Payphone
65
+ p: New York's final payphone came down in May 2022. We spent a day with the crew that removed it.
66
+ small: Cities · 8 min read
67
+
68
+ col:
69
+ h3: Chasing the Algorithm
70
+ p: A content moderation contractor describes 18 months of reading the internet's worst content so you don't have to.
71
+ small: Technology · 26 min read
72
+
73
+ col:
74
+ h3: Where Did the Mid-Size City Go?
75
+ p: Population data tells one story. Walking around Youngstown, Ohio tells another.
76
+ small: Cities · 15 min read
77
+
78
+ /// section bg:danger text:light align:center
79
+ h2: Become a supporting reader.
80
+ p: The Long Read is fully reader-supported. No investors, no brand deals, no tracking. A subscription covers our editorial costs and keeps the site ad-free.
81
+ button: Subscribe — $10/month -> /subscribe
82
+ btn-secondary: Gift a subscription -> /gift
83
+
84
+
85
+ [Archive -> /archive]
86
+
87
+ /// section
88
+ h1: All stories
89
+
90
+ /// section
91
+ h2: Technology
92
+
93
+ col:
94
+ link: The Fiber Wars -> /stories/fiber-wars
95
+ link: Chasing the Algorithm -> /stories/chasing-algorithm
96
+ link: Who Owns the Sidewalk Data? -> /stories/sidewalk-data
97
+ link: The Quiet Monopoly -> /stories/quiet-monopoly
98
+
99
+ /// section
100
+ h2: Cities
101
+
102
+ col:
103
+ link: What Happened to the Promise of Smart Cities -> /stories/smart-cities
104
+ link: The Last Payphone -> /stories/last-payphone
105
+ link: Where Did the Mid-Size City Go? -> /stories/mid-size-city
106
+ link: Living on the Heat Map -> /stories/heat-map
107
+
108
+
109
+ [About -> /about]
110
+
111
+ /// section
112
+ h1: About The Long Read
113
+
114
+ col:
115
+ p: The Long Read was started in 2021 by two journalists who were tired of writing to SEO briefs. We publish one to two pieces a week — long-form reported stories and essays about technology and the built environment.
116
+
117
+ col:
118
+ p: We have no investors, no editorial board, and no algorithmic pressures. If something takes six months to report properly, we take six months.
119
+
120
+ /// section align:center
121
+ h2: Our editorial standards
122
+
123
+ col:
124
+ icon: bi bi-incognito
125
+ h3: No tracking
126
+ p: We collect no analytics, no behavioral data, no ad pixels. Your reading is your own.
127
+
128
+ col:
129
+ icon: bi bi-journal-check
130
+ h3: Named sources
131
+ p: We don't publish anonymously sourced claims without a documented reason. We always try to give subjects the chance to respond.
132
+
133
+ col:
134
+ icon: bi bi-archive
135
+ h3: Everything stays up
136
+ p: We don't delete stories. If we get something wrong, we publish a correction and leave both up.
137
+
138
+
139
+ [Subscribe -> /subscribe]
140
+
141
+ /// section
142
+ h1: Support independent journalism
143
+ p: Subscribers get all stories in their inbox each week, access to the full archive, and the knowledge that this publication exists because of them.
144
+
145
+ col:
146
+ h3: Monthly
147
+ p: $10 per month. Cancel any time.
148
+ button: Subscribe monthly -> /checkout/monthly
149
+
150
+ col:
151
+ h3: Annual
152
+ p: $90 per year — save $30.
153
+ button: Subscribe annually -> /checkout/annual
154
+
155
+ col:
156
+ h3: Founding reader
157
+ p: $200 per year. Your name in our annual supporters list.
158
+ button: Become a founding reader -> /checkout/founding
@@ -0,0 +1,181 @@
1
+ [site]
2
+ title: Fluxline
3
+ description: Open-source event streaming SDK for TypeScript and Go
4
+ logo: <- logo.svg
5
+ favicon: <- favicon.svg
6
+ colors:
7
+ primary: #0d9488
8
+ secondary: #0f766e
9
+ info: #0891b2
10
+
11
+ [site.dark]
12
+ colors:
13
+ primary: #2dd4bf
14
+ secondary: #14b8a6
15
+
16
+ [nav]
17
+ Home -> /
18
+ Docs -> /docs
19
+ Pricing -> /pricing
20
+ GitHub -> https://github.com
21
+
22
+ [footer]
23
+ /// section bg:dark text:light
24
+
25
+ col:
26
+ h5: FLUXLINE
27
+ p: Open source under Apache 2.0
28
+ link: GitHub -> https://github.com
29
+
30
+ col:
31
+ link: Documentation -> /docs
32
+ link: Changelog -> /changelog
33
+ link: Status -> https://status.fluxline.dev
34
+
35
+ col:
36
+ p: Fluxline is maintained by a small team and community contributors.
37
+ link: Contributing guide -> /contributing
38
+
39
+
40
+ [Home -> /]
41
+
42
+ /// section bg:dark text:light
43
+ h5: OPEN SOURCE · TYPESCRIPT · GO
44
+ h1: Stream events without the boilerplate.
45
+ p: Fluxline is a lightweight SDK for publishing, subscribing to, and replaying ordered event streams. Works with your existing message broker — no new infrastructure required.
46
+
47
+ ////
48
+ html: <pre><code>import { Fluxline } from 'fluxline'
49
+
50
+ const client = new Fluxline({ brokerUrl: process.env.BROKER_URL })
51
+ await client.publish('orders', { id: 'ord_01', total: 49.00 })</code></pre>
52
+
53
+ col:
54
+ button: Get started -> /docs
55
+ btn-secondary: View on GitHub -> https://github.com
56
+
57
+ col:
58
+ p: v1.4.2 · 2.1 kB gzipped · Zero runtime dependencies
59
+
60
+ /// section
61
+ h2: Why Fluxline
62
+
63
+ col:
64
+ icon: bi bi-lightning-charge
65
+ h3: Under 3 kB
66
+ p: The TypeScript client ships at 2.1 kB gzipped. The Go client is a single file you can vendor.
67
+
68
+ col:
69
+ icon: bi bi-arrow-repeat
70
+ h3: Replay from any offset
71
+ p: Seek back to any sequence number and replay events forward. Works with Kafka, NATS, and Redis Streams.
72
+
73
+ col:
74
+ icon: bi bi-shield-check
75
+ h3: Exactly-once delivery
76
+ p: Idempotent producer IDs and consumer group offsets give you strong delivery guarantees out of the box.
77
+
78
+ /// section bg:primary-subtle
79
+ h2: Framework integrations
80
+
81
+ col:
82
+ h3: Next.js / Remix
83
+ p: Server action helpers and route handler bindings. Automatically infer event types from your Zod schemas.
84
+
85
+ col:
86
+ h3: Hono & Fastify
87
+ p: Middleware that turns any route into an event source. Streaming responses with backpressure handling.
88
+
89
+ col:
90
+ h3: Go net/http
91
+ p: Handler adapter for standard Go HTTP servers. No generics gymnastics — just plain functions.
92
+
93
+
94
+ [Docs -> /docs]
95
+
96
+ /// section
97
+ h1: Getting started
98
+
99
+ /// section bg:muted
100
+ h2: Installation
101
+
102
+ ////
103
+ html: <pre><code># TypeScript / Node
104
+ npm install fluxline
105
+
106
+ # Go
107
+ go get github.com/fluxline/fluxline-go</code></pre>
108
+
109
+ /// section
110
+ h2: Quick start
111
+
112
+ col:
113
+ h3: 1. Create a client
114
+ p: Initialize with your broker URL and an optional namespace prefix. Credentials are read from environment variables by default.
115
+
116
+ col:
117
+ h3: 2. Define your events
118
+ p: Use the TypeScript generic or Go struct tag to attach a schema. Fluxline validates before publishing and narrows the type on receive.
119
+
120
+ col:
121
+ h3: 3. Publish and subscribe
122
+ p: publish() is fire-and-forget with an optional ack callback. subscribe() returns an async iterator or a channel, depending on the language.
123
+
124
+ /// section
125
+ h2: Configuration reference
126
+
127
+ col:
128
+ h3: brokerUrl
129
+ p: Required. WebSocket or TCP URL for your message broker.
130
+
131
+ col:
132
+ h3: namespace
133
+ p: Optional string prefix applied to all stream names. Useful for multi-tenant deployments.
134
+
135
+ col:
136
+ h3: maxRetries
137
+ p: Default 3. How many times to retry a failed publish before raising an error.
138
+
139
+ col:
140
+ h3: ackTimeout
141
+ p: Default 5000 ms. Time to wait for a broker ack before treating the publish as failed.
142
+
143
+
144
+ [Pricing -> /pricing]
145
+
146
+ /// section align:center
147
+ h1: Free to start. Pay as you grow.
148
+ p: All plans include the full SDK feature set. Pricing is based on monthly event volume.
149
+
150
+ col:
151
+ h3: Open Source
152
+ p: Self-hosted, unlimited events, community support.
153
+ p: Always free.
154
+ button: Get started -> /docs
155
+
156
+ col:
157
+ h3: Cloud
158
+ p: Managed broker, 10M events/month included.
159
+ p: $49 / month
160
+ button: Start free trial -> /trial
161
+
162
+ col:
163
+ h3: Enterprise
164
+ p: Dedicated cluster, SLA, audit logs, SSO, custom retention.
165
+ p: Custom pricing
166
+ button: Talk to us -> /contact
167
+
168
+ /// section bg:muted
169
+ h2: Frequently asked questions
170
+
171
+ col:
172
+ h3: Can I use my own Kafka cluster?
173
+ p: Yes. The SDK is broker-agnostic. The managed Cloud tier runs NATS JetStream under the hood, but the OSS version works with any NATS, Kafka, or Redis Streams backend.
174
+
175
+ col:
176
+ h3: Is there a free trial for Cloud?
177
+ p: Cloud plans include a 14-day trial with no credit card required. You'll get 10M events to test with before you're charged.
178
+
179
+ col:
180
+ h3: What counts as an event?
181
+ p: Any publish() call that reaches the broker. Failed attempts before retry exhaustion are not counted.
@@ -0,0 +1,171 @@
1
+ [site]
2
+ title: Frontline Summit
3
+ description: The annual conference for product, design, and engineering leaders
4
+ logo: <- logo.svg
5
+ favicon: <- favicon.svg
6
+ colors:
7
+ primary: #e3236d
8
+ secondary: #b01a55
9
+ info: #7c3aed
10
+
11
+ [site.dark]
12
+ colors:
13
+ primary: #f0457e
14
+ secondary: #e3236d
15
+
16
+ [nav]
17
+ Home -> /
18
+ Schedule -> /schedule
19
+ Speakers -> /speakers
20
+ Register -> /register
21
+
22
+ [footer]
23
+ /// section bg:dark text:light
24
+
25
+ col:
26
+ h5: FRONTLINE SUMMIT 2025
27
+ p: March 12–14, 2025
28
+ p: Chicago, IL — The Civic Ballroom
29
+
30
+ col:
31
+ link: Code of conduct -> /coc
32
+ link: Sponsorship -> /sponsors
33
+ link: Contact -> /contact
34
+
35
+ col:
36
+ p: Questions? Email us at hello@frontlinesummit.com
37
+
38
+
39
+ [Home -> /]
40
+
41
+ /// hero bg:primary text:light
42
+ h1: Build what comes next.
43
+ p: Frontline Summit brings together 1,200 product, design, and engineering leaders for three days of talks, workshops, and honest conversations about how software gets made.
44
+ p: March 12–14, 2025 · Chicago
45
+ button: Register now -> /register
46
+ btn-secondary: View schedule -> /schedule
47
+
48
+ /// section
49
+ h2: This year's tracks
50
+
51
+ col:
52
+ icon: bi bi-cpu
53
+ h3: Platform Engineering
54
+ p: Developer experience, internal platforms, and the golden path between speed and stability.
55
+
56
+ col:
57
+ icon: bi bi-palette
58
+ h3: Product Design at Scale
59
+ p: Design systems, accessibility debt, and leading creative work in a fast-moving org.
60
+
61
+ col:
62
+ icon: bi bi-people
63
+ h3: Leadership & Culture
64
+ p: Hiring, retention, psychological safety, and building teams that survive hypergrowth.
65
+
66
+ /// section bg:muted
67
+ h2: Formats
68
+
69
+ col:
70
+ h3: Keynotes
71
+ p: Six 45-minute talks from practitioners who've shipped things that mattered.
72
+
73
+ col:
74
+ h3: Deep-dive workshops
75
+ p: Half-day sessions capped at 30 attendees. Hands-on, no slides, all practice.
76
+
77
+ col:
78
+ h3: Open hallway track
79
+ p: Unscheduled space for spontaneous conversations. Some of the best talks happen here.
80
+
81
+
82
+ [Schedule -> /schedule]
83
+
84
+ /// section
85
+ h1: Schedule at a glance
86
+
87
+ /// section bg:primary-subtle
88
+ h2: Day 1 — March 12
89
+
90
+ col:
91
+ h3: 9:00 am — Opening keynote
92
+ p: "The Decade of the Platform" — keynote by Mira Okonkwo, VP Engineering at Lattice.
93
+
94
+ col:
95
+ h3: 11:00 am — Workshop block A
96
+ p: Choose from: Incident culture, Design sprints for complex features, Staff eng career paths.
97
+
98
+ col:
99
+ h3: 2:00 pm — Lightning talks
100
+ p: Eight 10-minute talks from speakers selected from the open CFP.
101
+
102
+ /// section
103
+ h2: Day 2 — March 13
104
+
105
+ col:
106
+ h3: 9:30 am — Keynote
107
+ p: "Shipping with Confidence" — how Vercel restructured their deploy pipeline and reduced rollbacks by 60%.
108
+
109
+ col:
110
+ h3: 1:00 pm — Panel
111
+ p: "AI in the dev workflow: what's actually working" — four engineering leaders, unfiltered.
112
+
113
+ col:
114
+ h3: 4:00 pm — Unconference
115
+ p: Participant-led sessions. Vote on topics in the morning, run sessions in the afternoon.
116
+
117
+
118
+ [Speakers -> /speakers]
119
+
120
+ /// section align:center
121
+ h1: Featured speakers
122
+
123
+ col:
124
+ h3: Mira Okonkwo
125
+ p: VP Engineering, Lattice
126
+ p: Scaling platform teams from 12 to 120 engineers without losing the culture.
127
+
128
+ col:
129
+ h3: Dev Patel
130
+ p: Staff Engineer, Linear
131
+ p: Real-time sync architecture and the tradeoffs nobody talks about.
132
+
133
+ col:
134
+ h3: Carmen Estrada
135
+ p: Head of Design, Figma
136
+ p: Building a design system that 4,000 designers actually use.
137
+
138
+ /// section
139
+ h2: Call for proposals
140
+
141
+ col:
142
+ p: We select 30% of our program from open CFP submissions. If you've solved a hard problem and want to share it, we want to hear from you.
143
+ button: Submit a proposal -> /cfp
144
+
145
+ col:
146
+ p: CFP closes January 15, 2025. Decisions sent by February 1. Travel and hotel covered for selected speakers.
147
+
148
+
149
+ [Register -> /register]
150
+
151
+ /// section
152
+ h1: Get your ticket
153
+ p: Early-bird pricing ends December 1. Workshop seats are limited and sell out first.
154
+
155
+ col:
156
+ h3: Conference pass
157
+ p: Full three-day access, all keynotes and lightning talks, hallway track.
158
+ p: $799 early bird / $999 standard
159
+ button: Register -> /checkout
160
+
161
+ col:
162
+ h3: Conference + Workshop
163
+ p: Everything in the conference pass plus one half-day workshop of your choice.
164
+ p: $1,199 early bird / $1,499 standard
165
+ button: Register -> /checkout
166
+
167
+ col:
168
+ h3: Team of 5
169
+ p: Five conference passes at a 20% discount. Invoice billing available.
170
+ p: $3,196 (saves $800)
171
+ button: Contact us -> /contact