Open vicos59 opened 2 years ago
vicos59
commented
2 years ago Maybe we should consider just adding the "features" list to the Github Wiki. Would be easier to maintain, and if we might one day migrate the wiki here from the .org site... Something to think about.
In any case need to grab the original code soon in case it disappears one day.
jonyo
commented
2 years ago @vicos59 that is one option, but does have its downsides:
You can't do much with layout in the wiki.
As soon as you get into the GitHub site I wonder if it would be info overload (all the menu options at the top and all that) for someone new to it. Especially since this is the feature list, it is probably one of the first things someone will look at.
I agree it would make it easier to maintain though.
vicos59
commented
2 years ago This seems to be "The Guy"
vicos59
commented
2 years ago Grabbed the pages using the script. Still a few support files missing. These files were originally generated by Joomla.
Removed the header, footer and menu. Restructuring the folder layout so everything is contained in one base folder.
Needs more cleanup and figure out how to integrate it into main site.
vicos59
commented
2 years ago @jonyo Are the 'Language Packs' going to be available? If not, I'll remove from the features page. It says to download them in the Client Area.
Matters not to me if they are or are not.
vicos59
commented
2 years ago @jonyo Just issued a pull request https://github.com/geodesicsolutions-community/website/pull/13 for what I have finished so far. Became more involved than expected. Will get back to this when I can.
jonyo
commented
2 years ago @jonyo Are the 'Language Packs' going to be available? If not, I'll remove from the features page. It says to download them in the Client Area.
Matters not to me if they are or are not.
No, don't have the old language packs, they were not something they kept in the git source code.
vicos59
commented
2 years ago I had forgotten how tedious it is to edit numerous HTML files vs using a CMS or script-generated pages.
I've been thinking about this and the entire website is high maintenance right now. As far as the software features pages defined in this Issue, I now think it would just be best put them right into the Wiki where they can be easily maintained. Frankly, I am thinking it might be best to just move the entire wiki to the top level and let it be the website. Dokuwiki seems to be active and maintained.
It would take me another 2-3 hours to finish cleaning up these HTML files. In the same time or less, I could probab'y just copy and paste it into the Wiki.
Just something to think about. I am putting this Issue on hold for now until we decide the best way forward.
jonyo
commented
2 years ago I now think it would just be best put them right into the Wiki where they can be easily maintained
The down side like I've mentioned before, is that it makes it more difficult to style it. Of course you've discovered the up sides, being easier to maintain and such.
Frankly, I am thinking it might be best to just move the entire wiki to the top level and let it be the website. Dokuwiki seems to be active and maintained.
For simple websites where the main part does not change often, I'd prefer static HTML files over a CMS, the CMS ends up being overkill. Since once it is made you don't touch it much.
But a feature list we probably would. So now I'm going to contradict myself 😆 - maybe for the feature list we use something.
One option is we could look into github pages, I've used that years ago. It might be a good option.
jonyo
commented
2 years ago Info on github pages: https://www.youtube.com/watch?v=2MsN8gpT6jY
jonyo
commented
2 years ago Hmm, so I kind of convinced myself, maybe github pages is the way to go for the entire site.
But wait, what about the wiki content... And the dynamic parts like dynamic upgrade instructions... When I have time I'll look into it more.
edit: For the dynamic upgrade instructions... That I could probably convert into a vue3 JS driven thing (so it shows/hides parts using front end JS instead of back end PHP).
edit2: Dokuwiki will be more tricky, my goal would be to have the same path so that the links in the software admin continue to work. I'll look around to see if there are any good options for getting the wiki pages into github pages.
edit3: There are wiki syntax to md syntax converters out there, it might be possible to maintain the paths that way, and github pages works with MD.
vicos59
commented
2 years ago https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site
You can customize the domain name of your GitHub Pages site.
If only we had a good domain name we could use for this....🤔
Grab the old features pages from the WayBackMachine, clean them up and post them on the .org site. Beats rewriting all that stuff from scratch.
https://web.archive.org/web/20200525190920/https://geodesicsolutions.com/add-ons/free-add-ons.html
https://web.archive.org/web/20200512051130/https://geodesicsolutions.com/geocore-software/geocore-admin.html
https://web.archive.org/web/20200512045706/https://geodesicsolutions.com/geocore-software/geocore-themes.html
https://web.archive.org/web/20200523100023/https://geodesicsolutions.com/classified-ad-software-and-auction-features/features-list.html
jonyo adds:
Sure, it wouldn't hurt, though we'd probably need to re-make the screenshots so it has the updated community edition name and all that.
If you do that, be sure to record if you use any specific tools (like any software that automatically makes mobile/desktop/tablet views or something) so we can easily re-create them later if needed.
For the icons, something I have seen recently is box icons - entirely free icon set. It may be a good resource for the website when we need icons, and in the software if someone wants to update the look.
That is a good resource as they provide SVG's which allow easily changing the color with CSS.