diff options
Diffstat (limited to 'tracker/Merge_wiki_website_and_website.mdwn')
| -rw-r--r-- | tracker/Merge_wiki_website_and_website.mdwn | 45 |
1 files changed, 44 insertions, 1 deletions
diff --git a/tracker/Merge_wiki_website_and_website.mdwn b/tracker/Merge_wiki_website_and_website.mdwn index dc43a47..6ea8553 100644 --- a/tracker/Merge_wiki_website_and_website.mdwn +++ b/tracker/Merge_wiki_website_and_website.mdwn @@ -5,6 +5,9 @@ and merge the content of the org-mode based into the wiki. [[gustav]] is working on the branch *fripost-wiki#ge-move-website*. +Requirements +============ + Regarding redesign, the following are requirements: * Visitors of [https://fripost.org] should be brought to the "Hem" page @@ -16,6 +19,9 @@ Regarding redesign, the following are requirements: should be editable but still displayed as if it was part of the website. +Checklist +========= + Regarding merging, the following is the checklist: * In *from_wiki*, the following pages should be attended and possibly @@ -55,7 +61,44 @@ Regarding merging, the following is the checklist: * Check whether the content in *material* is available from the *propaganda* git repository. If it isn't, do something about it * Check where *logo2011.eps* is available elsewhere. - + +Doubts +====== + +There are still some doubts about how to proceed: + +**1.** How shall the becoming *fripost.org* be prepared for +publications from other sources, like the *fripost-meetings* Git +repository? Currently publication happens through + + rsync -ruvp --chmod=Dugo+rx,Fugo+r $(send-files) fripost@fripost.org:fripost.org/minutes/ + +and access through + + https://fripost.org/minutes/<whatever-asked-for> + +**2.** I assume press images and similar can be published according to +the same structure: + + https://fripost.org/images/<whatever-asked-for> + +**3.** Regarding how to enforce the soft separation between the wiki +and the website content, I don't know how to achieve that. + +I tried the following idea that did not work. The wiki content is left +untouched. All website content (apart from *hem.mdwn*) is moved into a +directory, *website*, and *hem.mdwn* is named *website.mdwn*. Then the +website is reached through *https://fripost.org* simply by making the +web server point those request to +*<path-to-fripost-wiki>/website*. The *website.mdwn* will be +*<path-to-fripost-wiki>/website/index.html* and default target. + +The problem was that links to shared static content (style sheets and +similar) with relative paths did not work. + +Other ideas to track +==================== + Consider to get back to how the certificate pages are accessed. It would be more natural to access a certificate page from a side note on the "Hem" page, the way it was done in the org-mode based website. |