alpha
Login
or
Join now
alice.pds.demo.boltless.dev
/
core
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
2
Pulls
1
Pipelines
core
/
appview
/
pages
4 folders
5 files
at
92009db2a95e65539b6c2da48b941ceda061cff3
oppiliappan
appview/db: fix up nits with newsletter handlers
3mo ago
92009db2
legal
appview/pages: add a brand page Also some misc. changes to page layouts. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
10 months ago
markup
*: correct typos throughout codebase Fix various misspellings found by the typos tool: - Error messages: Forbiden -> Forbidden, insufficent -> insufficient - Comments and docs: recieve -> receive, acheive -> achieve, etc. - Variable names: Referencs -> References, intialize -> initialize - HTML templates: Unubscribe -> Unsubscribe, explictly -> explicitly - Function names: perferom -> perform Also remove backwards compat code for is_deafult JSON field. Add _typos.toml config for false positives (external APIs, etc.) Signed-off-by: eti <eti@eti.tf>
4 months ago
repoinfo
revert "appview/pages: seo improvements, sitemap, schemae and more" This reverts commit 8fb22cb34756cc2930bb780548d45bde56cdbe65. Signed-off-by: oppiliappan <me@oppi.li>
6 months ago
templates
appview/db: fix up nits with newsletter handlers Signed-off-by: oppiliappan <me@oppi.li>
3 months ago
cache.go
appview/pages: rework caching mechanism instead of loading all templates at once and storing into a map, we now memoize the results of `parse`. the first call to `parse` will require calculation but subsequent calls will be cached. this is simpler to reason about because the new execution model requires us to parse differently for each "base" template that is being used: - for timeline, it is necessary to parse with layouts/base - for repo-index, it is necessary to parse with layouts/base and layouts/repobase in that order the previous approach to loading also had a latent bug: all layouts were loaded atop each other in alphabetical order (order of iteration over the filesystem), and therefore it was not possible to selectively parse and execute templates on a subset of layouts. Signed-off-by: oppiliappan <me@oppi.li>
11 months ago
funcmap.go
appview,knotserver: pref-handle display + identity ingest Lewis: May this revision serve well! <lewis@tangled.org>
3 months ago
funcmap_test.go
appview,knotserver: pref-handle display + identity ingest Lewis: May this revision serve well! <lewis@tangled.org>
3 months ago
htmx.go
appview/settings: add account management UI for tngl.sh users Signed-off-by: Lewis <lewis@tangled.org>
5 months ago
pages.go
appview: persist newsletter signup/dismiss per-user for cross-device hiding the newsletter widget used only localStorage to remember whether a user had signed up or dismissed it, so the cta kept reappearing whenever a user opened tangled on another device or browser. for logged-in users, store the state in a newsletter_preferences table keyed on did with an enum status ('subscribed' | 'dismissed') and the email they gave us. the home and timeline handlers read this row to decide whether to render the widget, and the server-rendered gfi banner widens when the widget is gone so the grid doesn't leave an empty column. resend stays the source of truth for the mailing list itself (sending, bounces, one-click unsubscribes) — the new table only answers the render-time question 'should this did see the widget right now?', which resend cannot cheaply answer because it's keyed on email rather than did and would add a network hop to every timeline render. anonymous visitors keep the localStorage fallback. the client-side 'already dismissed in a past session' path deliberately only calls hide() (not dismiss()) so that a stale localStorage flag can't clobber a subscribed row set from another device. Signed-off-by: eti <eti@eti.tf>
3 months ago