Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
leenagupte pushed 2 commits to main alphagov/frontend
leenagupte opened a pull request on alphagov/frontend
Use a blocks container to keep blocks to one column
⚠️ This repo is Continuously Deployed: make sure you [follow the guidance](https://docs.publishing.service.gov.uk/manual/development-pipeline.html#merge-your-own-pull-request) ⚠️ ## What ...
leenagupte created a branch on alphagov/frontend
remove-image-block - Serves the homepage, transactions and some index pages on GOV.UK
KludgeKML pushed 5 commits to content-items-for-all alphagov/frontend
- Add basic heading block When govspeak only contains a YouTube video, it removes the paragraph tag, and therefore the... 28bb313
- Merge pull request #4297 from alphagov/heading-tweaks Add basic heading block 432f93b
- Update example for placeholder in readme - Placeholder route is only served on assets.publishing.service.gov.uk 019f348
- Merge pull request #4300 from alphagov/update-placeholder-example-in-readme Update example for placeholder in readme 4279a23
- Add hardcoded content items for - These are the only controllers that 1) don't extend ContentItemController, and 2) ... 299b75d
KludgeKML closed a pull request on alphagov/frontend
Update example for placeholder in readme
- Placeholder route is only served on assets.publishing.service.gov.uk
KludgeKML opened a pull request on alphagov/frontend
Update example for placeholder in readme
- Placeholder route is only served on assets.publishing.service.gov.uk
KludgeKML created a branch on alphagov/frontend
update-placeholder-example-in-readme - Serves the homepage, transactions and some index pages on GOV.UK
KludgeKML created a branch on alphagov/frontend
content-items-for-all - Serves the homepage, transactions and some index pages on GOV.UK
AshGDS pushed 2 commits to main alphagov/frontend
AshGDS closed a pull request on alphagov/frontend
Add basic heading block
⚠️ This repo is Continuously Deployed: make sure you [follow the guidance](https://docs.publishing.service.gov.uk/manual/development-pipeline.html#merge-your-own-pull-request) ⚠️ ## What / Why ...
matthillco created a review comment on a pull request on alphagov/frontend
Cool, OK thanks. I'll hold off applying this change as we might not need any of it if the margins will be handled automatically.
matthillco created a review comment on a pull request on alphagov/frontend
The exception would be `govspeak` content/headings, which probably would not want the same amount of consistent bottom margin as typically these are related/connect to the following component. So w...
andysellick created a review comment on a pull request on alphagov/frontend
Sorry, I meant to refer to `capture` there. It's something like... ```Rails <% markup = capture do %> (the markup you're creating) <% end %> <% if classes.present? %> <div class="<%= ...
matthillco created a review comment on a pull request on alphagov/frontend
Also, if we use a responsive margin in the selector above, then we can tweak the spacing for mobile/tablet/desktop while still maintaining consistency.
andysellick created a review comment on a pull request on alphagov/frontend
Allowing content authors control over spacing could introduce inconsistencies as well as allowing the possibility that they could overlook problems, particularly if margins are different at differe...
andysellick created a review comment on a pull request on alphagov/frontend
In that case let's remove it - we usually try to have a margin down approach.
leenagupte created a branch on alphagov/frontend
mock-cut-down-landing-page-homepage - Serves the homepage, transactions and some index pages on GOV.UK
matthillco created a review comment on a pull request on alphagov/frontend
OK. Would the div still need a class name to identify it, or would it just end up as unnamed in the markup if there are no margin classes on it? It seems a bit wrong to have unnamed divs in the mar...
richardTowers created a review comment on a pull request on alphagov/frontend
To a degree, this gets us into the heart of the problem with this whole "blocks" approach. If the user of the publishing system is allowed to pick from a list of arbitrary blocks, and stack and ...
