What is Reddit's opinion of
Jekyll?
From 3.5 billion Reddit comments
➔ Jekyll website
By popularity on Reddit, this Service is:
100 reviews of this app found across Reddit:
Jekyll is a static cms, meaning once you did the html template, you simply add pages with some header configuration to generate a blog.
Biggest upside IMHO is that you can host your blog for free on github pages.
It's a free cms, that comes with free hosting so you only might need a domain if you don't want a something.github domain. And it's pretty simple to develop locally and push to github when ready.
No actual coding required, only yaml configuration files.
With those requirements, I'd recommend Jekyll generated and hosted by GitHub Pages.
You just push your markdown to a repo and it'll update your site, they handle hosting and you can still use a custom domain if you have one.
Nice work. Do you know Jekyll? It is a similar CLI program that allows you to use an HTML template for all your static pages.
Maybe it could be cool make your GUI work with Jekyll as a backend.
hetzner.cloud - 2.99 Euro al mese e dormi tranquillo. Se aggiungi il backup, il prezzo aumenta del 20% (3 euro e qualcosa).
Se il tuo sito è principalmente statico rifallo usando hugo.io o jekyllrb.com e paga sti 10 Euro all'anno di hosting e via.
Hostare su NAS è una rottura di palle causa connessione spesso inadatta e manutenzione che devi fare tu.
Namecheap - .com = £7.08/yr, .co.uk = £6.05/yr with privacy
A lot of the big brand registrars have horrible reputations and predatory practices
eg. buying domains you search for and "helpfully suggesting" that they can negotiate to buy from the "owner" at a higher price
search reddit for horror stories about GoDaddy etc.
Jekyll + Netlify = £0
I do have a personal page (I don't want it associated with this account) that I created at the behest of my supervisor.
I don't use it a lot, and I'm pretty sure no one's ever contacted me because of it.
It was useful, though, to learn a bit of web tech. I used Jekyll to build it, and I think it turned out nice.
Despite the lack of a social aspect (following, friends, etc.) I ended up hosting my own blog/website powered by jekyll.
I chose it because I'm a big fan of writing with markdown syntax, and jekyll allows you to write posts and pages using a really nice markdown/html hybrid.
It's super quick to set up, and you can host on github.pages for free!
Fast, flexible and with loads of themes to choose from. I can't recommend it enough.
Thank you, I'm glad you found it helpful!
I write all my blog posts in org and then convert them to HTML using Emacs. These HTML files are then used to build the entire site with Jekyll. I created the theme and layout myself - you can probably tell I'm not artistically talented :)
I said this for years before it finally “clicked” for me.
Check out Jekyll. It’s basically plain text with styling in Markdown. Tons of free templates available, and you can host for free on GitHub by simply changing where your personal domain points to.
DM if you want to know more or need some help.
Take a look at Jekyll, a static site generator which you can use with GitHub Pages. You've probably got no need for something as complicated as Laravel, all you should need to know is HTML, Git basics and how Jekyll works.
That said it all depends how non-static it is. What do you intend to do with storing contacts?
If you're not comfortable with code at all, take a look at Wordpress/Squarespace, it can probably do what you want without having to roll your own CMS
Ah, thank you! The site certainly works well; I'm a software dev in real life so I'm good at that part. My self-consciousness is about the math itself. I can't, for the life of me, get myself to do really careful rigorous math, so I don't... quite... trust myself to write about anything abstract like exterior algebra without making glaring mistakes. Even though I like to try. Plus there's also the general self-consciousness that comes with posting anything online.
The Wordpress LateX plugin is definitely bad. My site is built on Jekyll and hosted (for free) on Github pages. The TeX is through KateX which is like MathJax but much lighter weight and loads a lot faster (and it doesn't make the page reflow = reorder everything / move around as it loads the math).
I believe that even on Wordpress you could set things up so that KateX or MathJax parses math via Javascript when the page loads, but I haven't tried. It might require paying for Wordpress to modify the Javascript on the page. Can't remember
In the nicest way possible, your writing on this site might reach a larger audience if you spend a weekend reading up on best practices in website design. Alternatively, you could have a look at blogging tools like Jekyll that will do this for you.
- If you're doing this project to learn as much as possible, I would recommend trying to build a simple CMS yourself. I'm sure there are lots of tutorials out there. If you're trying to get this project done ASAP I would recommend using a static CMS like Jekyll on a subdomain. You can use Wordpress on a subdomain really simply also. But that is over-kill if you just want a simple static blog.
- Yes, definitely.
- Sublime Text is a text-editor while RapidWeaver looks like drag-and-drop website builder. The two aren't really comparable. I personally think most drag-and-drop website building apps are pretty crappy and result in subpar sites. If someone can only create sites using tools like that, then I'd hesitate to call them a web developer. But that's just my opinion ;)
Good luck!
Wordpress is pretty popular as a platform. If you're not opposed to learning a little HTML & CSS I highly recommend Jekyll. There are plenty of really nice looking themes to use, you have a ton of control over your site if you choose to customize.
It's an awesome way to show potential employers that you are competent with web technology. Another huge bonus is that you can use Github Pages to host your site for free.
Extended explanation: A lot of effort has been put the site, even since our last deployment, and the (small) team was planning to update everyone, but it seems like we've been called out first!
All of OPs concerns are valid, and as I was saying in the post linked to above, the process for deployments is still being improved. To explain it all in a nutshell, the site is actually static HTML, generated by Jekyll, so it has no database. We work with YAML files that are used to build the listings, each holding information about the merchant, via key: value pairs. While this works great, it does require manual intervention, but the benefit is that we're able to vet the content for accuracy (as best we can), and ensure no spam/robot submissions are received.
Once continuous integration is...integrated within our process, deployments to the live site will be much faster. Again, it's a small team that is working on this non-profit initiative, and combined with life's responsibilities and the holiday season, things have slowed down recently, but that's not the intention of course.
That said, yes, help from others is valuable! We'll still try to get that article out with a more in-depth status update, and how to further get involved. Funding hasn't been necessary for us, due to our hosting donator (thanks!), and mainly just the cost of effort/time. The Bitcoin Cash Fund team could probably use your support though, which would assist a wide variation of projects in the Bitcoin Cash world.
We're actually getting a new release packaged up for deployment, and hope to get it live ASAP! Thanks for everyone's interest, concerns, and constructive feedback.
Yep Github Pages will be fine for you. You can use Jekyll on Github pages, so it's quite easy to set up the structure for a multi-item portfolio, or case studies, etc.
I host a number of projects on Github Pages, and use Jekyll on a few too -- most notably my blog is Jekyll/Github Pages.
Jekyll is very easy to use, and you can even get pre-made themes if you're not very technical.
You're using PHP as a templating engine, which is totally fine. There's nothing wrong with it. It'll make your site slower than just serving static files, but not by much.
You could look into learning some build tools which you could use to compile templates into static files so that you don't have to do the tedious work of copy-pasting the nav/footer yourself. Or you could simply use something like Jekyll. It requires setting up Ruby, but it has really nice integration with GitHub pages so you could get started with that.
opensourcerails.com has some nice examples.
Edit: though personally, I'd recommend Jekyll over "rails". But wether that fits, depends a lot on your requirements. You don't list any, just that it must be rails. Why is that?
You really have some clean code there.
Don't fuck it up by wrapping with wordpress clutter and junk.
p.s. github pages runs Jekyll, you just push and it runs, no CI required unless you want to do custom plugins. https://jekyllrb.com
Why not just use Jekyll, Middleman, or any of several other static site generators?
If you're looking for theming and plugins, you still have numerous options.
Friends don't let friends blog in WordPress.
There's a few different ways you can do it.
1) If your server allows it you can use php and then use a php include for the header file. Locally you'll have to run something like MAMP/WAMP to test it.
2) You can include it using javascript. Not the best practice, but it does work.
3) You can look into a static site generator such as Jekyll which will let you have partials or templates.
Personally, #1 is the easiest way to handle it, and most servers are going to support it anyways.
1) To get a website at username.github.io, the repo should be named username.github.io - note: that will only work for your username. Full details here
2) GitHub Pages is a hosting service, that uses Jekyll to auto build if it needs to, but can host any static site.
3) Jekyll is a static site generator. Basically, it takes a directory of markdown files, applies a theme to them and produces HTML for them. The official site will go into more detail about how it does that. It was initially created by one of the GitHub founders.
4) If you are using Jekyll, you can apply different themes to your site to change the aesthetics. It's all HTML, CSS, and JavaScript at the end of the day so they are the main ways to alter the aesthetics.
edit: added link to pages documentation
Its not difficult to create a batch file to run pandoc against every markdown file within a folder (including recursion if necessary). I've done something similar to convert technical docs to HTML. Correct that this won't create an index or menu for you.
I'll add that u/jidloyola provided a nice solution. Jekyll is a static website generator that consumes markdown files. IMO this is definitely worth a look.
Make a website! You can buy a domain from Google or some other company! This also has an added perk of being able to get your own email address!
While you could rent a server and write your own back end to serve your front end, if you just want something simple make a website using Jekyll or hugo and host it (for free) using GitHub pages.
You can put anything on there, a blog, a portfolio with your school work, the sky's the limit!
Hope this helps
If this is more for your personal blog, I like using Jekyll on github, since I keep most my code there anyways, and its free with github pages.
If instead you plan this to eventually be the official site for your game once you get further along, ManaKeep may be a nice option; its a website builder made just for indie game devs, and includes a blog feature =) (made by me so happy to answer any questions if you had any)
Cheers,
Sounds like you need templates! If you are having to copy paste the header across the pages you are now ready to move on to a slightly more complex setup but it will make maintenance like this easier, what are you using if anything as a build tool?
One of my favourites to use for a super simple site, and minimum changes to what you have already is https://jekyllrb.com/. There are many other options to choose from though.
>... I’ve chosen the manual route as far as category front matter is concerned.
Jekyll has Front Matter defaults for this case. They allow you to set defaults for each file at a given path. I think they would also help here, e.g.:
# in your config.yaml
defaults: - scope: path: "_posts/pictures" values: category: "pictures"
Do you really need a dynamic, database-driven site?
You might consider something like Jekyll where you can easily manage/update static files but still make it look pro. On to of this placing things into an SCM like Git is really nice.
For a simple website with static content most people don't need a database and can alleviate all the SQL injections, XSS and other nasty stuff that comes along with the territory.
Complimenting this to further lock things down you could use the chattr command to make your static files immutable, only removing the chattr flag when they need to be updated (you could write a simple script for this and tie it into your git orchestration).
On top of this read up on Apache file permissions, considering using Let's Encrypt if you have valid DNS entries.
I would also suggest putting things on a cheap VPS host, they can run as low as $3/month from OVH or Vultr. That way you don't need to worry as much about home server availability, issues with your ISP etc.
Jekyll[0]. And it is hosted on GitHub pages[1].
Here is the source: https://github.com/lalwanivikas/lalwanivikas.github.io
I’m hosting through github pages because they have built-in support for jekyll. I like this setup because it’s free and I can completely customize the code.
No, but I use jekyll. It's fairly quick to set up and very simple to work with because it's just static files. It's great for a project like this - a small site for someone who is tech savvy and doesn't need the huge overhead of a CMS and a database, etc.
Of course, there's no wrong way to build your portfolio site. If you're most comfortable with [insert cms here] and think you'll do your best work within it, use it! The output matters 10 times more than what you build it with.
SSI is the simplest solution. Just using something like <?php include 'nav.html' ?> is super quick.
If you want to stay away from SSI there are solutions like Jekyll
For static websites I like Jekyll. You can use a pre-built theme to begin with, and modify it as you go along. It is also very easy to host on GitHub Pages (which is also free).
Yep, if you want a static site page that can be easily edited just spend a little extra time and learn something like Jekyll. Super easy to pick up and get looking right, supports Markdown rather than having to know all HTML, and has themes designed for small businesses across a few different theme sites.
If you're willing to pay to have your domain direct to Notion, just go the extra mile and host a Jekyll site that works better. There's so many tutorials out there to get a perfect website that doesn't follow one format and load after 30 seconds.
You certainly don't need to use a CMS however each page on your website will have common elements like the head section containing all of your CSS and JS includes. You likely want some kind of menu and logo etc.
If you hand craft this but it means that any time you change these common elements you have to do it on every page you have. One thing a CMS does do is allow you to separate these common elements out and then recombine them with data using a template engine.
You might be interested in a static site generator, which also uses a template engine and normally markdown files to define the content. You configure your template files and where your content is and the static site generator spits out all the correct HTML that makes up your site. You then just upload all of these files to your website via FTP or ideally Rsync.
I like python so have used pelican however Jekyll is probably the most popular. Github uses this in its Github Pages feature. With this you can commit & html & markdown files as content and it is automatically built into a website and hosted by github. This has the glorious benefit of having all of your content in source control with a dead simple deployment system. Multiple people can contribute content which you can easily manage via pull requests.
To be honest, most of the building side I did months ago as part of a The Hacker Within tutorial; I don't remember much of the details besides everything being really finicky. As far as I remember, we followed the Jekyll Quickstart Guide to build a webpage, pushed the resulting directory to a GitHub repo, and that was all it took for the page to be visible online. This guide seems to be pretty comprehensive on the GitHub Pages side. One of the hardest parts was getting my domain to point correctly at the GitHub page so that I could use <first name><last name>.com instead of the .github.io url. It took a lot of fiddling on both my domain's registrar and the GitHub pages menu, and it wasn't clear why the settings I ended up with were what worked versus what other tutorials said.
Once the site existed though, I could just edit the index.md page using markdown and jekyll automatically built a new corresponding HTML page for me. That's the nature of all the changes I've made in the past few weeks.
I'm sorry I can't be more directly helpful - if I can find the slides to that original tutorial I'll link them here.
Perhaps look at something like Jekyll, which is sort of a content management system for static sites. This is what I tend to lean towards.
Or there are also old school server side includes. I’m not sure I would recommend this route as it couples your pages to a specific web server, but if you’re going for lightweight, it might be worth it to you.
Who is the end user? Could you use a static site generator instead of a CMS? Eg Jekyll or something else . A little less WYSIWYGy (Markdown for the input text) but less things can go wrong once it's running because the output is just static HTML.
Make sure all your markdown pages have a YAML Front Matter, even if it is blank. For example:
--- ---
# Why I Love Jekyll Lorem ipsum...
I moved my Jekyll site over to GitLab the other day and everything is working fine (including the markdown). Here's a link to the repo if you want to take a look. If you got more questions, don't hesitate to ask!
Not quite - looks like you need to brush up on what a static site generator does. With Jekyll, you make all of your changes offline on your machine. Then, you run 'jekyll build' in your terminal, and Jekyll generates for you a website that you upload to a server. Check it out: https://jekyllrb.com/docs/usage/
It's generally convenient enough to make a change and upload your WHOLE site each time, just to make sure every page is updated correctly.
It's really simple once you get the hang of it :)
By calling Jekyll a "generator" for static pages means that you can include snippets of code to re-use throughout the pages you make. Yes, you certainly are still writing all of the HTML/CSS/JS markup. But Jekyll shines by giving you structure of how to use that code and then compiles it for you into static pages.
For example, rather than having to build 5 pages and copying the same <header> code in over and over again, you can just create a file called header.html and put it in the _includes folder. Then in any page that you want to use that header code you just type in {% include header.html %} (docs on includes here).
Now when the site is "compiled" by Jekyll it'll create your static page with that header code put into it. This is very nice since any changes made on the header.html file only needs to be done one time, in one place, and all of the pages that use that header get updated.
Same thing is done by using the _layouts folder, so you don't have to enter in the <html><head> tags on every page. You just do it one time and then use that layout where needed.
Does not sound like something you need React for. In fact it may hurt your SEO to use React on the client. I would look into a static site generator like Jekyll. Now onto your question, there are whole sites devoted to themes for Jekyll based sites. This helped me stand up a personal site in hours rather then days.
If you are looking to do React for learning purposes, great! I love React. You can still look at other portfolio sites and see what they are doing and take inspiration from them.
Github Pages is totally free, but you'll have to redesign your site as a static one using Jekyll or something.
If you absolutely want to stick to PHP and wordpress, you can either switch to a free host such as 000webhost, or purchase a cheap hosting from NearlyFreeSpeech.net (they accept bitcoins too!).
Jekyll or some other static site generator. Compiles your source files to HTML that's served up by Jekyll itself, or Apache. That's about as lightweight as you're likely to get.
Try using a static website builder like Jekyll or Hugo. They can dynamically build static .js files, along with .html files, using data from .csv files. Should be super simple.
http://gohugo.io https://jekyllrb.com
I'm a Jekyll fan... but in your case I suggest you put more energy into Hugo. It builds faster and runs as a single binary application. (Nothing to really install.)
This is a very large topic with many things to consider but heres a quick overview:
First you have to select a content management system (CMS) based on the needs of the site. There are plenty of existing options to choose from and if you're really keen you can make your own.
There are 3 main types of CMS:
- Database driven CMS. This type of CMS stores most of it's content in a database and are generally used when a lot of dynamic content is required. Wordpress is probably the most common database driven CMS.
- Flat file CMS. This type of CMS does not use a database, instead it stores the content in flat files on the server. This leads to faster page load times. Grav is a good example of a flat file CMS.
- Static site generator. Similar to a flat file CMS, a static site generator does not use a database. This kind of CMS pre-compiles your website into static files which are uploaded to the server. Jekyll is a good example of a static site generator.
Once you have selected what CMS you are going to use, you will need to create a theme or template using your design. How you create this is very dependant on the CMS you choose.
How you deploy/manage the website is also very dependant on the CMS you choose. My advice would be to do some research into the many options available and find one that suits the project then find out how to adapt your site to that CMS.
I may be misunderstanding the question, but for simple websites with mostly static content, you can use a static site generator. This removes the pain of managing all of your HTML files independently by keeping their contents separate from the template, and makes blogging fairly simple. There isn't any real routing, since every route is just mapped to a file built by the generator. Here's a list of some of the top static site generators. I deploy my personal website via GitHub pages, which uses Jekyll. If you already know Angular or React, then the templating systems for these generators will be familiar. The speed benefit of using a static site is enormous.
You can certainly also build a one-page dynamic app with Angular or React, and serve it as if it were static. This really has the same effect for the end user, but you can achieve much more interactive pages as well as more advanced routing.
This is what I use for my blog - static stuff, just like you're saying.
It's really great. You could conceivably host it on Github and point their domain to it. Github doesn't want you to do that of course (they want you to host a blog) - but you could definitely get away with it for some time.
It depends on what you're talking about… Do you want to build static websites, websites that run on a CMS like WordPress, or full-on web applications?
Illustrator would not be the way to hard-code websites. What you'll need in any case is a good text editor like Sublime Text, Notepad++, Atom, etc.
I would suggest looking into Jekyll first, then later Rails or WordPress.
Right. In the workflow I'd like, I would:
- compose my text in the text editor of my choice, possibly to include embedded/linked images and so on.
- use a static site generator-like tool; or actual static site generator like Jekyll or Hugo, to manage structure and push to publishing location (LBRY) either exclusively or in addition to a separate hosting situation.
So, there would be a script which would:
- read a simple config file to determine my channel(s), then
- determine which files have already been published, then
- automagically publish un-published files
- preferably first determine if file is still in draft stage
There's no special reason why such a tool would be required to handle only text. It could determine same for video, images, audio, 3D models, comic books, PDF, epub, whatever. It simply would need to have some sort of indexing function to determine what has and what has not already been published and, preferably, what is not-yet-ready to be published.
Using free GitHub Pages + a custom domain might be sufficient for any type of static portfolio site, and there are a lot of community themes you can use to bootstrap off of. Static site generators like Jekyll and Hugo can be integrated if you want to host a blog for writeups.
True, making a static website manually can be a bit annoying. Things like Gatsby are called static site generators or headless CMS. You could look at this list, maybe you will find something for you (and no, I don't suggest static site generator as default only because there is one mine on the list :P)
BTW, GitHub has build-in static site generator, Jekyll.
Well yes you can but you have to move away from Wordpress or other content systems and build something custom.
You need some experience writing code with html/css and Markdown. Theres Github pages which provides free hosting for static websites. And then there's Jekyll which let's you make great blogs and static websites. If you are complete beginner to this maybe this blog post can help you set a good looking Jekyll blog.
It takes a bit of patience(actually a lot!) for non-programmers to get started using Jekyll or other "non-CMS" Solutions but it has the least monetary investment. All you need to buy is a domain name (and that is optional as well since you get a free github subdomain).
But I couldn't recommend this to someone with no experience writing code. You can learn this but the investment in time is way too high. A better option for you is to write on Medium (or guest posts on other blogs) and get some money out of it. Once you do, you can invest it in your blog. It will cost you about $60/year for shared hosting and $12/year for a domain name. About $80 is all it takes to run a great looking blog for year. There are lot of great looking free themes available.
You might have to do a bit of learning, but Jekyll will make this much easier (and you'll still be learning about HTML and CSS):
Jekyll is near and dear to my heart. Suddenly everything "clicked" when I began to use it and I had a much clearer picture of web development.
Couple questions: why Java, why Spring, and what are you trying to do?
To actually answer your question: doesn't matter. To me, it's totally dependent upon what you're trying to achieve. If you're just looking to learn a front-end framework for the hell of it, I'd recommend React. I've spent years working with the framework, and have enjoyed it greatly.
But I've only used React when working with actual businesses as a dev and QA. Personally, at home, I run my site using the Jekyll framework, which is Ruby based. It's works really well for me, because my site is static as hell. No feeds to update, no messenger to account for.
If you're making a static site and need a simple frontend: Jekyll.
If you're making a dynamic site where you need to manage state and update components: React.
Are you starting something new or have you been on wordpress for long?
I'd say do some research into alternatives there are a lot out there both if you want to selfhost or otherwise. I know it might end up being a lot of work but I'd recommend you look into jekyll. It's also a great learning-opportunity if you wanna get into coding!
Are portfolios anytime important?
Maybe it is something specific to western companies, or western market. I live and work in Ukraine and I have never seen anybody asking for a portfolio. I also have not heard anybody sending their portfolio instead of a CV or a LinkedIn profile link.
By the way, if you really care what's under the hood of your site you might consider static site generators like Jekyll or Hugo in combination with, sat, GitHub Pages. As a developer, when I browse sites made this way I know that these are not just sites - they have their souls.
Yes, you can serve your website from a private GitHub repo using GitHub pages (free!) and use a custom domain address. That is how I have my personal blog setup now. I have a post with instructions :)
https://davidjchambers.com/2017/12/27/site-setup.html
See the ‘Custom Domain and Hosting’ section.
If you don’t want to use GitHub pages there are a slew of other providers where you can host your site
You can get all nerdy and set up automatic deployment via a CI, but you're probably not working at a scale where that's needed. Copying the rendered files will be good enough for a basic website and host it on the cheap at any number of web hosts.
If you are comfortable using Git and GitHub, you can host static sites or Jekyll-generated static sites on GitHub Pages. It has support for HTTPS, custom domains too.
You could turn your site into a Jekyll theme and then have your client write the content in simple Markdown files. Your site would remain static and your client wouldn't have to dabble with the technical side.
Late comment, but I would follow this guide:
https://jekyllrb.com/docs/pagination/
It's fairly simple to set up and works on Github pages.
(I have it set up on my personal site which runs on GitHub pages)
The best approach is based on how you're going to be building out the pages...but the solution usually ends up being a variation of creating a template for all of the parts of the page that will be repeated and then applying that template to pages that have unique content.
The Layouts page in the Jekyll documentation can give you a pretty good idea of how this is usually accomplished.
Since you're going all static, the best static website generator is probably Jekyll.
For managing contents, if you want to keep it on the front-end, you can use something like Vue.js and keep your data in JSON.
I think I'd be worth looking into a static site generator like Hugo (my personal fav) or Jekyll. They don't require a database. You just write you content out in markdown (with front matter) and it spits out a static website based on the html templates you created.
Really speeds up the process vs handcoding since you can make partial files and base templates, but they dont have a lot of the complications that come with a traditional CMS like Wordpress or Drupal. (Plus the sites they make are usually way faster, more secure, and cheaper to host.)
Someone else also mentioned grav which is also a good option since its document based. It's not a static site generator but a flat file cms. Both are nice for sites like yours tho since no database.
Edit: Wordpress isn't a bad option tho tbh. I just wouldn't choose it for your particular use case.
Für eine Vereinshomepage reicht ja eine statische Seite. Dafür gibt es static-website-generatoren wie jakyll oder pelikan. Alles was du können musst, ist etwas markdown schreiben und das skript aufrufen, dass daraus html macht.
Von wordpress würde ich Personen, die von der Materie wenig Ahnung haben, abraten. Als eierlegende Wollmilchsau und ausgewachsenes CMS benötigt es viel Pflege und eine wissende Einrichtung. Gerade dieses CMS ist eigentlich ständig im security ticker von heise Gast, wie zum beispiel heute wieder.
So the problem with that is WordPress kind of has a flavor of PHP. Mostly, you'd be learning to extend and use built-in functionalities, which wouldn't necessarily transfer all that much to being able to build everything from scratch. Then again, being a WordPress-only developer is not a bad thing, a good one is always appreciated. My advice? Check out stuff like Jekyll if you just want to do static sites. Jekyll paired with basic gulp lets you use html/css/js in a normal fashion, but also lets you explore components, props, templates, liquid (shopify), scss etc. Also lets you understand that you usually need an environment, how it works and what not. Think of it as static sites on steroids, you can still write html/css/js like you normally do, but if you wanna do more later on, it's so easy to just start using SCSS or start making components, like you make a button.html component you style, and then wherever you need a button, you'll simply {% include button.html %} , Jekyll will take care of the rest. Doesn't hurt you can host those websites for free with GitHub Pages, letting you showcase your work, alongside your repositories.
GitHub pages uses Jekyll for building your pages. So we can create pages using two ways: 1) html 2) markdown
In markdown mode, md is converted into html. There is no need to work in markdown, it's just a lazy way to write html.
Back to your question. You want to create multipage sites. So, you could directly create index.html, page1.html, page2.html, etc. But if you are creating a blog or collection of pages, you could use Jekyll to build pages automatically for same type of pages.
Documentation: https://jekyllrb.com/
Feel free to ask more questions.
> Hm, yeah it might be in how jekyll processes the markdown?
No, this is in the kramdown itself. Checked with online kramdown.
> There are limits to it, and so for more advanced formatting I think you and I both need to look into the includes (and passing parameters into them) thing.
The best I think I could do was to look inside actual Jekyll code - this page and it's source - they don't do any includes - they just paste raw HTML, seems there is no better way.
Okay so I dont have live code but I looked over the 2016 page and generated this bit for you to try out. I believe it should have no problems, but you can likely do things a bit better.
The idea I went with was to indicate in the frontmatter that would use a default layout but this one would be for a given year, or can be applied as defaults to each page for this year, or even, through the _config.yml defaults settings documented here
year: 2016
nav:
- label: about
title: meeting main page
path: / - label: location
path: /location.shtml - label: programme
path: /pr2016.pdf - label: abstracts
path: /abstracts.shtml - label: fee
path: /fee.shtml - label: registration
title: register
path: /registration.shtml - label: links
path: /links.shtml
The layout page this would affect can look like so:
{% capture yearSubPath %}/{{page.year}}{% endcapture %} <div id="top-two"> {% for link in page.nav %} <a href="{{link.path | prepend: yearSubPath}}" title="{{ link.title | default: link.label }}">{{link.label}}</a>" " {% endfor %} </div>
In case you didn't know there are some really great static site generators for blogs like (Nothing against WordPress)
Either way great work with the site, the colors are looking really slick.
- No. Posts only contain the post text and meta data. The page layout is separated from them.
2+3. Posts are written in a simple markup language like Markdown, so you can use every editor that supports that, then push the post to your repository and create a new build. You can add HTML to your post but don't have to.
The Jekyll documentation is good and should answer all your questions. Give it a spin: https://jekyllrb.com/docs/home/
Hello, building (static) website, books, presentations, radio shows, and more with jekyll? Let's make jekyll 4.0 better, faster, ....! Yes, you can!
To quote Olivia Hugger (@dog_awoo), the Jekyll Open Source Project Lead writes:
> Now is a great time to finally take on the feature you’ve wanted to see in Jekyll for ages! > Just open an issue or experiment with the code to get going! > > (Source: Jekyll 4.0 is on the Horizon!)
Happy Jekylling. Cheers. Prost.
> I'm still not exactly sure what Jekyll really is
Jekyll is a blog-aware, static site generator written in Ruby. I'd highly recommend that you read the documentation on the Jekyll website to learn more about it.
Github Pages has Jekyll pre-installed for every repository.
> Additionally, what exactly is a _config.yml file?
YML is a file format that's a bit like JSON, but more concise. (In other words, it's a data serialization language). It's often used for configuration files. In this case, _config.yml is used by Jekyll as a, uh, config file.
> Is this something I create myself, or something that I have to obtain externally?
Not exactly sure what you're refering to.
If you mean the config file, yes, you'll create that file in the root of your web folder. The documentation page you linked shows what you need to put in the config file to enable the SEO plugin.
If you mean the plugin itself, it looks like that comes preinstalled, based on that same documentation page.
So my suggestion is not about templates, it's about a system. I use Jekyll to create my static websites. It gives me the power of a website with server-side code, without any of the bloat or the hassle.
Your parents don't need a CMS or redis. They just need a better motherfucking website. :)
Also, static site generators are awesome. Jekyll is the biggest and probably the most popular, but there are lots of others.
One of the best static generators especially if you're familiar with reactjs.
Also, some developers prefer to use jekyll.com. It was quite popular before.
Jekyll ~ 30 000 stars
gatsby ~ 13 000 stars
You may want to consider a static site generator, like Jekyll, https://jekyllrb.com/, with a tool like SiteLeaf, https://www.siteleaf.com/, to act as the CMS.
For the checkout, you could try the Shopify Buy Button, https://www.shopify.com/buy-button.
This combination of solutions should be (1) very fast (this is a significant advantage for a static site generator), (2) very secure, and (3) relatively inexpensive.
If you're familiar with HTML and CSS, you can create a static site with Jekyll. I recently created my blog this way and prefer it to Wordpress because even the simplest themes contain a LOT of unnecessary code.
Jekyll is an awesome flat file CMS and it works out of the box with Github pages if you wanted to use that as your hosting. You can easily point a domain name to it as well. Or you can host it elsewhere pretty easily.
You will need a really basic idea of web development and particularly with Ruby.
Jekyll is a framework that does more than just parse markdown. It helps you organize your code into reusable templates and layouts, manages posts, and allows you to configure pages/posts with front matter. It's also has a pretty decent size library of plugins. https://jekyllrb.com/docs/plugins/
Danke für den Link. Hindsight ist 20/20, zeigt aber mal wieder schön, was man nicht tun soll. Ich kann es Blogs, die politisch brisante Dinge veröffentlichen nur empfehlen, statische Webseiten zu benutzen. Klar, man muss auf etwas Komfort verzichten, die Autoren müssen eine neue, aber zugegeben einfache, Art lernen wie sie die Beiträge schreiben (markdown/kramdown) und wie man mit Git umgeht (hey ein einfaches commit schafft jeder), aber am Ende ist es das wert.
Denn eine statische Webseite bietet erstmal nach außen keinen Angriffspunkt durch Scripts. Kommentare kann man durch bspw. Disqus implementieren, was nur eingebunden wird, aber keinen Zugang zum eigenen Webspace bietet. Dann hat der Angreifer nur noch die Wahl den Webserver selbst anzugreifen.
As already suggested, Github is great for static sites or even a blog.
Saw someone else suggesting Zoho for email, which is something that I used to do, and while it is a good service, I must suggest that you check out Mailgun. I use Mailgun to forward incoming emails to my primary Gmail address. Gmail also allows for you to send mail from the address you're receiving it as using SMTP.
I use Jekyll and Github Pages - free hosting.
Jekyll is pretty neat and you can build your portfolio/blog. There is a lot of starter themes, but I recommend building/designing your own if you want to stand out.
For what it's worth, wordpress.com is the wrong place to go if you are privacy-conscious and want a free blog. I would say you should learn how Jekyll works and use a free GitHub Pages site instead.
Everyone is recommending you take on a huge framework and or some larger language. What I would recommend is looking into to smaller workflow tools like Handlebars which does the temaplting you're were just asking about. Also for a basic Static CMS I would highly recomend Jekyll. You can also host a Jekyll site free on Github, which is helpful as well!
People tend to recommend stuff that goes way to deep and can get messy fast. I would stay minimal and bare bones, it makes learning a lot easier.
If you have any questions feel free to ping me.
Look at Jekyll, you set up a template, and then you just write your blog posts in markdown (same format that reddit uses for comments and posts) in their own files.
Github pages supports Jekyll, so you can use GH pages to host your blog, meaning you don't need to fuck around with servers. If you do want your own domain name, you can point your domain name at the GH pages url, and set up a CNAME file in your GH pages repository.
Like the others have suggested, look into an easy-to-use CMS so you don't have to hardcode the content directly into the .html files.
Jekyll is great and the pages load quickly. You can write the blog posts in markdown. Easy to run on GitHub pages, too. Check it out: https://jekyllrb.com/
I've heard that Middleman is good too, though I haven't used it. https://github.com/middleman/middleman-blog
You're welcome.
Jekyll is probably the most prominent static site generator - it has a large community and loads of themes, so it's a good place to start, but you can find plenty of alternatives if that doesn't float your boat.
There are quite a few good static site generators, like https://middlemanapp.com (Ruby) or https://phenomic.io (NodeJS/React/Webpack) or https://jekyllrb.com (Ruby). They allow you to encapsulate parts of your site or automate them.
Made my personal blog using Jekyll which I host under Github. Throw in a repo username.github.io, create a CNAME record inside the repo and point your domain DNS to Github. Free hosting, rapid page/posts with markdown language and your own CSS/JS capabilities.
If you're looking for this to be a landing page or blog I would convert it to a Jekyll site instead. It's much more straightforward for blogging, landing pages, and doing simple updates.
If your app is going to be backed by a data model or database Rails may be the better option. I would start with a new Rails application then add in the template. You're going to need to create routes for all of the pages, convert the static HTML pages to ERB files, and then convert the static links in the template to Rails path helpers.
Alternatively you could just use Rails as an API and keep your website relatively static. When you need to pull in information from the database you could send AJAX requests to your Rails app.
Very interesting ideas for basketball. Nba has the efficiency index for each player that measures the difference players make on the court and it is a good start.
I used Jekyll and usually write javascript and html, css. Jekyll speeds up the process though. Hugo is a similar one. There are a bunch of static site generators.