Repository navigation
Conversation
Spanish law 34/2002, LSSI-CE article 10, requires a site run by an association to publish its name, its address, an email, its entry in the register it is recorded in, and its tax number. The legal notice page that shows them is written and waiting; two of the five facts are missing and no volunteer can supply them. They go in config.toml, under [params.association], rather than in the text of that page. Two reasons. The association can correct a fact without anyone editing a page of legal prose, which is the kind of edit that goes wrong. And the gap is visible: bin/check-content reports an empty one on every run, instead of the fact being absent from a paragraph nobody rereads. Filled already: the legal name, and the tax number G67254045. Empty, and only the Management Board can fill them: the registered address, and the entry in the Registre d'Associacions de la Generalitat de Catalunya. The check warns and does not fail. The site builds and serves without them, and an error would turn every pull request red for a reason no contributor could fix. The gate is the legal notice page, which cannot be published while they are empty: that page is the one place the law asks for these, and a page that leaves them out does not do the job it exists for. Checked both ways: with the two keys empty the run ends 0 errors and 13 warnings, and with them filled, 11.
DZPM
commented
Oct 8, 2026
Comment on lines
+51
to
+52
| address = "" | ||
| registry = "" |
The site identifies the association nowhere, which the LSSI-CE (article 10) requires of any organisation that runs a website. This page gives the name, the CIF, the contact mailbox, the terms of use and the applicable law. The registered address and the registry number are not in the repository. The page shows them as pending: it must not be published until they are filled in.
The site publishes 138 people pages with a name, a photograph, a biography and profile links, links Google Forms, embeds a Google Calendar, and sends members to PayPal, with no privacy policy. GDPR articles 13 and 14 require one. The page names the controller, lists each kind of data the site involves with its purpose and legal basis, names the third parties (Google, PayPal, GitHub), states that the site sets no cookies and runs no analytics, and gives one mailbox to exercise the rights of articles 15 to 22, including the removal of a people page. The registered address is not in the repository and shows as pending.
The footer is where a reader looks for them. The two pages are resolved with site.GetPage, so a moved or renamed page fails the build instead of leaving a dead link.
The partial was included only when cookie_consent_info_url was set, and the site config never set it, so no page rendered the banner. The site sets no cookie of its own, which the privacy policy now states. A banner that asks consent for a cookie that does not exist would only mislead, so the partial and the two vendored Osano assets go.
The banner was removed in the previous commit.
The legal notice held the five facts LSSI-CE article 10 asks for as text, two of them a paragraph saying the association still had to supply them. They come from [params.association] now, through a shortcode. The association can correct a fact without a volunteer editing a page of legal prose, which is the kind of edit that goes wrong. And an empty value prints a line that says so rather than a missing bullet: a missing bullet reads as a page that never claimed to carry the fact, where a line that says it is missing is the page admitting it does not yet do its job. Both states are checked in the build. With the two keys empty the page reads "Registered address: not published yet. The Management Board has to supply it." With them filled it reads the value.
DZPM
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The legal notice and the privacy policy that pybcn.org does not have, and the two facts only the Management Board can supply.
Why the site needs this
Spanish law 34/2002, LSSI-CE article 10, requires a site run by an association to publish its name, its address, an email, its entry in the register it is recorded in, and its tax number. The site publishes none of them. It also has no privacy policy, while it embeds Google Forms and a Google Calendar, serves from GitHub Pages, and links to Meetup and YouTube.
What this adds
Two pages. A legal notice at
/pybcn_association/legal-notice/and a privacy policy at/pybcn_association/privacy-policy/, both linked from the footer of every page.A
[params.association]table inconfig.toml, which the legal notice reads:The facts go in the configuration rather than in the text of the page, for two reasons. The association can correct one of them without anyone editing a page of legal prose, which is the kind of edit that goes wrong. And the gap stays visible instead of being quietly absent from a paragraph nobody rereads: an empty value prints a line that says so, and
bin/check-contentreports it on every run.The check warns and does not fail. The site builds and serves without them, and an error would turn every pull request red for a reason no contributor could fix.
The dead cookie banner goes.
cookieconsent.min.jsand its CSS were loaded on every page for a banner that no longer appeared. The site sets no cookies, which is what the privacy policy now says.What the board needs to provide
@mesejo, as Secretary, these two:
Either answer here and I will commit them, or push the two lines onto this branch. Both are one edit to
config.toml, nothing else.Until they arrive the legal notice reads, in the page itself:
That is why this does not merge yet. A legal notice that leaves out the one section the law asks for does not do the job it exists for.
Worth the board's eye, not only the data
The pages are written in plain English by a volunteer, not by a lawyer. They describe what the site actually does: no analytics, no server of our own, no cookies, a static site on GitHub Pages, and a handful of third-party embeds named one by one. If anything in them is wrong about how the association works, this is the moment to say so.