TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Knowledge Base Writers / Hugo writers. Share your setup and wisdom

3 点作者 dv35z超过 2 年前
Hey HN crew -<p>I&#x27;m putting together a &quot;local notes --&gt; publishable knowledge-base site&quot; workflow (it&#x27;s a git-versioned Hugo site which sits in an iCloud folder. I&#x27;m using iA Writer as the main writing IDE. When ready to publish (on iPhone&#x2F;iPad), I use Working Copy to commit &amp; push the changes, and then GitLab Pages builds &amp; publishes the site. It&#x27;s a new setup for me - but works pretty well. Happy to share details if anyone is interested in the setup.<p>Questions &#x2F; Issues<p>- How to Cross-link while in the writing flow (e.g. Notion-style linking). What I want to do, is to be able to quickly stub out [[Important Ideas]], and over time expand those entries into pages. But it seems I&#x27;ve got to figure out ways to translate [[ ]] topics into links when publishing out to Hugo. What&#x27;s the best way to do this? I see there are Hugo Shortlinks - but those look like a pain to write out frequently...<p>- Renaming &amp; &quot;shaping&quot; content over time - Sometimes I change the name of a page - I&#x27;d love to be able to update entires all over the site (I believe Obsidian keeps track of file names? Can iA Writer? Right now, when writing, I have no idea when I create a broken link. What&#x27;s the latest on automatic link integrity checkers. Is there a tool which could fail to publish my site if it included a broken link?<p>- How would you recommend adding photos to content? I haven&#x27;t figured out how to get &#x2F;topic&#x2F;foo&#x2F;photo-of-foo.jpg to appear in &#x2F;topic&#x2F;foo&#x2F;foo-notes when published? For example, in iA Writer, I&#x27;ll import an image, it seems to save the image saved in the same directory as the text content. I can preview it in iA Writer and the image appears, but when I publish to Hugo, I&#x27;m guessing that Hugo is not referring to the image correctly?? Apologies that&#x27;s vague - but the gyst is, &quot;out of the box&quot;, it seems like I&#x27;ve got to &quot;sort out how to embed images&quot;. I often will start a page on my phone - a few quick text notes, a few images... will publish it, and them come back a few days later to expand on it. Just want that &quot;publish some text and pictures&quot; flow to be easy.<p>- Somewhat related - What&#x27;s the current &quot;best practices&quot; on where to put related files (e.g. photos, diagrams, videos, etc that accompany or are embedded in a document). I am considering setting up a dedicated media.example.com. I&#x27;d love to have a local folder of files, and have it atomatically sync to an S3 bucket or something, which serves &#x2F;&lt;topic&gt;&#x2F;&lt;subtopic&gt;&#x2F;{photos, videos, audio, pdfs, etc}. On the content page, it could refer to those image links absolutely. Still.. frustrating having to make a whole separate &quot;tree&quot;.<p>- What do you suggest for site search? I want it to feel as quick as Mac&#x27;s Spotlight search, where it starts autocompleting suggestions.<p>- Other stuff: Can anyone suggest their favorite &quot;good out of the box&quot; Hugo themes? I&#x27;ve got to make several microsites, and I&#x27;d like to arrive to a few themes which are a &quot;safe default&quot;<p>Thank you for any advice. Very new to this, so trying to be productive without getting too bogged down.

1 comment

philiphodgen超过 2 年前
I am attempting something similar, and at the moment the tool I am using is <a href="https:&#x2F;&#x2F;docusaurus.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;docusaurus.io&#x2F;</a> with the same set of problems to overcome. (Especially the photos problem).<p>I have considered using Obsidian Publish. My objective is to build an internal knowledge base: SOPs for a business. It won&#x27;t be publicly visible. Obsidian Publish would require me to password protect the site, and that&#x27;s an unacceptable addition of friction to day-to-day use.<p>Collaborative editing is the other problem to solve. In my world, &quot;here&#x27;s the repo on Github&quot; draws blank stares. I have to use Google Docs or endless iterations of Word files.<p>Nobody will actually use an SOP in a Google Doc online, of course, and the trove of Word files on our server collects dust.<p>That&#x27;s why a website (built using Docusaurus or similar) appears to be the best way to reduce friction and inertia. The path of least resistance should be the website full of SOPs, not &quot;I remember how this works&quot; or &quot;I&#x27;ll just re-invent the wheel.&quot;<p>I sympathize with your plight and I&#x27;m busily trudging along a parallel path.
评论 #33096114 未加载