『#142 – Building a Portfolio Site When You’re Blind (Plus Browser Tab Survival)』のカバーアート

#142 – Building a Portfolio Site When You’re Blind (Plus Browser Tab Survival)

#142 – Building a Portfolio Site When You’re Blind (Plus Browser Tab Survival)

無料で聴く

ポッドキャストの詳細を見る

このコンテンツについて

 Show notes In this episode (TW142): Michael and Damashe follow up on VoiceOver weirdness, then dig into listener Callum’s question: how to build a portfolio site (with a blog) when you’re blind and do not have strong visual design context. They compare platforms, talk themes and hosting, and share a bunch of practical workflow tips for browsing, tabs, and keeping projects from turning into endless rabbit holes. Topics we covered Recording workflow: Cleanfeed vs Reaper, and why Reaper habits stick even when you deliver the Cleanfeed track.VoiceOver volume oddities: how settings can get weird, and why “start from scratch” sometimes helps (even if it does not explain the root cause).Callum’s website question: portfolio + blog, accessible building, and design confidence without sighted visual feedback. Platform options and tradeoffs: Squarespace as a “simple builder” option (with a note about past backend accessibility issues and the hope that it has improved). Google Sites as a low-cost, template-driven option (with less flexibility and potential domain-setup friction).WordPress as the flexible option, but possibly overkill depending on goals. WordPress specifics: The block editor (Gutenberg) has improved, but it can still feel clunky. You can use a single “classic” style block or approach to avoid fighting the full block workflow.Theme recommendation: GeneratePress (lightweight and accessible).Using AI tools to help choose color palettes and layout decisions (especially with accessibility in mind).Tip: use AI to produce CSS, then apply it globally with a “site-wide CSS” plugin or customizer area instead of pasting code everywhere. Hosting and infrastructure talk (high-level): Shared hosts mentioned: DreamHost, Namecheap, RackNerd. VPS options mentioned: DigitalOcean, Linode (Akamai), and a note that Vultr’s interface can be rough.“Build your own server” is possible, but often more work than Callum needs. Local development and tooling: Local WP for testing and experimenting without breaking a live site. WP-CLI for command-line WordPress management.Magic-link login workflows and why they can be annoying in practice.Passkeys and Auth0 as an advanced direction (with a reminder: that is beyond beginner setup). Browser workflow wins (Mac): Switching tabs and recovering when you accidentally end up on a blank “start page” tab. Reopening a tab/window you closed by mistake.Why multiple windows can still be useful even if you love tabs. Search and platforms: Damashe’s take on Kagi and why Google search results feel worse than they used to. YouTube as a learning tool, and why ads are pushing people toward Premium.Mastodon + the “bot” account that posts links you forget to add to show notes.Threads and the fediverse: hopes for better cross-platform hashtag visibility.Scheduling: exploring a weekday recording night to keep Monday releases consistent without Sunday crunch. Listener question Callum: building a portfolio site as a blind creator, plus blogging, plus choosing a platform and making it look “clean” without visual design instincts. Get in touch Email: feedback@technicallyworking.show Mastodon: Michael: @payown@dragonscave.space Damashe: @demashe@technically.socialThe bot: @tw@technically.socialHashtag: #TechnicallyWorking (capital T and W if you want) 3 Mastodon posts (ready to paste) Post 1 TW142 is out. Callum asked a big one: how do you build a portfolio site (and blog) when you’re blind and don’t have strong visual design context? We talk Squarespace vs Google Sites vs WordPress, plus how AI can help with colors, layout, and CSS. #TechnicallyWorking Post 2 If you’ve ever closed windows and “lost” tabs, TW142 has a few shortcuts that might save you. Cmd+W (tab), Cmd+Shift+W (window), Cmd+Shift+T (bring it back), and tab switching tricks we somehow missed for years. #TechnicallyWorking Post 3 We also wander into Kagi vs Google search, YouTube as a learning tool (and the ad problem), and why picking a weekday recording night might keep Monday releases consistent without the Sunday editing sprint. Feedback welcome: feedback@technicallyworking.show #TechnicallyWorking Episode image Alt text: A simple black-and-white graphic summarizing TW142: Callum’s website question, platform choices (WordPress, Squarespace, Google Sites), using AI for design/CSS help, key Mac tab shortcuts, and tools discussed like Local WP, WP-CLI, Kagi, and YouTube. Download the image Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/ffbe69ff-60c1-4e14-ac1a-8ca43e1e5309 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.
まだレビューはありません