Static files: move source to a dedicated directory.

[dalf]

Since it is a topic in itself, here a new issue :

From #137 (comment)

In first order we should separate source code from the ./searx/static folder.

I would see:

• src/static
• src/searx
• src/searx/static <-- built files

But a lot of stuff expect searx source code in the searx directory.

So If the source folder for the static files is static/src or just static.

static (or static/src)
	themes
		oscar
			img           # searx/static/themes/oscar/css/images AND searx/static/themes/oscar/css/img
			js            # searx/static/themes/oscar/src/js
			less          # searx/static/themes/oscar/src/less
			package.json
			gruntfile.js
			README.rst
		simple
			js            # searx/static/themes/simple/js/searx_head AND searx/static/themes/simple/js/searx_src
			less          # searx/static/themes/simple/less
			...           # incomplete because a similar PR to https://github.com/searx/searx/pull/2346 must be done
			gruntfile.js
			package.json

[return42]

I would see:

• ...
• src/searx/static <-- built files

But a lot of stuff expect searx source code in the searx directory.

For the first step we should leave the static build products where they are and move only the source files of the build products to another location

So If the source folder for the static files is static/src or just static.

Hm, why not ./src/static? .. and build products will be generated at searx/static (as is)

BTW: what about the files in ./searx/data, I mean the sources that generate these files? Should we move searx_extra/update also to src/data? At the end we have something like:

.
├── doc
~
├── searx
│   ├── data
│   ├── static
│   │   ├── plugins
│   │   └── themes
~
└── src
    ├── data
    └── static

I would see:

src/..

If there comes the day we think it is a good idea, we can also move ./searx to ./src/searx

[dalf]

Hm, why not ./src/static ?

👍

There are files that are not compiled:

• searx/static/themes/oscar/fonts
• searx/static/themes/oscar/img
• searx/static/themes/oscar/css/images

I'm not sure what to do for these files.

[return42]

Leave them where they are .. in a second step, we can have a look what files can be generated ... E.g.

• searx/searx/static/themes/simple/img/favicon.png can be genrated from searx/static/themes/simple/img/searx_logo.svg and
• fonts can be updated from their origin
• ..

[return42]

@dafl are you implementing the move to src/ .. or should I give it a try?

[dalf]

I will do it.

[return42]

In #151 we have moved source files to the src directories below the themes/*/src, this was the first step.

The next step should be to move the themes/*/src to /src/*/static, see #151 (comment)

Moving the source files includes moving the gruntfile.js and package.json of the themes (in the simple themes additional .jshintignore, .jshintrc and.stylelintrc.json needs to be moved).

static/themes/__common__ needs a more elaborate treatment, I assume js/image_layout.js is only used by oscar theme.

@dalf should I give it a try / I assume that you know more about this topic but if you do not have time, I could give it a try (might be a good exercise for me).