What should a forked Spectre project look like?

[davestewart]

I thought this would be a good place to continue the discussion from the original PR.

In that thread I suggested creating an org and fork to ensure Spectre CSS is available going forwards.

Questions around the feasibility of that include:

• what would a forked repo / org look like?
• what needs to be done now?
• what would be good to do soon?
• what would be nice to do in future?

I'm looping in recent PR authors and contributors:

@ma4nn @Valexr @codebling @peterhil @blokhin @jviotti @salamwaddah @janbakker2525 @NazimHAli @janbakker2525 @akirk @McLaynV @mlbiche @matronator @NicoHood @wyndon @st-wong @endorama @marcosstefani @Vectrex @nisarhassan12

Here are my thoughts...

Need to do now:

• rename the org (see Change of Org Name #3)
• fork the original code
• publish docs
• review outstanding PRS (see Review PRs #5)
• publish a new package (in the meantime, can npm i spectre-org/spectre-css)

Good to do soon:

• remove support for LESS
• proper markdown docs
• a @spectre-org NPM namespace

Nice to do in future:

• introduce theming
• wrappers for Vue, React, etc

Who knows if this will go somewhere, but drop your thoughts and suggestions below.

[ma4nn]

@davestewart thanks for your effort, good idea with the new organization 👍

A couple of thoughts here:

• I don't think the org name "picturepan-too" is very appropriate (because "picturepan2" is the original author), imho it should better contain the framework name (e.g. spectre-org) or kind of a successor framework name (e.g. spectre2, spectre-fork, skyfall-css, ..)
• We should define what is the purpose of this fork, i.e. which PRs to accept, what is the direction for new developments (e.g. I personally would keep it simple and extremely lightweight as it currently is, i.e. no theming, wrappers, etc. within the original repo), etc.
• Also we should discuss how/who will maintain it (admins, owners, etc.) so there won't be a situation like in the original repo/org

[NazimHAli]

+1 about library name! Before making any changes, it would be good to set up basic things like automated linting, testing, metrics, publishing, deploying on every commit for PRs and releases.

Keeping it lightweight is ideal and we can keep those separate from the core library.

[davestewart]

OK, renames done; we now have:

spectre-org/spectre-css

[ma4nn]

Maintainers
Totally agreed. Happy to take suggestions.

Hi @davestewart back from vacation now🍹I saw you committed and merged already several changes, nice 👍

Can you please elaborate a bit more on what is your plan regarding maintainers, review processes, priorization, releases, etc. I'm more than ready to invest time in this project and make spectre-css alive again, but the common goal should be clear. Also regarding Admin rights on the repositories/org, etc.

In addition I very much support the suggestion from @NazimHAli that we should add linting, testing, etc. in the first place before applying any changes.

Happy to discuss this also directly, e.g. via Skype, Teams, Discord, whatever 😉 Just let me know.

[davestewart]

Hey! Been a busy few weeks for myself, how are you fixed this week?

DM me on Twitter and we can coordinate @dave_stewart

[ma4nn]

@davestewart seems like I cannot send you DMs without being a Premium Member🙈 can you follow my account @vianetz then it should be possible to exchange DMs

[codebling]

Thanks for tagging me! Don't think I have an interest in contributing/maintaining a lib that I'm not actively using at the moment, but thanks for making me part of the conversation!

[st-wong]

Not sure if I have the time to contribute, but definitely looking forward to seeing how things go! All the best!

[davestewart]

If anyone is curious, I've migrated the existing html docs to Markdown, and have set them up in VitePress:

It's live here:

• https://spectre-org.github.io/spectre-docs/

There are a few bits to finish off:

• Migration fixes spectre-docs#4
• Add final polish spectre-docs#7

Create issues if you need to here:

• https://github.com/spectre-org/spectre-docs/issues

[endorama]

@davestewart thanks for the ping! I've not been working with front-end things for a while now, so I'm a bit out of touch.

I like the direction, I cannot commit to a maintenance schedule but I'll look around for opportunity to help (i.e. reviewing outstanding PRs). I agree with the current work in progress and suggestions in the thread created by @ma4nn.

[davestewart]

Cool, thanks for the reply!

[peterhil]

Great! I use Spectre.css actively at work and on hobby projects. I hope I can help somehow. A least I could review some pull requests.

[davestewart]

Just to let everyone know, Spectre CSS is now on NPM!

• https://www.npmjs.com/package/@spectre-org/spectre-css

We have also updated the docs with simpler install instructions, search, and better information around customisation.

• https://spectre-org.github.io/spectre-docs/

In the coming weeks and months we have modest plans to make Spectre CSS even better.

Issues:

• https://github.com/spectre-org/spectre-css/issues
• https://github.com/spectre-org/spectre-docs/issues

Projects:

• https://github.com/orgs/spectre-org/projects

[akirk]

Looks fantastic!

[davestewart]

Thanks! I think so too. Really excited to breathe new life back into such a great project