Skip to content

merge pidgin specific, and WordPress specific stylings into Vocabulary proper, prep for v2.0 release#363

Open
possumbilities wants to merge 21 commits into
vocab-2.0from
css-refactor
Open

merge pidgin specific, and WordPress specific stylings into Vocabulary proper, prep for v2.0 release#363
possumbilities wants to merge 21 commits into
vocab-2.0from
css-refactor

Conversation

@possumbilities
Copy link
Copy Markdown
Contributor

@possumbilities possumbilities commented May 18, 2026

Description

  • merges /pidgin directory into Vocabulary proper
  • merges pidgin.css into vocabulary.css fully (along with associate library-vars.css)
  • adds appropriate assets from /pidgin directory, and removes old assets from vocab 1.0
  • merges localized WordPress patch styles from style.css into vocabulary.css (mostly pidgin specific, but some broader)
  • merges pidgin specific scripts.js into main vocabulary.js

Technical details

Note: this moves this dev branch closer to merge into main, there should be at least one more PR that follows to wrap final testing/cleanup.

Checklist

  • I have read and understood the Developer Certificate of Origin (DCO), below, which covers the contents of this pull request (PR).
  • My pull request doesn't include code or content generated with AI (also see Avoiding generative AI development tools — Creative Commons Open Source).
  • My pull request has a descriptive title (not a vague title like Update index.md).
  • My pull request targets the default branch of the repository (main or master).
  • My commit messages follow best practices.
  • My code follows the established code style of the repository.
  • I added or updated unit tests and/or test scripts for the changes I made (if applicable).
  • I added or updated documentation (if applicable).
  • I tried running the project locally and verified that there are no
    visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 18, 2026

Deploy Preview for creativecommons-reno-prototype ready!

Name Link
🔨 Latest commit bb8eff7
🔍 Latest deploy log https://app.netlify.com/projects/creativecommons-reno-prototype/deploys/6a1f0356208e610008c38a52
😎 Deploy Preview https://deploy-preview-363--creativecommons-reno-prototype.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@possumbilities possumbilities changed the title setup baseline rough import of wp specific patches, to assimilate into Vocabulary merge pidgin specific, and WordPress specific stylings into Vocabulary proper. prep for v2.0 release May 21, 2026
@possumbilities possumbilities moved this from Triage to In progress in possumbilities May 21, 2026
@possumbilities possumbilities changed the title merge pidgin specific, and WordPress specific stylings into Vocabulary proper. prep for v2.0 release merge pidgin specific, and WordPress specific stylings into Vocabulary proper, prep for v2.0 release Jun 2, 2026
@possumbilities possumbilities marked this pull request as ready for review June 2, 2026 16:43
@possumbilities possumbilities requested review from a team as code owners June 2, 2026 16:43
@possumbilities possumbilities requested review from shailee-m and zackkrida and removed request for a team June 2, 2026 16:43
@possumbilities possumbilities moved this from In progress to In review in possumbilities Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

1 participant