I would checkout hugo. It's a different approach. You write your pages in markdown, run the hugo binary to generate/preview your site, and then you upload the generated files to a webhost. Any host that can server html will work.
Lots of available themes, but you can make your own out of html/js and some little template variables. You can find a theme you like, copy it into its own directory, then just make changes until you get what you want.
There's also some more advanced things you can do like using github pages, you can also use staticman for things like comments. Comments will actually be added to your site's "codebase".
Ghost is decent, like people have said, but there's also Hugo. I played with it once, but I'm not a huge blogger so it didn't make much sense to keep messing with it.
Edit: Never mind, can't really do the mobile thing. :P
> In the end, I want working on the frontend to feel like working on a web app, so that it's familiar to web developers, follows best practices, etc. We already have, as a project, many ties to Ember, and so I chose it mostly because it feels like a solid, default choice.
I don't particularly enjoy working on web apps so that's probably part of my objection :)
>One thing that this could enable is a mode wherein you run rustdoc in the background, and as you tweak your code and the docs, it automatically updates in your browser. It won't do that today, but the way it's built fundamentally makes this possible.
I don't see any reason that would be incompatible with static pages. Hugo has "hot blog reload" and it generates static pages.
Please don't take my comment the wrong way. I'm very, very happy rustdoc is getting some much needed love and decoupling it from the compiler will make it massively better! I just don't think that rendering static documentation warrants the technical complexity of a web-app framework. It seems to me that using an existing Rust templating library would be sufficient for rustdoc.
Netfily or Githube Pages can be used for free. As an alternative to Zim, Hugo might be an option. Its Markdown files can be easily created in any editor and the changes can be deployed automatically.
https://gohugo.io/hosting-and-deployment/hosting-on-netlify/
Shameless plug: obsidian-export. It will convert [[WikiLinks]]
and ![[Embeds]]
to plain Markdown (among a few other things) so you'll always have a way to go back if Obsidian doesn't work out the way you hoped.
I originally wrote it for exactly this reason, though I also now use it to author all of my site content directly in Obsidian and publish to https://nick.groenen.me/ with the help of Hugo.
If you want to make your own here's a quick bit of javascript that you can modify:
<span id='countdown-nms' class="countdown"></span> <script type="text/javascript"> (function() { var f = function(n) { return n < 10 ? "0"+n : n } var out = function(d, h, m, s) { return f(d) + "d, " + f(h) + "h, " + f(m) + "m and " + f(s) + "s" } var el = document.getElementById('countdown-nms') var to = new Date("2016-08-10T00:00:00+0100") setInterval(function() { var diff = (to.getTime() - Date.now())/1000 if (diff > 0) { el.innerText = out( Math.floor(diff/3600/24), // Days Math.floor(diff/3600)%24, // Hours Math.floor(diff/60)%60, // Minutes Math.floor(diff%60) // Seconds ) } else { el.innerText = out(0, 0, 0, 0) } }, 1000) })() </script>
The date I've used is for the UK countdown so you might want to adjust it. If you're a Hugo user and you want to add countdowns to your theme, this code is just a modified version of a shortcode I wrote. Source here: https://github.com/nboughton/hugo_theme_robusted/blob/master/layouts/shortcodes/countdown.html
ParseInt
, the Go function has that explicit base argument.
<code>int</code> does not. In Hugo, that int
is a template function.. think of those as the only functions that a user can use in their site templates.
In the templates, I cannot use the core Go functions like ParseInt
directly.. so explicitly providing the base is not a option.
Gatsby must be quite heavy for your requirement it seems. However, I can suggest you to checkout hugo which only requires you to write HTML templates, markdown content and config.toml
Other than that, 11ty which is feature rich but requires you to write Javascript.
I'm not aware of any Nim framework that achieve the same, would love to see if there is any!
As you see, lots of folks suggest WordPress is totally fine as long as you spend a deal of effort hardening it and time managing it.
Meanwhile, my question would be: what do you need it for? Are you just doing a simple blog? There are great static site engines that would render your posts for you and you wouldn't have to worry about vulnerabilities or a database or anything like that.
Check out Hugo if this fits your needs:
There are plenty others just a Google search away. If this isn't what you need, enumerate your needs and there might be a much better fit for you than WordPress...
I have been using hugo, a static site generator for a personal blog-like project. The theme system is fairly simple so customization should be quick. The generator itself takes markdown files and produces html quickly. Very easy learning curve.
Just an alternative suggestion. Have a good one!
There is a "back to basics" movement using static site generators, for example Hugo is massively trendy right now.
Most animation today can be done with SVG and CSS, with little or no JS needed.
IMO, React/Angular were designed by Facebook (React) and Google (Angular) to get "ahead of the curve" on Web Components. Skip that nonsense, do not pass Go, go directly to Web Components:
Lighter, reactive frameworks will emerge around Web Components. Yes, React and Angular are wrapping their fat fingers around them. But fat fingers.
I really like this (commercial, though there is a free/open source tier) component framework:
It's from the same folks who developed JQ Widgets.
How about reconsidering your criteria getting rid of the database and dynamic content, and trying a static site generator like Hugo? This removes nearly all of your threat surface.
Hey thanks for noting this -- how would you improve it? Honestly I'm kind of over the entire theme I'm using on the site (and the version of highlighter.js it comes with, I think iI'm also wasting space too much space.
I use hugo and have been looking for a new theme that's a little bit denser, more minimal, and uses more of the screen real-estate.
How would you suggest I improve it? Should I just stick to black-on-white everywhere? or maybe go white on black everywhere?
Static site generators are great for this, very fast, mostly easy to learn, not unnecessary complexity e.g.
Our knowledge base is a Hugo static site (free). Docs are written in markdown and managed through GitHub.
When I push changes to the repo, the site automatically rebuilds and publishes -- that happens via Docker/Jenkins. Someone more technical than me set that whole deal up - I just have to know how to use GitHub and Hugo.
I say it depends. I can't stand wordpress and I deal with a lot of small business websites as a side business. I've moved all of them off Wordpress and they are now Hugo static websites. Its secure (straight up html/css/js), fast (pre-compiled html pages served from a CDN), and cheap to host. All my client sites probably cost me $0.10/month to host on Azure. Smashing Magazine actually just migrated from WP to a JAMstack.
So while WP will help I feel like more and more people will see the benefits of using a framework like Hugo to build your run of the mill small business website.
If you're not too attached to WordPress, you could switch to Hugo. Deploy to an S3 bucket and host the blog from there.
I did this recently as an experiment and it worked a treat. I even created a CloudFront distribution for it. The domain I used is a Route 53 one so aliases make things super simple. I used a custom domain and ACM for the SSL certificate.
Realistically though, what you're paying right now is worth it for the time it saves you. Even if the AWS deployment costs nothing, it can be a time sink to configure if you're new to it.
Well Spacing you can control in css. Check in assets/_markdown.scss and override in assets/_custom.scss.
For images it's likely that shortcode needed, which will generate img tag with float styles.
I forgot my website credentials, so I don't think I can fix it by myself.
(In hindsight, using a static site generator like Hugo would have been a better idea than a CMS like October, especially for Godot's purposes. This way, anyone could submit a pull request easily and pages would load faster.)
Not sure what kind of dedicated server you have, but running vms comes with a cost. You really don't need it for two services you are running.
btw. if your personal website is static, I recommend using a static site generator (I use hugo). Either way you can just rsync it over to the server without using ftp
I've been doing this since I started grad school 1.5 years ago. It's so easy to work with using the in-browser editor and is viewable anywhere. It supports links within files, between files, and to external resources, along with media. It's just so damn versatile.
However, I've since migrated to Hugo for more complex things which automates cross-referencing and construction of list items. This is useful for annotating research papers and tracking meeting notes in a way that is easy to navigate for other people who I grant permission to.
Hugo doesn't parse CSS files to handle images. They're stored alongside with your content files. This way they can be detected as "resources" and handled by file type. The screenshot in the page resources section in the docs should give you more information.
I discovered Hugo: "https://gohugo.io/" a small but really cool static website generator that works well with GitHub to manage your site.
The Hugo community offers a bunch of templates that are free that you can tweek the way you want.
If you want to try to play around with it yourself give it a shot. I worked with it after a few Wordpress projects and i think it is just awesome. Super easy, fast, and should be enough four you purpose i guess.
But if you fell uncomfy / a little scared than tell your boss that you may need help a professional well be a lot faster then you and probably save you time and mony in the end.
No other advantages. It's less complex and has less features, but it does everything incredibly well, and is incredibly fast.
Jekyll was taking 1-2 minutes to generate my blog, and something like 5-10 seconds when I was working on a post. I would often save a post and have to keep refreshing the browser a few times until it was regenerated.
Hugo takes around 700ms to generate my entire blog. During development, posts are regenerated instantly, and the browser also updates instantly with the built-in live reload.
You might need to use Jekylll or Octopress if you really depend on some plugins. But take a look at the hugo docs and see if anything is missing.
Have you considered a website generator that reads from static config files for editable data? Something like Hugo (https://gohugo.io/)
This way they could edit their site by updating some text files (without having to learn HTML or understand CSS), but you avoid the mess of a CMS and maintain the performance benefits of static files.
May not be the answer you're looking for, but it's just another option out there if you want to consider it.
I think you are looking for something not WordPress but like it? You mentioned a static site, so if you are looking for a static website engine check out https://gohugo.io or https://middlemanapp.com. They are not going to have a GUI like WordPress however.
>* I have no problems with any language. If I don't know it, I can learn (usally I use PHP, VBA, Python, Rust, Java and Javascript) * I need one of the sites to be multilanguage (Spanish and English). So I need some kind of module to "join" the pages in each language * I need some kind of "contact module". If possible, with multiple fields (not just email, subject and email body). * For SEO purposes, I need a sitemap builder * If possible, good documentation about how to build themes, or a good library of themes
Take a look at Hugo.
However, Hugo does not offer a "contact module" by default. But the problem can probably be solved with the help of the Hugo community. Probably someone has even published a solution already.
And the documentation is a bit confusing in parts. But even I, as someone who is not a professional WebDev, got along with it.
The rest of your requirements, such as a sitemap, are fulfilled by Hugo.
This.
You don't mention what kind of a site/page you are building and how big it's going to get, but the most idiomatic way would be to generate everything exactly once upon a change. If it is a blog/website of considerable but reasonable size, you can use or check out the code of https://gohugo.io or similar static site generators. They do this pretty well.
Hi,
i highly reccomend to read some documentation :D
if your frontend is just static html and does not need to be pre-processed or something, you don't need the build step - so the errors regarding hugo are not relevant (btw: hugo is an awesome tool to create static sites - https://gohugo.io/)
all other configs are described in the s3 plugin docs http://plugins.drone.io/drone-plugins/drone-s3/
if you just want to push all files in your repository, you can just write source : **/*
I've written a piece along these lines:
https://www.brycewray.com/posts/2020/09/normal-persons-guide-static-website-hosting/
. . . and its Netlify-centric precedessor:
https://www.brycewray.com/posts/2019/04/publish-or-perish/
Hope they'll be of some help to you. Also, the Hugo docs site has plenty of info in this regard, starting at:
It sounds like a backend might be overkill for what you're doing. Would it be possible to either pre-compute all the permutations and generate a website from it or do it on the fly in the browser?
If you went the precompute route, you could use a static site generator like Hugo that supports generating pages based on data to build out a static site you could host.
If you went the dynamic route, you could write all the data to JSON and load it in the browser to compute on.
The nice thing about doing it all on the client side is hosting from AWS S3 or Firebase is dirt cheap and you don't have to worry about people abusing your APIs, securing a database, etc.
Hugo is a very good alternative as well. https://gohugo.io/
It's fast and comes with a lot of themes provided by community users https://themes.gohugo.io/
I recently have used it with my website/blog https://manojsinghnegi.com/
> https://gohugo.io/templates/sitemap-template/
Thanks. That makes perfect sense.
"You should configure a parameter as the public url and use that as the base to generate the whole taxonomy"
Do you mean specify my custom domain name in the yaml file ?
Many thanks
Google Page Insights is a wonderful tool. In addition to that I'd say that pregenerating your html files makes a huge difference. There's some great tools out there for that now too, like gohugo.io
Your feedback on scrolling is duly noted! Will look into it!
> 2. Then, I would git submodule add
a theme, such as my-foobar
into the themes
directory. So the command would be run within my-site/themes
and look like git submodule add [URL to my-foobar repo]
. This would produce my-site/themes/my-foobar
.
Take a look: https://gohugo.io/getting-started/quick-start/#step-3-add-a-theme
> 3. If I make changes to my website's contents, I would git push
from the my-site
directory.
Yes.
> 4. If I make changes to the theme, I would change files in my-site/themes/my-foobar
and git push
from within my-site/themes/my-foobar
.
Yes, but also you'd go up to the website directory, and add and push the changes from there too, but like git add themes/my-foobar
(instead of having to specify the file).
Even with how confusing this can be, I can say I haven't actually had any major issues, nothing complicated that I had to correct, or no file changes loss or anything like that.
J'ai un soucis bizarre. Un collègue doctorant a construit un site web (pro), comme ça se fait dans notre communauté. Il le met en ligne, on peut y accéder, nickel.
Sauf qu'aucun moteur de recherche ne l'a indexé : Google, Bing, DuckDuckGo, Qwant, ... Et le site est en ligne depuis un bon mois.
Sur la page de notre labo, il y a bien un lien vers le site en question (le site n'est donc pas caché).
Avez vous une idée du pourquoi ça peut arriver ? Que faire ? Que fait la police ?
Le site est static et a été construit avec Hugo
Edit : précisions:
You could probably pull that off with Hugo - a static site generator - and a CMS like Forestry. If you don't have a complex frontend (basically if you're not building an app) I would avoid React and other frameworks as they add unnecessary complexity, impact performance and accessibility.
A static site generator will build the site when you change the content files. If your site changes a 20, 30 times a day, that's fine. Hugo specifically can build a very large amount of pages extremely fast. In this benchmark, 10,000 in around 7 seconds.
There's nothing faster out there than prebuilt pages. No code needs to run on the server to generate the page, it's already there. Also, there's no database to worry about or security vulnerabilities in the backend. The CMS you choose will have a similar interface like WordPress for editing content but will commit the data to your git and there are services out there like Vercel and Netlify which build and deploy your site on every commit and give you a CDN for free.
Ok, this is a bad idea. First, learn to use your browser's debugger, it's probably throwing some error. But you absolutely should not be using AJAX to include HTML. JS is executed last, performance with this will be horrible.
I'd recommend a static site generator like Hugo. Its templating allows you to include HTML snippets and it will render your site as static HTML.
While blogspot is a decent starter blog, it's a good idea to control your own blog as a programmer. You can use github to host your free blog and there are many static micro blogging platforms like https://blog.getpelican.com and https://gohugo.io . It will also help you become proficient on using GIT and github.
I can think of an example using object oriented design, but not with Wordpress. You can try using taxonomies with Hugo, then host it for free at a number of free static hosts.
hugo
as in https://gohugo.io ?
Sounds like you want to create your own theme for it?
https://gohugo.io/themes/creating/
For help - click their community link: https://discourse.gohugo.io/ - there also seems to be r/gohugo ...
[shameless plug]
I write my blog content in Org mode, and export that to front-matter + Markdown using <code>ox-hugo</code> (that whole website's content is exported from a single Org mode file.) that Hugo picks up and converts to HTML.
[/shameless plug]
And that time cuts down to around a second for live previews. So I C-s
in my Emacs frame, the post auto-exports to Markdown, Hugo converts that to HTML, all in a second or two.
I disagree that you need a portfolio site. That sounds like a theoretical idea that might seem reasonable enough but isn't the result of any practical experience. The people that impress me the most are the ones who can show me code they've written, can talk about the engineering decisions and trade-offs they've made, and show that they know how to unit test it. A website doesn't really set you apart.
If you still want to build a portfolio site anyway you're looking for a static site generator. Hugo is lightning fast, flexible, and simple enough that I'm comfortable pointing a fresh developer at it. Netlify is an awesome host for static sites that can also serve as a continuous integration pipeline hooked directly up to your repository. Jekyll and Gatsby are two of the other big static site generators but configuring Ruby on your Windows machine won't be worth it and Gatsby will require you know a bit more about React. Hugo is a single executable.
Depends on how you want to write your content. There are plenty of "importers" out there for static site generators (I personally use Hugo which has several wordpress importers, having had a stint with Nikola for a few years). There's also stuff like GitHub pages, which uses a limited subset of Jekyll.
The hard part is getting all existing links to point to your new location/hosting. That might take more time than you might think.
Sounds like a simple site, in that case maybe look into Hugo instead? I have moved a few simple sites away from WordPress and into Hugo recently with the Netlify CMS to update content.
This is our (from my girlfriend and me) post about or three week hiking trip to Iceland in 2018. No hotels, no campsites, nearly no contact to other people. I hope this supports some of you when planing a similar trip.
Please give us any kind of feedback you have. Because we're both from Germany, feel free to correct any kind of language mistakes as well. Thanks!
​
For those of you who are technically interested:
The site is build with hugo, so feel free to take a look at my GitHub repository.
>a google "site" collapsible list: https://sites.google.com/view/listofvotingmethods
Wow, this page lagged a ton and never actually loaded the contents of the page for me. Modern Google sites is probably not a very good option.
If you want the community to be able to maintain it, other than actual wiki software I would recommend using Hugo or Jekyll hosted on Github or Gitlab pages.
Also, don't forget that reddit has subreddit wikis. It looks like the /r/EndFPTP one has actually had a bit of recent activity.
I recommend using Hugo https://gohugo.io
I use it in combination with Gulp. Works really well and fast for me.
I did loads of sites in Jekyll but when I met Hugo I was no longer caused by headaches of Ruby stuff in Jekyll.
This definitely sounds like a Hugo question. I'd start by looking at the docs over on their page.
Off the top of my head though, I'd personally have a random/ folder in my public/ directory, and an index.html file with a javascript redirect there. The tricky part is getting to the list of pages on your site from which you'll pick one at random. Maybe check into reading in your sitemap.xml and pulling out all <loc> tags without an associated <priority>0</priorirty> value?
How technical of a person are you? If you can handle git, my advice is to use Hugo hosted on Netlify. This setup is 100% free, and it's literally the fastest possible website. There's a few CMS services (wordpress-like dashboards) that are also free. I haven't used them so I can't vouch for their quality or ease of use, but Forestry looks nice.
Just a few quick thoughts - I haven't dug in or looked at the content, just a preliminary glance at the design:
Thanks. I am writing my content source in Org, and then exporting that to Markdown + front-matter for Hugo using <code>ox-hugo</code>, and then Markdown to HTML using Hugo.
Here's the flow:
ox-hugo
(C-c C-e H H
). You can find my site source in its footer on each page.
> create nav bar menu in one place using JS . This would avoid the hassle of copy pasting nav menu html code on every Static html page that'll be created in future
This is what static site generators like jekyll and hugo are for. (Or PHP like in the SO thread, but that seems like overkill) If you do it in javascript your menu won't be visible to anything without JS (And so the vast majority of search engine crawlers will miss all the links)
What people probably mean when they say jquery menus are crawled is "menus in html that are animated (IE submenus) in jquery will still be crawled" (Because they're just HTML when you strip out the css and js)
I would suggest to keep the format such that it can be understood by a static site generator (personally I use hugo). Basically this means markdown and maybe YAML or TOML header.
This can later generate nice linked html pages with navigation. It's also nicer if you want other media in notes.
One option would be to create a private (or public, up to you) static website with a tool like Hugo. You can style the site's template however you'd like, and your notes are simply markdown so they pick up any template changes naturally.
Trying to dynamically mix formatting and content is tedious and error-prone at best, so even if markdown doesn't make sense for your use case, I'd look for tools that let you separate the content from the template, rather than unify them.
What? No. Why?
Hugo is a go app. Compiled to run anywhere with a dev server built right into it. It even has support for live reload out of the box. You don't need to compile, push, and upload new versions every edit.
This is terrible advice.
Please go through the getting started guide again and then hit up Using Hugo which explicitly details all of this.
a text editor.... yes! Try Atom.
Something like 'live reload' or 'browsersync' might be usefull.
If you just want to experiment with front endy stuff why not try out a static site generator like hugo. it does live reloading and you can install it in a few minutes. Draw some ideas on paper then work on turning them into code with some filler content.
Alternatively take an atomic approach, start by drawing a couple of components (a nav bar, a picture slider thing, an fancy quote) and get them working in isolation. They will be good learning exercises and when you have a few you can start combining them to make a page. that way you can focus on some details with out getting over whelmed.
Also +1 for the CSS frame work suggestions, look at the source code.
I am surprised no one has talked about Gitlab pages in here yet. I guess everyone is obsessed with Jekyll and Github pages? :D
My website is currently generate with Hugo and hosted in an Amazon S3 bucket. I recently added Cloudfront and TLS (using the TLS cert that Amazon provides). Before that it was generated using Octopress which is essentially a fancy wrapper for Jekyll (that is not fair to Octopress, it is more than that).
With Gitlab pages you can generate and host your website using a decent number of static website generators such as Jekyll, Octopress (technically Jekyll), Hugo, Hexo, Pelican, etc.
For costs, my domains are around $100/year. I have 2x .io one .net and .com which are all redirected to the main website. Route 53 hosted zones are $0.50 a month each, I have 2 so it makes it a dollar a month. Usually traffic is 1 to 2 dollars a month. Supposedly it will double with Cloudfront.
All date format declarations have to use the date/time of "Jan 2, 2006 at 3:04:05pm -0700" (with time zone)
Something about 1-2-3-4-5-6-7; so Jan(1) 2nd(2), 3:04:05pm of year 2006(6) in the -0700 time zone
All the examples on the Format page do this, but it's not super obvious at first glance
Not sure why, but that's how it works
I have a small Hugo (https://gohugo.io/) site with this theme (https://themes.gohugo.io/themes/hugo-theme-learn/) that I document everything I do including any software I write.
Git repo with homeassistant config + README.md file -> Triggers Jenkins job to deploy homeassistant changes -> Final step of the job takes the README.md and any other marked .md files and adds to my hugo site git repo -> Triggers Jenkins job to deploy updates to hugo site.
Works really well but it'd be a bit of a faff if you didn't have the full pipeline in place already.
Many recommend Wordpress because it is easy and there is a huge community but I would advise you to consider other options. My reasons for this recommendation:
If you do not need a "web app" and just want to build a landing page / basic website IMHO it's a better idea to build a static website. You can use Wordpress for this, too but there is alternatives like hugo which I prefer. If you lack the skills to build a site with hugo alone you can combine it with a headless CMS like forestry.
A static website is more secure, more responsive and decreases cost of hosting and maintenance.
Hugo is a templating engine. Effectively it allows you to build static (non dynamically generated) websites on your home computer, render it and then upload to a server. There is no faffing about with databases and server side code.
Text is created using markdown (a very simple and easy to learn formatting language).
Here's a link. There's lots of themes to choose from and it is relatively easy to set up.
That only works locally in your browser since you're using "file://".
It sounds like your goal is to create a list of files in a directory. Look into: https://gohugo.io/templates/lists/ and https://discourse.gohugo.io/t/list-files-in-a-directory/21258/3
Thanks for the reply. Good thing to consider. However that can easily be handled in Hugo by simply defining an Alias in the Front Matter of each page’s .md file. See the Aliases section of URL Management in the Hugo documentation.
https://gohugo.io/content-management/urls/#aliases
This will allow me to build the site with more SEO friendly (longer, more descriptive URLs), as well as organize the site more logically than before.
I think it depends on the kind of work you are about to do. If it is ecommerce or something related to some creative work then you need a good website. I am selling services for which i need online presence, that's pretty much it. So initially for simplicity, you can have your logo designed on fiverr and then use google sites to build it yourself - drag and drop + simple + resposive. Good thing is that it can be done as soon as you buy a domain from google. You can also opt for gsuite for email/docs which saves license cost vs Microsoft office.
If you are a bit technical then hugo is also a very good static site generator with tons of templates. Static sites can be hosted for free on render.com.
here are the theames: https://themes.gohugo.io/ hosting site doc: https://gohugo.io/hosting-and-deployment/
Wix is also a good premium service which connects well with google domain. But with many elements, it gets a little slow in my opinion.
If you are looking for an e-commerce then feel free to DM, i can help you develop it. good luck.
Rather than a framework, I would suggest a tool: Hugo.
It's absolutely fantastic to create a static website with some simple templating and a dash of markdown you're up-and-running. Add some theme from the massive library and you can run a micro-blog, sales-front, art gallery, pretty much whatever...
Give it a look!
IMHO Tailwind is simply a tool to make it easier to write CSS. In the end it's just CSS like any other CSS. CMS does not matter since all work with CSS.
In Wordpress you typically have a ready to use theme (unless you develop a theme) and you would use CSS rather than TailwindCSS.
Anyway, I use Hugo without a theme (I do my own) and it works fine. Now I use this barebone Hugo/Tailwind3 starter kit.
Ah ok! So that gives you a lot of freedom to choose different solutions, depending on your tastes.
On the one hand, if you used WP and it was fine, then there's a good argument to just keep using it, since why spend time learning something new when you have a business to run? The implementation of the website is a low priority from that perspective.
On the other hand, if you are a dev and just like to try new stuff anyway, I'd suggest looking into various static site generators which are absolutely ideal for static pages that don't change much. The big advantage is that they just generate static files, no database or PHP or anything else needed. You can literally drag-drop the generated folder into Netlify and you've got your hosting sorted.
Personally I use Hugo for all my static sites. It is super fast but on the other hand the templating can be a bit hairy. I've also heard good things about Eleventy but never tried it myself.
If you consider having them converted and stored in a server space anyway - why not use something like Hugo? Any update (or any update) would be rendered automatically into HTML. It is just a matter of having it configured once (a pretty simple thing).
github pages is a hosting solution, and you can use a static site generator with it, e.g. here's Hugo's docs
Coding isn't necessary, but it does help mostly because you tend to be used to a lot of random confusing setups and command-line interface (CLI) stuff once you've been coding for a while.
I would definitely recommend against self-hosting WordPress, but if you can find a place that will host for you, that will probably work for what you need.
> In this case I would not want others to contribute to the wiki at the moment as that's not the purpose of this website.
If you NEVER want anyone else to contribute to the site, maybe a static site generator like hugo is a better bet? (that's what I use for my personal blog, but it's not restricted to blogs) MediaWiki is pretty complicated to sysadmin, the primary benefit of it is allowing others to contribute.
The repo is here and more can be read about Hugo on their official website.
It's what the original version of AkhMorning had been written in, and the very first Balance website before this one. It's something I had worked with for a good while.
CMS ist OK, eigentlich nutzen Agenturen selbst für ihre Kunden fast nur WordPress und CMS Systeme, die dann nicht aktualisiert werden...
Bezogen auf den Anruf - falls Du ne Rechtschutz hast - kläre das mal, ob das schon Rufschädigung/üble Nachrede sein kann. Sowas geht gar nicht.
Thema Weitergabe und statisch: schau Dir mal statische Sitegeneratoren wie z.B. https://gohugo.io/ an. Ein Segen.
Ganz im Ernst: ich habe meine ersten Kundenwebsites vor 21 Jahren gemacht, die "Anforderungen" sind immer die gleichen. Ja wir brauchen Admin Menü, wir müssen selbst Dinge ändern können. Zu 99% wurden die Änderungen dann doch von uns durchgeführt. Forum, Gästebuch und den Blödsinn braucht auch keiner mehr. Alles Andere lässt sich statisch lösen (oder sogar automatisiert generiert bei Upload von z.B. Bildern)...
Besonders für "kleine" Websites (Mittelstand) ist sowas wie Hugo einfach perfekt.
The author seems to be pursuing a different approach with static site hosting or low-code scenario. Yours requires at least a VPS.
Quote: >actually kills two birds with one stone providing organic search discoverability and the site specific full-text search and requires no maintenance.
Anyway, the solution you offer is definitely worth mentioning at https://gohugo.io/tools/search/. Have you thought of submitting there?
Oh, I wanted to include this option too, but was like "who does this nowadays"? But honestly, I would not write the feeds from hand. I'd suggest to change your workflow to use a static site generator like Hugo that spits out static HTML and the feed XML
As far as I can tell this is not ox-hugo or even configuration behavior but rather done at the theme level, given the heading link example in the documentation. There's no if
statement in the theme, which seems to indicate it's hard-coded and not controlled by configuration. The file name given in the link above might work depending on the theme, but in the theme I use (PaperMod) it seems to be controlled by partials/anchored_headings.html
so you should check your theme and replace the anchored header file with a corresponding file in your root layouts
directory. See Customize a Theme for more information.
Forking and hosting an existing solution won't work for anyone non-technical. I am technical, and I don't even want to do it. I would rather push a couple of buttons and have a HN-clone be automagically created and hosted for me.
As for existing forum software, all of them are clunky and will require a technical person to host, manage, and maintain. It is like trying to ask someone to use hugo rather than weebly/medium/substack for their personal blog. Or setup their own file-servers rather than using dropbox. Again, even I would rather just use dropbox.
People will always want to consume content and be part of communities. I don't need to measure that. What I need to do is execute well-enough to tide them over from existing solutions. Only way to figure out if I can do that, is by just doing it!
I know of no such solution which is not to say they don't exist. But my instinct is that this could be done with a statically generated page plus some javascript for the image viewer. That way you can host the generated files on pretty much any webhoster.
As an option Hugo comes to mind as I'm familiar with it. It has templating and supports pretty much any data structures. There's many other static site generators that would do the job though.
Thanks, it's new, and will get more content soon.
I use a framework called Hugo (https://gohugo.io/)
In your config.toml
file be sure to set relativeurls = true
. You may need to fork and edit parts of your theme. I found the theme I used (hugo 386) did not use a lot of relative links. Relative links are easy, just make a link to the page you want using regular markdown or html paths, Hugo does the rest of the magic for you.
Normally Hugo should put the permalink as the location of the sitemap, because the sitemap protocol requires absolute urls.
If you host your site on github and then map the github to a custom domains, hugo has no way to detect this mapping because it's handled by github, therefore it considers the url(s) on github as the "absolute" url(s).
You should configure a parameter as the public url and use that as the base to generate the whole taxonomy.
https://gohugo.io/templates/sitemap-template/
<loc>{{ .Permalink }}</loc>
Since you are familiar with coding, how much do you like it?
WordPress is quick to set up and there's tons of free themes out there, coding will help if you decide you want to build your own theme or even modify others you like. WordPress gives you better ownership of your content and is also well known in the hosting space; most everyone has support for it, making it easier to transfer your site incase you end up not liking your host. WordPress is also way more flexible, being Open Source software and community supported should your needs change or expand in the future.
An interesting alternative you may also want to look into is HUGO which is a static site vs a dynamic site like WordPress. It too has themes and a growing community support but has a slightly higher learning curve for initial set up and maintenance.
As for education about websites YouTube would be one of the best sources but you should also check into other subreddits like:
Hope this helps!
Thank you! I can take exactly 0 credit for the appearance and usability of the guide, that's down to this awesome "Learn" theme for a static site generator called hugo.
But I agree, it's clean, it's free for me to host because it's just a static site (Even though it has interactive content like the search) and it makes adding content a doddle.
A few people have mentioned things like WordPress, but setting it up and doing the stuff for that is a pain in the arse and as you are at the can’t do HTML side but can do Reddit I would honestly look at using something like Hugo.
It is pretty simple compared to WordPress and will spit out some html you can upload somewhere.
https://gohugo.io/getting-started/installing#chocolatey-windows
Is a good starting point.
Failing that, start with learning html and css and just move from there. Don’t start with using word, I mean look at something like this for example and view source:
http://bettermotherfuckingwebsite.com
Hugo can get you something in a pretty templated design quick and is more forgiving than WordPress but less chance of you not keeping it updated and someone using it to host porn or something.
You could use an external service, such as Discus, to provide comment features: https://gohugo.io/content-management/comments/#add-disqus
However, this will mean comments are ONLY available to those with Javascript enabled. It will also mean your privacy policy will need to extend to account for this service.
Absolutely possible. My own blog is built using Hugo (https://gohugo.io/) and couldn't be easier to maintain. The source files and the blog itself are all hosted on Github for free.
There's an "ugly URLs" setting which gives all files a html
extension, indeed. I may be mistaken but I believe that also didn't fix the issue when I tried it.
Markdown render hooks are the solution to this problem I suspect, but I haven't tried.
I use mkdocs which includes a nice search feature. I would also just use plain markdown as well. Another option could be a static web generator, e.g. Hugo.
Not sure how you use Docker w.r.t to self-hosting the services that you do but a convention that I follow is keeping my docker-compose, settings, and small amounts of data in a single directory on my server. I can rsync it to my NAS or other places.
For services that use larger amounts of data (Plex Media), I keep the data on a remote FS mounted from my NAS. I map those paths into the containers instead of using a local directory (a sub-dir in my primary services directory).
This all just makes it easy for me to backup and migrate. I just need to backup my /etc/fstab and another system services I configured on the host. The documentation is my compose file basically.
Check out Luke Smith's email wizard, it's an easy way to get an email server up and running on its own but can also be a nice starting point for a more custom solution.
> blog
I use Hugo. It's kind of limited compared to something like WP but it's a lot lighter and can still produce nice results.
I started learning web development last year. I took an introduction to web development course, from where I got an brief overview of what web development is and learned that html, css, and javascript are the fundamentals I have to start with.
I learn the fundamentals by designing resume and posters with html and css. I soon found [W3 Schools](www.w3schools.com), [CSS Tricks](www.css-tricks.com), and MDN are especial helpful.
After that, I began playing static site generator like [Hugo](https//gohugo.io) and learn by customizing templates and adding functions. Here I found my knowledge about web development from google is helpful but not systematic enough to let me achieve what I have in mind. Then I searched Coursera and took "HTML, CSS, and Javascript for Web Developers" offered by Yaakov Chaikin.
I am now playing with Gatsbyjs and Tailwind by building my personal website.
>I don’t expect more then 1-5 people per month. It would have Wordpress
If I were you, I would consider whether the maintenance effort for Wordpress is worth it with so few visitors. If I were you, I would rather use a SSG (static page generator) like Hugo. With this you have no maintenance effort.
You could then host the pages for free or for little money, for example at Netlify, AWS or Github or Gitlab (https://gohugo.io/hosting-and-deployment/).
> Images should go in the static folder, in which though you're allowed to create custom subfolders for organization sake.
Depends. If you want to process the images further they should not be in /static.
I don't think you can do this directly in your configuration file.
However, you should be able to add something like this in your menu partial:
{{ $menu := .Site.GetPage "/menu" }} {{ range $menu.Pages }} <a href="{{ .Permalink }}">{{.Title}}</a> {{ end }}
That will expand to all pages under your "/menu" section. Inside the {{ range }}
bit .
will refer to the specific page, so you can use it to get all page variables for that page. Above I only used Permalink
and Title
, which are most likely to be the ones you're interested in.
Static generators. Take a decent theme, write content in markdown, and suddenly you have a reliable site with no dynamic content, no security holes, and something you can essentially set and forget.
I prefer Hugo.
You definitely want to use a so-called static site generator. That's exactly what you are looking for. I recommend Hugo, not only because Math Support with KaTeX is built-in in most themes. Just download a theme and go. https://gohugo.io You can then host your site for free wity Netlify.
You should look into static site generators like Hugo. No database needed. Blogs are in markdown, everything is in version control, Hugo generates the site from the markdown & a theme you choose.
You could look at Hugo. They even have a walkthrough on running it on Amplify: https://gohugo.io/hosting-and-deployment/hosting-on-aws-amplify/
Regarding the scalability. The initial "build" of your static site will be the longest. After that, unless each new post somehow ends up updating the whole website (which would mean something's been done wrong), yes, it will scale.
It will scale as well as S3 & Cloudfront can, which is basically beyond what most of us will ever need.