У меня есть вордпрес вебсайты они в динамике работают т.е надо постоянно обновлять версию вордпресса, плагины и т.д.
Как перевести в статик чтоб не надо было обновлять?
Есть специальные плагины что переводят в статик но они не работают с галлереями что я использую.
На старом привете Other Side хотел посмотреть детали типа взять халтуру но того привета больше нет также как и здесь этого участника....Также есть инструкция как можно перевести в статик без плагинов но я не уверена как ей следовать.
Люди просят сделать им подобные вебсайты но я не собираюсь постоянно обновлять ихние версии а статик пока не работает.
Через месяц я буду присутствовать на встрече где будет много богатых людей
с их родственниками и могу сделать вебсайт
предложив им купить его но вебсайт должен быть статик.
Естественно кто поможет разработать' работающий продукт (перевод на статик) получит вознаграждение
и детали должны быть оговорены заранее.
Можно писать в личку.
Как перевести вордпресс вебсайты в статик?
Как перевести вордпресс вебсайты в статик?
Внизу инструкция как перевести динамик вордпрес в статик.
Не уверена что выбрать:
Jekyll, Hugo, Gatsby...?
//инструкция
convert WordPress content into static pages.
You can convert WordPress content into static pages.
This process is often referred to as "static site generation" or "static site conversion." Converting a WordPress site into static pages offers several benefits, including improved speed, security, and reduced server load. Here's how you can do it
:
Choose a Static Site Generator (SSG):
There are various SSGs available, such as Jekyll, Hugo, Gatsby, and more. Choose one that best fits your needs and is compatible with WordPress.
Export WordPress Content:
In your WordPress admin dashboard, go to "Tools" -> "Export."
Choose what content you want to export (posts, pages, media, etc.) and download the XML file.
Install and Configure the SSG:
Install the chosen SSG on your local machine or server.
Configure the SSG to use the exported WordPress content as the data source.
Convert Content:
Each SSG has its own way of handling content conversion. You'll typically write templates or configure settings to map WordPress content to your static site's structure.
Generate Static Pages:
Run a command or trigger the SSG to generate the static pages based on your configuration and content.
Review and Test:
Review the generated static site to ensure it looks and functions as expected.
Test all links, forms, and interactive elements to make sure they work in the static environment.
Deploy:
Upload the generated static site to your web hosting server or a content delivery network (CDN).
Update DNS Settings:
If you're moving your site to a new domain or hosting provider, update your DNS settings to point to the new location.
Configure Server Redirects (if needed):
Set up server redirects from the old WordPress URLs to the corresponding new static URLs to maintain SEO and user-friendliness.
Regular Updates:
Keep in mind that the static site won't automatically update when you publish new content in WordPress. You'll need to regenerate and redeploy the static site whenever there's new content or changes.
Remember that this process requires some technical knowledge, especially if you're working with command-line tools and configuring templates. Additionally, dynamic features like comments and user logins won't work out of the box in static sites. You may need to consider third-party services or JavaScript solutions for such features.
Overall, converting WordPress to static pages can be beneficial for performance and security but may require some effort in initial setup and maintenance.
Не уверена что выбрать:
Jekyll, Hugo, Gatsby...?
//инструкция
convert WordPress content into static pages.
You can convert WordPress content into static pages.
This process is often referred to as "static site generation" or "static site conversion." Converting a WordPress site into static pages offers several benefits, including improved speed, security, and reduced server load. Here's how you can do it
:
Choose a Static Site Generator (SSG):
There are various SSGs available, such as Jekyll, Hugo, Gatsby, and more. Choose one that best fits your needs and is compatible with WordPress.
Export WordPress Content:
In your WordPress admin dashboard, go to "Tools" -> "Export."
Choose what content you want to export (posts, pages, media, etc.) and download the XML file.
Install and Configure the SSG:
Install the chosen SSG on your local machine or server.
Configure the SSG to use the exported WordPress content as the data source.
Convert Content:
Each SSG has its own way of handling content conversion. You'll typically write templates or configure settings to map WordPress content to your static site's structure.
Generate Static Pages:
Run a command or trigger the SSG to generate the static pages based on your configuration and content.
Review and Test:
Review the generated static site to ensure it looks and functions as expected.
Test all links, forms, and interactive elements to make sure they work in the static environment.
Deploy:
Upload the generated static site to your web hosting server or a content delivery network (CDN).
Update DNS Settings:
If you're moving your site to a new domain or hosting provider, update your DNS settings to point to the new location.
Configure Server Redirects (if needed):
Set up server redirects from the old WordPress URLs to the corresponding new static URLs to maintain SEO and user-friendliness.
Regular Updates:
Keep in mind that the static site won't automatically update when you publish new content in WordPress. You'll need to regenerate and redeploy the static site whenever there's new content or changes.
Remember that this process requires some technical knowledge, especially if you're working with command-line tools and configuring templates. Additionally, dynamic features like comments and user logins won't work out of the box in static sites. You may need to consider third-party services or JavaScript solutions for such features.
Overall, converting WordPress to static pages can be beneficial for performance and security but may require some effort in initial setup and maintenance.