Static sites for working groups

[starbelly]

Some working groups have very custom needs, embedded mostly comes to mind. In order to support such needs it may be optimal to faciliate static sites / content for particular working groups. I'm interested to hear from @peerst on this topic.

[benoitc]

what do you mean by "facilitate" ?

[starbelly]

@benoitc basically, support in some way or fashion, even if it's just dropping in static files into priv/static and some config to go with it.

[benoitc]

Why not re-usoing github pages for it? We could have the dns <WG>.erlef.org pointing to it. This would makes things maybe easier to manage. Thoughts?

[starbelly]

@benoitc That's a possibility. It's unclear how people want things to look. If it's github pages, there would be no continuity. I think that's important. Thoughts?

EDIT: Note that as pointed out by Fred, the security working group and it's guide is an excellent first candidate for this, unless embedded gets together content sooner.

The name of this issue is "Static sites" but that was just the initial as it wasn't clear do we want full blown sites? But after talking to the embedded group that's not what they want. Instead they just want to be able to link to static content from the website (i.e., it's part of erlef.org)

@peerst correct me if I'm wrong on that

[benoitc]

@benoitc That's a possibility. It's unclear how people want things to look. If it's github pages, there would be no continuity. I think that's important. Thoughts?

i am not sure what you mean there. Which continuity are we talking? If you want them to appear as a page, they can be proxied by the main site if needed also.

If we want dynamic website, using tools like ghost allows you to have a remote site that access to an api. That also feasible with a coming release of barrel...