On Sat, Apr 02, 2016 at 11:58:41AM -0600, Jaimos Skriletz wrote: > On Fri, Apr 1, 2016 at 5:43 PM, Thomas Adam <tho...@fvwm.org> wrote: > > > On Fri, Apr 01, 2016 at 02:47:24PM -0600, Jaimos Skriletz wrote: > > > ββ > > > > Thanks! It looks really good. We can remove the Changelog section; people > > can look at the release descriptions and/or Git history from now on. > > Maintaining this is a doubling of effort for absolutely no reason. > > > > > βThe ChangeLog page is just links to the files on GitHub so there is no > maintenance on the page. Could be removed, I just thought it would be nice > to have links easily found on fvwm.org for them. > β
It can be removed. > > In terms of the FAQ, have you (for now) just copied that from > > $FVWM.GIT/docs/ > > ? If so, I can remove that file from the FVWM repo and make the one in > > fvwmorg.gh.io the authoritative version (as it should be). Same goes for > > removing other files from the FVWM repo too, but that's a different > > concern. > > > > > No, the FAQ is a html dump (save as) from the old fvwm.org page as it was a > copy of that file with linked anchors in it. The FAQ needs to be converted > into a markdown file (complete with anchored links). Then I will create a > simple wrapper to wrap the markdown file into the webpage. I would keep the > FAQ around in $FVWM.GIT/docs/ until then. > > Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md, > DEVELOPERS.md, etc should be located and maintained on the webpage or > in $FVWM.GIT source. I think either can work with git.io so it is probably > a matter of preference. But agreed, these markdown files should all be > collected and maintained in a single place. The point here is to put the files which relate to the website into the repository which handles the web site, and for other files to remain outside of it. For the website, this includes: authors, faq. Developing happens in FVWM and although you could link to that file in the FVWM.git repo, I wouldn't bother. > - A simple/minimal "default" config. This has to then be maintained by us. Maybe, but no thanks. We've done this in the past, and no one has maintained it. There's such a plethora out there on the Internet, just link to those. > - Examples of various config snippets for things such as Vector > Buttons, Window Decors, Menus, Modules, etc. (This was kinda attempted on > the current fvwm.org page). This can move to the wiki. > I think the actual question is should fvwm.org provide any resources for > configurations like above, or should it only link to other sites? This is > also not something I was planning on including in the initial transition of > moving the site to git.io, but was something I was thinking of developing > and adding if there was interest to have a collection of config snippets on > fvwm.org. If not I will look into updating the wiki (though I am liking > jekyll over ikiwiki for building static pages). Redirect to other sites for that sort of thing. As for moving the wiki to somthing on GH, sure. But that's a different conversation and has no bearing on the transition of the web site. -- Thomas Adam
