I’m creating a web site for a user, which has a considerable amount of
static pages. The user, who has some knowledge in HTML and CSS and can
be tought how to use some simple erb-code snippets (for example, to
create a <%= link_to “…”,root_path %>), should be able to add, change
and remove the static pages by himself.
I will describe the approach I came up with, but would be glad to hear
better ways how to do it:
My approach would be to use high_voltage
(GitHub - thoughtbot/high_voltage: Easily include static pages in your Rails app.) for dealing with those
pages. I would reserve a directory app/views/user_pages for the HTML and
erb files, and app/views/images/user for holding the images needed for
his pages. The user will be told to upload by FTP only to those two
directories (or I will provide a specially tailored upload page for
this).
I will also create an admin page, where the user can select, which of
those static pages should show up in the main menu, and maybe also some
sequence number for each page, so that the user also can control the
sequence of the static page links in the main toolbar. This allows the
user to first test how the static pages look on the net, before he
“commits” them to the general public. This will be important, if he
really uses <%…%> tags, because he won’t have a Rails environment when
creating the pages.
What do you think about this design?
Ronald