Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

html generation #411

Open
skittishtrigger opened this issue Jul 2, 2015 · 3 comments
Open

html generation #411

skittishtrigger opened this issue Jul 2, 2015 · 3 comments

Comments

@skittishtrigger
Copy link

Admittedly I stole this idea from zleppers modpack helper but it seemed like such a good idea with simple implementation that I thought it might do some good here too.

The base idea is have solder generate a html or php page that displays a list of modpacks, mods broken down in such a way that it is clear what mods are used in each modpack, and what mods in total that are available. I do not know if anyone else thinks this would be helpful but I think it would certainly save a lot of time and trouble for people who try to update several pages that contain this info.

@GenPage
Copy link
Contributor

GenPage commented Jul 3, 2015

This is a pretty big feature request in my opinion, not from a back-end coding standpoint but front-end. How its designed, presented, etc. There is a lot of information to be presented in this context. Its not something thats high on my to-do list, but I am open to further input/design ideas about this. This could be something that replaces the current dashboard

@skittishtrigger
Copy link
Author

I love the simplicity of the dashboard as it is tbh. It allows for further expansion of the platform without cluttering things up and making "too complicated" I was thinking a simple sectioned layout myself. One page that lists all the modpacks, a page that lists all mods for each modpack, and a page that lists all mods. The reason I say separate pages in an html or php format is for ease of use redistributing the information as need. Like on my forum page descripting the modpack thismodpack1 could be linked via code to that file itself and automagically update update as the mods change along with the mod info (author, page links, etc) and the modpacks page could go elsewhere. Also maybe having the direct links to the modpacks on a public facing venue that each modpack author could use would possibly ease up some of the issues with permissions in regards to individual mod developers. The generated pages imo should be accessible from our solder installs directly via the webserver of choice used in the install and a simple link added to the current dashboard to navigate there locally.
As far as the actual design of it I would do something basic with a config file that would allow us to set certain aspect/control the overall presentation with a watermark of sorts on the page somewhere identifying the solder and technic platforms.

@rfox90
Copy link

rfox90 commented Jul 4, 2015

A JSON output of the mods in a pack would be more appropriate.

You can then use your own templating tools to iterate over the JSON and make pretty html.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants