Show HN: Git-based front-end interface for Hugo
Recorded: May 24, 2026, noon
| Original | Summarized |
GitHub - arashThr/hugo-flow: Simple rich-text CMS for Hugo weblogs. Try at https://hugo-flow.arashtaher.com · GitHub Skip to content Navigation Menu Toggle navigation
Sign in
Appearance settings PlatformAI CODE CREATIONGitHub CopilotWrite better code with AIGitHub SparkBuild and deploy intelligent appsGitHub ModelsManage and compare promptsMCP RegistryNewIntegrate external toolsDEVELOPER WORKFLOWSActionsAutomate any workflowCodespacesInstant dev environmentsIssuesPlan and track workCode ReviewManage code changesAPPLICATION SECURITYGitHub Advanced SecurityFind and fix vulnerabilitiesCode securitySecure your code as you buildSecret protectionStop leaks before they startEXPLOREWhy GitHubDocumentationBlogChangelogMarketplaceView all featuresSolutionsBY COMPANY SIZEEnterprisesSmall and medium teamsStartupsNonprofitsBY USE CASEApp ModernizationDevSecOpsDevOpsCI/CDView all use casesBY INDUSTRYHealthcareFinancial servicesManufacturingGovernmentView all industriesView all solutionsResourcesEXPLORE BY TOPICAISoftware DevelopmentDevOpsSecurityView all topicsEXPLORE BY TYPECustomer storiesEvents & webinarsEbooks & reportsBusiness insightsGitHub SkillsSUPPORT & SERVICESDocumentationCustomer supportCommunity forumTrust centerPartnersView all resourcesOpen SourceCOMMUNITYGitHub SponsorsFund open source developersPROGRAMSSecurity LabMaintainer CommunityAcceleratorGitHub StarsArchive ProgramREPOSITORIESTopicsTrendingCollectionsEnterpriseENTERPRISE SOLUTIONSEnterprise platformAI-powered developer platformAVAILABLE ADD-ONSGitHub Advanced SecurityEnterprise-grade security featuresCopilot for BusinessEnterprise-grade AI featuresPremium SupportEnterprise-grade 24/7 supportPricing Search or jump to... Search code, repositories, users, issues, pull requests...
Search Clear
Search syntax tips Provide feedback Include my email address so I can be contacted Cancel Submit feedback Saved searches
Name Query To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign up
Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. Dismiss alert arashThr hugo-flow Public
Notifications
Fork
Star Code Issues Pull requests Actions Projects Security and quality Insights
Additional navigation options
Code Issues Pull requests Actions Projects Security and quality Insights
mainBranchesTagsGo to fileCodeOpen more actions menuFolders and filesNameNameLast commit messageLast commit dateLatest commit History27 Commits27 Commitspublicpublic srcsrc .gitignore.gitignore AGENTS.mdAGENTS.md CLAUDE.mdCLAUDE.md DockerfileDockerfile README.mdREADME.md compose.ymlcompose.yml deply.shdeply.sh eslint.config.mjseslint.config.mjs next.config.tsnext.config.ts package-lock.jsonpackage-lock.json package.jsonpackage.json postcss.config.mjspostcss.config.mjs tailwind.config.tstailwind.config.ts test-tiptap.jstest-tiptap.js tsconfig.jsontsconfig.json View all filesRepository files navigationREADMEHugo-Flow: Git-based Front-end interface for Hugo GitHub Integration: Commit files directly to your repository via the GitHub API. Local Development Set up your .env.local file: NEXTAUTH_URL=http://localhost:3000 Run the development server: npm install Ensure your .env.local is configured with your production keys and URL. npm run build Start the production server: npm start About Simple rich-text CMS for Hugo weblogs. Try at https://hugo-flow.arashtaher.com Resources Readme Uh oh! There was an error while loading. Please reload this page. Activity 3 0 0 Report repository Releases Packages
Uh oh! There was an error while loading. Please reload this page. Contributors Uh oh! There was an error while loading. Please reload this page. Languages TypeScript CSS Dockerfile JavaScript Shell
Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. |
The project by arashThr introduces hugo-flow, which functions as a custom, web-based front-end interface designed to facilitate the management of static Hugo websites, positioning itself as a simple rich-text Content Management System. A core feature of this system is robust GitHub integration, allowing users to commit files directly to their repository via the GitHub API. The dynamic configuration system enables users to select their specific repository and the corresponding file paths through a user interface, streamlining the process of content management. Furthermore, the application provides a dual editing mode, offering users the choice to switch seamlessly between a visually rich WYSIWYG rich text editor and a standard raw Markdown editor, accommodating different content creation workflows. Image handling is also integrated, allowing users to upload images which are automatically pushed to the repository as base64 blobs alongside their markdown posts. For local development, the setup requires configuring a development environment by setting specific environment variables in a .env.local file, including NEXTAUTH_URL, NEXTAUTH_SECRET, GITHUB_ID, and GITHUB_SECRET. Development is initiated by installing necessary packages and running the development script, which launches the application on http://localhost:3000. When deploying to production using a standard Node.js setup, the process involves ensuring the environment variables are correctly configured, building the optimized production bundle using npm run build, and subsequently starting the production server with npm start. A more advanced deployment strategy utilizes Docker and Docker Compose, capitalizing on Next.js standalone output to achieve a highly optimized and minimal container size. This method requires several preparatory steps; first, the GitHub OAuth application must have its authorization callback URL updated to the production domain. Second, production environment variables must be set in a server-side .env file, specifying the necessary domain, a secure runtime secret generated using openssl, and the corresponding GitHub credentials. Following this, the application is launched in the background using docker-compose up -d --build. To ensure secure and accessible deployment over HTTPS, this setup is typically paired with a Caddy reverse proxy, where a Caddyfile entry directs traffic for your domain to the application running on localhost:3000, allowing the application to be securely served across the internet. |