How to maintain a site without an admin panel?

Question

GitHub

Good afternoon!
Such a subject - there is a site with about 400+ pages, a site without an admin panel. Everything is made up by hand, has no documentation, a huge pile of files. The whole thing is administered through Bitbucket, Middleman, etc. That is, each page is a completely separate entity. However, the part of the site called "blog" is powered by Wordpress and has an admin panel (everything is clear with it). The rest of the site is very difficult to administer, since I'm used to Wordpress and PHP, and everything is in Ruby, Slim, etc. Working through the code is inconvenient, there are many edits to the content (text, pictures)

I have the task of making new pages on this site, hence the question arose:
Is it possible to install WP in new directories, is this an adequate solution, since let's say if you make 20 new pages then 20 WP installations this can create even more confusion.

Maybe there is an option to install Wordpress in one of the directories, and prescribe rules for pages like that without violating the current site? i.e. for new pages only use WP.

Or maybe you can do something differently, but working with statics at 21 is clearly not the best way out, since there are many edits to content.

Answer 1

You can put 1 wordpress and convert all pages into a page template, then create a page for each template. (Yes, very monotonous work, but even so) then you can already use the power of wp for gradual integration. For example, if there is a blog on 50 pages, then put it into these 50 templates and already add news through the admin panel. This is clearly more convenient than changing the news block every 50 pages.

the question is how to avoid new installations of WP on each of the directories

The question is how does it work now. All on the same domain or different?
If there are different domains, then there is a multisite in Wordpes.
If on one, then just save the necessary nesting. When the parent for the page is specified.
And then you can gradually adapt all the templates.

Answer 2

I don’t rummage for WordPress, I would throw an admin panel, routes on the chest in a couple of hours. I put all the finished html into views.
Xs what kind of routing did you have there, but I think you can get the necessary html from the url. And so I would make a controller in which I looked, if there is html already ready, spit it out. If there is no such html, then get it from the database and give it already

Answer 3

I'm not sure if I understood the description of the situation 100% correctly, but try screwing one of the options below:

• textolite.ru
  
• https://github.com/Self-Evident/OneFileCMS
  
• https://pulsecms.com/
  

This is all CMS for static files, and not in markdown.

Answer 4

In general, this is completely solved by installing nginx in front of all this economy in order to locationroute requests to different parts of the site through it, which become just different upstreams for it.
First, set everything up so that the links work correctly in the current configuration (static + WordPress for a blog). After that, put WordPress (or whatever you decide to use there) somewhere nearby and begin to gradually redo the existing pages, adding new rules to the nginx config along the way. When the work is completed, it will be possible to simplify the resulting config and get a working solution.
At the same time, you will get the opportunity, for example, to optimize the return of statics so that nginx itself gives it away, without pulling the upstreams.

Answer 5

WP on the site should be only one.
Throwing all static pages into the WordPress database is a couple of hours work for a PHP programmer. Then you can work with them only through WordPress, that's all.