I am looking to "automatically" create images from Jekyll posts. Either dynamically or on site build, I am not picky. I know I can create images from html and css, so this must be possible, but I am not sure where to start to do it in Jekyll.
From what I can tell this seems like it would have to be when the site builds since I don't know of any way to return an image using a static page haha.
Related
I am a beginner at web development, and I just want to make a small website based on jekyll. So I have created 4 posts, and they show up nicely on the website. The thing is that they actually show up on the bottom of the page, under stuff I put in index.md (which takes up like the whole page); I want to find a way to move the whole post section to the right so it's parallel to the content in my index.md. I tried CSS flexbox, but I can't find where to add the codes because the posts are found in a separate folder and don't show up in my index.md. What should I do?
You might want to try a different Jekyll template from the one you are using now instead of adapting your current one. The template my university provide for Jekyll in our institutional GITLAB, for instance, has posts above content in the index.md file. And it can be tricky to adjust themes.
However, there are Jekyll templates with a two-column layout with a side-bar.
You might want to check out the "Minimal Mistakes" theme or the "Hyde" theme.
I have a static HTML site hosted on github pages and I was wondering if there is any code that could use a template to fill in the header and footer of every page? I thought I remembered learning this a long time ago but don't know what to search. In my mind I'm picturing creating a header.html and a footer.html and just pulling from those files on each page...idk any help is appreciated!
Github pages is also 'Jekyll'. You can create 'layouts' that can have common headers/footers and use them across pages. I'd recommend looking at some default Github pages templates to get an idea of how it works.
I want to know if it is possible to hide page(s) in Jekyll when pushed to production. For example, I have a page called crazy-toes that I'm currently developing. But have different edits/changes for other pages that need to be pushed live. Is there a way if someone types in their browser mysite.com/crazy-toes/ they go to a 404? I know there is the published variable for the Front Matters, but for multiple pages, it doesn't seem efficient.
You could store the page in Drafts.
I'm using static html pages and incline js to generate dashboard. The backend is go.
However, as number of pages growing, I have to maintain a lot of html pages, and many of the block elements are duplicated.
I'm wondering whether there're some cases to use jekyll to generate dashboard pages, since jekyll can convert pieces of elements into complete htmls? So that I can modify one part and the modification take effect on every html pages that generated.
Are there better framework to do so?
Thank you!
If you're duplicating elements, then those are the perfect pieces of markup to put into a layout and/or include. That's exactly what those are for.
Each individual page you need can reference a specific layout in its front matter. Includes can be used within the individual pages or within the layouts or both (and can be nested).
The Jekyll Documentation is ok for this, but to wrap your head around it I find it easiest to look at the documentation together with a few existing Jekyll templates to understand how it all fits together.
after a bit more dig. I found that packages such as Grunt and Gulp can be used to generate htmls from separate parts.
I created an HTML website in dreamweaver it has a index page, nav-menu and around 10 other linked pages. I did not build the website from templates I just copied and pasted.
I want to upload this website using Wordpress and Ive never done it before. I'm still learning but need help figuring thing out;
I saw that in order to upload the page to Wordpress I need to create a so called theme and in order to do that I need to create different files like index.php, header.php, footer.php etc
My question is do I have to do that process with all my pages?
I mean about.html contact.html jobs.html?
What is the ideal way to do it?
A WordPress template is essentially a set of PHP pages and CSS that defines how your WordPress site looks. Template Development Link
Manually converting your site is going to take time. The advantage of the WordPress site will be that your site will be easier to update down the line.
How difficult building your template and pages is really going to depend on how clean your original css and pages are built.
First, build your template. You are going to try and pull your CSS and apply it to the template pages.
Next, you will need to use the WordPress GUI interface to add pages and include the content from your original site.
Again it is going to come down to how much of your formatting was done inline and how much you leveraged CSS in your presentation. A lot of table formatting for example will be more difficult to translate.