Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh documentation architecture + content strategy #1716

Closed
jmduke opened this issue Jul 23, 2023 · 4 comments
Closed

Refresh documentation architecture + content strategy #1716

jmduke opened this issue Jul 23, 2023 · 4 comments

Comments

@jmduke
Copy link
Member

jmduke commented Jul 23, 2023

Content

  • Getting started
    • Registration and setup
    • Importing
    • Building your base
    • Getting a custom domain
    • Hosting
    • Sending
    • Sending your first email
    • Scheduling an email
    • Markdown
    • Share images
    • Billing
  • Advanced features
    • CSS
    • Tags
    • Metadata
    • RSS-to-email
    • Surveys
    • Paid subs
    • Multiple newsletters
    • Automations
    • Teams
    • Dedicated IP
    • Comments
  • Tutorials
    • Automations sequences
    • Collecting names
    • Customizing list views
    • Drafting emails via the API
    • Scheduling emails via the API
  • Dreamhost
  • Migration guides
    • AWeber
    • Benchmark
    • Campaign Monitor
    • CC
    • ConvertKit
    • EmailOctopus
    • FeedBlitz
    • Mailchimp
    • Mailcoach
    • Mailerlite
    • Moosend
    • Revue
    • Substack
    • Tinyletter
  • API
    • Emails
    • Subscribers
    • Changelog
    • Tags
    • Images
    • Newsletters
    • Exports
    • Bulk actions
    • Automations
    • Comments
  • Integrations
    • Blogger
    • Carrd
    • Discord
    • Duda
    • Fathom
    • Framer
    • Linktree
    • Plausible
    • Stripe
    • Wordpress
  • Esoterica
  • Kudos
  • Affiliate
  • Subscriber referrals
  • Glossary
  • Template variables
  • Automations reference
  • Privacy
  • Data exports
  • Offboarding
  • Law enforcement
  • Screen reader

Tasks

  • Really implement search
  • Add description metadata to pages
  • Add sticky footer with copyright and social links
  • Add analytics
  • Lightbox
  • Video support (e.g. /share-images)
  • iFrame / loom support (e.g. /blogger)
  • Add anchor support to enum lists, so we can e.g. link to /event-types#subscriber.created
  • Add tracking information for searches
  • Add code-highlighting to Markdoc
  • Allow collapsing overlong code samples
  • Add basic table component
  • Add link to buttondown.email application
  • Update TypeScript code example to use fetch (and name it "JavaScript")
  • Automatically run npm run search-index
  • Sentry instrumentation for measuring search times
  • Loading state for search
  • Dedupe "Introduction" in search
  • Add anchors to h1/h2/etc tags
  • Show a mini table of contents on the right
  • Mobile-optimize

Inspo

@jmduke
Copy link
Member Author

jmduke commented Mar 27, 2024

  • Better empty state / no results state in search — it should prompt folks to email us or file a ticket if they can't find what they're looking for

@smonette
Copy link

smonette commented Mar 28, 2024

We may need a few replacement snippets for old-docs components:

  • <MultiLanguageSnippet> Primarily in Tutorials.
  • <Playground> Primarily in Tutorials
  • <ConditionallyRender> Only on building-your-subscriber-base atm
  • <Notice> Across many article types

@smonette
Copy link

  • The "/using-markdown" page needs a way to display output examples.

Old docs screenshot

@jmduke
Copy link
Member Author

jmduke commented Mar 30, 2024

@jmduke jmduke closed this as completed May 3, 2024
@jmduke jmduke unpinned this issue May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Q2 2024 (April — June)
Status: Done
Development

No branches or pull requests

3 participants