How many degree listings does your institution’s website have? How robust is that information? How consistent and on-brand is it? The amount of information related to academic programs is vast and varied. Tuition, scholarships, plans of study, facilities, profiles, media and more. Having clear and consistent academic information would be a differentiator for many schools. A single source-of-truth for academic content might be the holy grail.
This presentation shares how West Virginia University has started to tackle this problem. Their Academic Programs API combines Contentful, a headless CMS, with Amazon Web Services. This has led to a flexible, easy-to-update system for authors, developers and designers.
In this session, you’ll learn how to:
* Work with content owners to show them the importance of centralized content and how to source it
* Define content models and relationships in Contentful
* Use AWS’s Lambda, DynamoDB and API Gateway services to build an API
* Expand your efforts beyond academic information
* Take control of your institution’s content
Beyond DevOps: How Netflix Bridges the Gap?C4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1mv6Kpr.
Josh Evans uses the Netflix Operations Engineering as a case study to explore the challenges faced by centralized engineering teams and approaches to addressing those challenges. Filmed at qconsf.com.
Josh Evans is Director of Operations Engineering at Netflix, with experience in e-commerce, playback control services, infrastructure, tools, testing, and operations.
Presentation titled Librarians' adventure into LODLAM by Silvia Southwick & Cory Lampert during the SemTech LODLAM Training, San Jose, CA, August 19, 2014
Why do they call it Linked Data when they want to say...?Oscar Corcho
The four Linked Data publishing principles established in 2006 seem to be quite clear and well understood by people inside and outside the core Linked Data and Semantic Web community. However, not only when discussing with outsiders about the goodness of Linked Data but also when reviewing papers for the COLD workshop series, I find myself, in many occasions, going back again to the principles in order to see whether some approach for Web data publication and consumption is actually Linked Data or not. In this talk we will review some of the current approaches that we have for publishing data on the Web, and we will reflect on why it is sometimes so difficult to get into an agreement on what we understand by Linked Data. Furthermore, we will take the opportunity to describe yet another approach that we have been working on recently at the Center for Open Middleware, a joint technology center between Banco Santander and Universidad Politécnica de Madrid, in order to facilitate Linked Data consumption.
Beyond DevOps: How Netflix Bridges the Gap?C4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1mv6Kpr.
Josh Evans uses the Netflix Operations Engineering as a case study to explore the challenges faced by centralized engineering teams and approaches to addressing those challenges. Filmed at qconsf.com.
Josh Evans is Director of Operations Engineering at Netflix, with experience in e-commerce, playback control services, infrastructure, tools, testing, and operations.
Presentation titled Librarians' adventure into LODLAM by Silvia Southwick & Cory Lampert during the SemTech LODLAM Training, San Jose, CA, August 19, 2014
Why do they call it Linked Data when they want to say...?Oscar Corcho
The four Linked Data publishing principles established in 2006 seem to be quite clear and well understood by people inside and outside the core Linked Data and Semantic Web community. However, not only when discussing with outsiders about the goodness of Linked Data but also when reviewing papers for the COLD workshop series, I find myself, in many occasions, going back again to the principles in order to see whether some approach for Web data publication and consumption is actually Linked Data or not. In this talk we will review some of the current approaches that we have for publishing data on the Web, and we will reflect on why it is sometimes so difficult to get into an agreement on what we understand by Linked Data. Furthermore, we will take the opportunity to describe yet another approach that we have been working on recently at the Center for Open Middleware, a joint technology center between Banco Santander and Universidad Politécnica de Madrid, in order to facilitate Linked Data consumption.
Emerging technologies in academic libraries. A department by department overview. Data visualization, online reference, nextGen library platforms, open source software, digital asset and archive management systems, digital humanities, scientific and creative software, new physical spaces for libraries.
Lessons learned on the Azure API Stewardship Journey.pptxapidays
apidays LIVE Singapore 2022: Digitising at scale with APIs
April 20 & 21, 2022
Lessons learned on the Azure API Stewardship Journey
Adrian Hall, Principal Product Manager at Microsoft
------------
Check out our conferences at https://www.apidays.global/
Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8
Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io
Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/
Deep dive into the API industry with our reports:
https://www.apidays.global/industry-reports/
Subscribe to our global newsletter:
https://apidays.typeform.com/to/i1MPEW
When you treat docs like code, you multiply everyone’s efforts and streamline processes through collaboration, automation, and innovation. The benefits are real, but these efforts are complex. The ways you can leverage developer process and tools vary widely. Let’s unpack the absolute best situation for using a docs as code model.
Then, we can walk through multiple considerations that may point you in one direction or another. We can talk about version control, publishing, REST API considerations, source formats, automation, quality controls and testing, and lessons learned. Let’s study best practices that are outcome-dependent and situational, creating strategic efforts.
apidays LIVE Paris 2021 - Lessons from the API Stewardship Journey in Azure b...apidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Lessons from the API Stewardship Journey in Azure
Ryan Sweet, Principal Architect at Microsoft
Enterprise Serverless Adoption. An Experience ReportSheenBrisals
The adoption of Serverless is growing in the industry. However, its adoption in larger enterprises is somewhat slow compared to start-ups and individual developers. This talk tells an enterprise adoption success story and shares insights into the secrets behind its success!
[DevDay2018] High quality mindset in software development - By: Phat Vu, Scru...DevDay.org
In this topic, Phat will show what high quality mindset is, how important it is. He will try to bring as many examples as possible – not theory, but lesson-learned ones. His expectation is that he could encourage developers to have or refresh a mindset about doing high quality software.
BOUND TECH SOLUTIONS Offering you the best Training for your career development. Our experts offering you the best training. You can attain the best ever training with our industry professional.If you want to shine your career with PEGA Training join our concern.
Microservices and the Art of Taming the Dependency Hell MonsterC4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1OkQDCc.
Michael Bryzek presents lessons learned building an expansive microservice architecture at Gilt - an organization with 1500 git repositories and over 400 individual applications powering its apps and web sites. He emphasizes the importance of REST APIs and great client libraries to talk to them as a critical step to adoption. Filmed at qconnewyork.com.
Michael Bryzek is the CTO and co-founder of Gilt Groupe, an innovative online shopping destination offering its members special access to the most inspiring merchandise, culinary offerings, and experiences every day, many at insider prices. Gilt continually searches the world for the most coveted brands and products, including fashion, home decor, hotels and travel experiences on every continent.
15015 SRV318 Serverless Breakout Session Research at PNNL: Powered by AWS Pacific Northwest National Laboratory's rich data sciences capability has produced novel solutions in numerous research areas including image analysis, statistical modeling, and social media (and many more!). See how PNNL software engineers utilize AWS to enable better collaboration between researchers and engineers, and to power the data processing systems required to facilitate this work, with a focus on Lambda, EC2, S3, Apache Nifi and other technologies. Several approaches will be covered including lessons learned. AWS re:Invent 2017, Amazon, Giardinelli, Serverless, SRV318, EC2 11/28/2017 1:00:00 PM Tue Breakout Session
Research at PNNL: Powered by AWS - SRV318 - re:Invent 2017Amazon Web Services
Pacific Northwest National Laboratory's rich data sciences capability has produced novel solutions in numerous research areas including image analysis, statistical modeling, and social media (and many more!). See how PNNL software engineers utilize AWS to enable better collaboration between researchers and engineers, and to power the data processing systems required to facilitate this work, with a focus on Lambda, EC2, S3, Apache Nifi and other technologies. Several approaches will be covered including lessons learned.
AWS User Group - Survey Results and Building APIs on AWSSebastian Krueger
APIs are the hot topic everyone talks about. Today, even CEO's appear to know what an API is. SOA is dead. Long live the API. This talk will give an overview of designing and implementing REST APIs in the context of AWS. We will cover the basics, but get pretty technical for most of the presentation. Followed by a deep dive of building a Survey API using API Gateway, Lambda, and DynamoDB (Surprised? ;-).
Two architectural styles will be showcased.
1. Server-less design - API Gateway and Lambda
2. Server-based design - Elastic Beanstalk
Live demo will be given using API Gateway and Lambda to design a basic API from scratch in only 15 minutes.
Taking Your HTML Email Communications from "Ew" to "Wow"Dave Olsen
HTML emails can suck. From the 1990s era code to uninspiring templates to fulfillment and statistics in an alien CRM HTML emails are something that many choose to ignore. Or, at best, develop and deliver outside of a CRM.
In the summer of 2018 University Relations at West Virginia University implemented a new way of delivering HTML emails in support of Enrollment Management. We found we could be more creative and focused in our messaging than we ever expected. Early numbers show we may have influenced our class with our new strategy.
In this session, you’ll follow along with a case study that will cover how we:
• Re-thought our email communication plans from the ground-up
• Helped designers and developers collaborate with Enrollment Management using Litmus
• Built a tool on top of MJML to help speed up our development time, as well as segment copy and imagery, for our emails
• Track the effectiveness of our email communications using a dashboard built in Data Studio
And it’s all CRM agnostic.
The rise of digital platforms has given marketers the ability to track everything that our customers are doing. Tracking “all the things” presents problems though. What metrics show that a platform is effective? How do we collect the data in the first-place? In this workshop we’ll cover how to combine three Google products into the ultimate data gathering and reporting workflow. One that will save you time while giving you the answers you need and moves beyond “page views.”
More Related Content
Similar to Building an Academic Program Database and API with Contentful and Amazon Web Services
Emerging technologies in academic libraries. A department by department overview. Data visualization, online reference, nextGen library platforms, open source software, digital asset and archive management systems, digital humanities, scientific and creative software, new physical spaces for libraries.
Lessons learned on the Azure API Stewardship Journey.pptxapidays
apidays LIVE Singapore 2022: Digitising at scale with APIs
April 20 & 21, 2022
Lessons learned on the Azure API Stewardship Journey
Adrian Hall, Principal Product Manager at Microsoft
------------
Check out our conferences at https://www.apidays.global/
Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8
Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io
Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/
Deep dive into the API industry with our reports:
https://www.apidays.global/industry-reports/
Subscribe to our global newsletter:
https://apidays.typeform.com/to/i1MPEW
When you treat docs like code, you multiply everyone’s efforts and streamline processes through collaboration, automation, and innovation. The benefits are real, but these efforts are complex. The ways you can leverage developer process and tools vary widely. Let’s unpack the absolute best situation for using a docs as code model.
Then, we can walk through multiple considerations that may point you in one direction or another. We can talk about version control, publishing, REST API considerations, source formats, automation, quality controls and testing, and lessons learned. Let’s study best practices that are outcome-dependent and situational, creating strategic efforts.
apidays LIVE Paris 2021 - Lessons from the API Stewardship Journey in Azure b...apidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Lessons from the API Stewardship Journey in Azure
Ryan Sweet, Principal Architect at Microsoft
Enterprise Serverless Adoption. An Experience ReportSheenBrisals
The adoption of Serverless is growing in the industry. However, its adoption in larger enterprises is somewhat slow compared to start-ups and individual developers. This talk tells an enterprise adoption success story and shares insights into the secrets behind its success!
[DevDay2018] High quality mindset in software development - By: Phat Vu, Scru...DevDay.org
In this topic, Phat will show what high quality mindset is, how important it is. He will try to bring as many examples as possible – not theory, but lesson-learned ones. His expectation is that he could encourage developers to have or refresh a mindset about doing high quality software.
BOUND TECH SOLUTIONS Offering you the best Training for your career development. Our experts offering you the best training. You can attain the best ever training with our industry professional.If you want to shine your career with PEGA Training join our concern.
Microservices and the Art of Taming the Dependency Hell MonsterC4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1OkQDCc.
Michael Bryzek presents lessons learned building an expansive microservice architecture at Gilt - an organization with 1500 git repositories and over 400 individual applications powering its apps and web sites. He emphasizes the importance of REST APIs and great client libraries to talk to them as a critical step to adoption. Filmed at qconnewyork.com.
Michael Bryzek is the CTO and co-founder of Gilt Groupe, an innovative online shopping destination offering its members special access to the most inspiring merchandise, culinary offerings, and experiences every day, many at insider prices. Gilt continually searches the world for the most coveted brands and products, including fashion, home decor, hotels and travel experiences on every continent.
15015 SRV318 Serverless Breakout Session Research at PNNL: Powered by AWS Pacific Northwest National Laboratory's rich data sciences capability has produced novel solutions in numerous research areas including image analysis, statistical modeling, and social media (and many more!). See how PNNL software engineers utilize AWS to enable better collaboration between researchers and engineers, and to power the data processing systems required to facilitate this work, with a focus on Lambda, EC2, S3, Apache Nifi and other technologies. Several approaches will be covered including lessons learned. AWS re:Invent 2017, Amazon, Giardinelli, Serverless, SRV318, EC2 11/28/2017 1:00:00 PM Tue Breakout Session
Research at PNNL: Powered by AWS - SRV318 - re:Invent 2017Amazon Web Services
Pacific Northwest National Laboratory's rich data sciences capability has produced novel solutions in numerous research areas including image analysis, statistical modeling, and social media (and many more!). See how PNNL software engineers utilize AWS to enable better collaboration between researchers and engineers, and to power the data processing systems required to facilitate this work, with a focus on Lambda, EC2, S3, Apache Nifi and other technologies. Several approaches will be covered including lessons learned.
AWS User Group - Survey Results and Building APIs on AWSSebastian Krueger
APIs are the hot topic everyone talks about. Today, even CEO's appear to know what an API is. SOA is dead. Long live the API. This talk will give an overview of designing and implementing REST APIs in the context of AWS. We will cover the basics, but get pretty technical for most of the presentation. Followed by a deep dive of building a Survey API using API Gateway, Lambda, and DynamoDB (Surprised? ;-).
Two architectural styles will be showcased.
1. Server-less design - API Gateway and Lambda
2. Server-based design - Elastic Beanstalk
Live demo will be given using API Gateway and Lambda to design a basic API from scratch in only 15 minutes.
Similar to Building an Academic Program Database and API with Contentful and Amazon Web Services (20)
Taking Your HTML Email Communications from "Ew" to "Wow"Dave Olsen
HTML emails can suck. From the 1990s era code to uninspiring templates to fulfillment and statistics in an alien CRM HTML emails are something that many choose to ignore. Or, at best, develop and deliver outside of a CRM.
In the summer of 2018 University Relations at West Virginia University implemented a new way of delivering HTML emails in support of Enrollment Management. We found we could be more creative and focused in our messaging than we ever expected. Early numbers show we may have influenced our class with our new strategy.
In this session, you’ll follow along with a case study that will cover how we:
• Re-thought our email communication plans from the ground-up
• Helped designers and developers collaborate with Enrollment Management using Litmus
• Built a tool on top of MJML to help speed up our development time, as well as segment copy and imagery, for our emails
• Track the effectiveness of our email communications using a dashboard built in Data Studio
And it’s all CRM agnostic.
The rise of digital platforms has given marketers the ability to track everything that our customers are doing. Tracking “all the things” presents problems though. What metrics show that a platform is effective? How do we collect the data in the first-place? In this workshop we’ll cover how to combine three Google products into the ultimate data gathering and reporting workflow. One that will save you time while giving you the answers you need and moves beyond “page views.”
Reimagining Your Website: What are prospective students looking for and how a...Dave Olsen
Review insights from the 2016 Ruffalo Noel Levitz E-expectations Report and discover tips and tools for implementing these strategies across your websites.
Progressive Mobile Strategy Redux: The Future Friendly EnterpriseDave Olsen
A common refrain from both management and clients alike today (still!) is, "We need an app...." Unfortunately, over the long-term, mobile solutions will need to be more diversified than a single app or even a single platform. Not only will your customers be affected by the rapid adoption of smartphones but also your workforce and business processes. From optimizing web content to developing unique experiences mobile will touch and transform your entire enterprise. Together we’ll look ahead to see what kind of changes an enterprise needs to make to be future friendly.
This talk was presented at the Huawei Mobile Information Revolution Think Tank on November 19, 2015.
Case Study: Rebuilding an Admissions Web PresenceDave Olsen
From print-heavy communication plans to ad hoc social media efforts to an ever expanding number of web sites we are very good at building silos of content. In this session we'll discuss the data, tools, and strategy that West Virginia University used to pare down and better integrate their Admissions-related communication efforts.
Ensuring the consistent adoption of brand elements across various channels can be a problem for many large organizations. As West Virginia University rolls out a new brand campaign our central Digital Services unit is sharing tools with our web development community to help them make this shift. In this talk you will learn how we’re using patterns to:
* modernize and standardize toolsets
* encourage broad and fast adoption of the new brand elements
* make it easier to incorporate future changes to brand elements
This process has not been without its challenges so expect many pitfalls and missteps to be shared.
The Death of Lorem Ipsum and Pixel-Perfect Content (MinneWebCon version)Dave Olsen
A designer has been asked to mock up an example student profile page in Photoshop. It’s beautiful. The student’s name fits perfectly under the profile image. Their bio is split into two perfectly aligned columns. The design just feels… right. Approvals are given and the production of a website with many different profiles is started. As more profiles are added the design no longer seems to work. It’s starting to seem like the website itself will no longer work. The cold, hard reality of varied and inconsistent web content has hit the project hard. Do we make large design changes or just live with it?
To head off this question we should utilize real content as we develop mock-ups. But it shouldn’t just be one set of real content. Delivering the best possible and most robust websites requires us to design using the best-case, worst-case, and every-case-in-between content. By combining the skills of content specialists, designers, and even developers designs will be that much stronger.
Case Study: Automating Outage Monitoring & CommunicationDave Olsen
This is a review of how West Virginia University's Digital Services unit monitors and communicates system outages. In the past we have had little coverage for our systems. Notices amounted to emails which didn't work well at 2am. We've now been able to combine a number of solutions (New Relic, Pingdom, Slack, PagerDuty, StatusPage.io) into one cohesive monitoring and communication workflow.
The Death of Lorem Ipsum & Pixel Perfect ContentDave Olsen
A designer has been asked to mock up a student profile page in Photoshop. It’s beautiful. The student’s name fits perfectly under the profile image. Their bio is split into two columns that perfectly line up. Unfortunately, all of this perfectly laid-out content is an unrealistic best-case scenario. Our content never fits this perfectly. Names are longer than the eleven characters used in the mock-up. Bios naturally vary in length from person to person. The reality is that we will have large variation in our content.
Rather than addressing these variations after we’ve received approvals and started building a website, we should stress-test our designs with real content from the start of our process. To deliver the best possible product, we need to design for the best-case, worst-case, and every-case-in-between when it comes to possible content.
* Learn how systems and patterns can help us build reusable and shareable components for our websites
* Discover the benefits of taking the design process out of Photoshop and moving it to the browser.
* Learn how content specialists can engage with the design process from the beginning and be advocates for realistic content.
* Explore how real and varied content, not lorem ipsum, can be used to test a design and how it might work.
* Discover how developers can also be involved in this process to ease integration of a design with a CMS or a custom solution.
Optimizing web performance (Fronteers edition)Dave Olsen
Today, a web page can be delivered to desktop computers, televisions, or handheld devices like tablets or phones. While a technique like responsive design helps ensure that our web sites look good across that spectrum of devices we may forget that we need to make sure that our web sites also perform well across that same spectrum. More and more of our users are shifting their Internet usage to these more varied platforms and connection speeds with some moving entirely to mobile Internet.
In this session we’ll look at the tools that can help you understand, measure and improve the web performance of your web sites and applications. The talk will also discuss how new server-side techniques might help us optimize our front-end performance. Finally, since the best way to test is to have devices in your hand, we’ll discuss some tips for getting your hands on them cheaply.
Responsive design is forcing us to reevaluate our design and development practices. It's also forcing us to rethink how we communicate with our clients and what a project's deliverables might be. Pattern Lab helps bridge the gap by providing one tool that allows for the creation of modular systems as well as gives clients the tool review the work in the place it's going to be used: the browser.
This talk is a deep dive into how Pattern Lab is organized and how to take advantage of it.
The Squishy Future of Content - HEEMAC EditionDave Olsen
This talk was given as a keynote for the HEEMAC conference at the University of Southern Florida.
With the adoption of responsive design, we're finding that our pixel perfect content is no longer being placed in pixel perfect boxes on pixel perfect web sites. Placeholder content no longer suffices during development. Copy and paste doesn't work in migrating between designs. With the emergence of the small screen as a primary computing device, web site design is more strongly informed by our content than ever before. With these changes we need to rethink how content affects layouts, and how we can best communicate these changes and engage with stakeholders to create future-friendly web sites.
Learn why we need to be advocates for content at all phases of a project.
Explore the fundamental content types and content rules that will shape how content flows and is viewed by visitors.
Learn how content choreography can help keep our stakeholders most important message the focus of your site.
Review and rethink our web development workflows to create a new process that is better suited to addressing the constraints of the small screen.
Responsive design is forcing us to reevaluate our design and development practices. It's also forcing us to rethink how we communicate with our clients and what a project's deliverables might be. Pattern Lab helps bridge the gap by providing one tool that allows for the creation of modular systems as well as gives clients the tools review the work in the place it's going to be used: the browser.
This deck reviews some of the features of Pattern Lab. It also discusses how I feel it can fit into the overall workflow of a team. It doesn't cover the technical aspects of the tool but I'm happy to follow-up if anyone wants me to. Also, be sure to check out the documentation at http://pattern-lab.info/docs/
The Squishy Future of Content - Penn State EditionDave Olsen
With the adoption of responsive design, we’re finding that our pixel-perfect content is no longer being placed in pixel-perfect boxes on pixel-perfect websites. Placeholder content no longer suffices during development. Copy-and-paste doesn’t work in migrating between designs. Rather, website design is more strongly informed by our content than ever before. With these changes we need to rethink how content affects our development workflow as well as understand how content and messaging affect layouts.
• Learn why you need to be an advocate for content at all phases of a project.
• Explore the fundamental content types and content rules that will shape how your content flows and is viewed by visitors.
• Learn how content choreography can help you keep your most important message the focus of your site.
With the adoption of responsive design, we’re finding that our pixel-perfect content is no longer being placed in pixel-perfect boxes on pixel-perfect websites. Placeholder content no longer suffices during development. Copy-and-paste doesn’t work in migrating between designs. Rather, website design is more strongly informed by our content than ever before. With these changes we need to rethink how content affects our development workflow as well as understand how content and messaging affect layouts.
• Learn why you need to be an advocate for content at all phases of a project.
• Explore the fundamental content types and content rules that will shape how your content flows and is viewed by visitors.
• Learn how content choreography can help you keep your most important message the focus of your site.
The Server Side of Responsive Web DesignDave Olsen
Responsive web design has become an important tool for front-end developers as they develop mobile-optimized solutions for clients. Browser-detection has been an important tool for server-side developers for the same task for much longer. Unfortunately, both techniques have certain limitations. Depending on project requirements, team make-up and deployment environment combining these two techniques might lead to intriguing solutions for your organization. We'll discuss when it makes sense to take this extra step and we'll explore techniques for combining server-side technology, like server-side feature-detection, with your responsive web designs to deliver the most flexible solutions possible.
Measuring Web Performance - HighEdWeb EditionDave Olsen
Today, a Web page can be delivered to desktop computers, televisions, or handheld devices like tablets or phones. While a technique like responsive design helps ensure that our websites look good across that spectrum of devices we may forget that we need to make sure that our websites also perform well across that same spectrum. More and more of our users are shifting their Internet usage to these more varied platforms and connection speeds with some moving entirely to mobile Internet. In this session, we’ll look at the tools that can help you understand, measure and improve the performance of your websites and applications. The talk will also discuss how new server-side techniques might help us optimize our front-end performance. Finally, since the best way to test is to have devices in your hand, we’ll discuss some tips for getting your hands on them cheaply. This presentation builds upon Dave Olsen’s “Optimization for Mobile” chapter in Smashing Magazine’s “The Mobile Book.”
Web Performance & You - HighEdWeb Arkansas VersionDave Olsen
Today, a web page can be delivered to a desktop computer, a television, or a handheld device like a tablet or a phone. While a technique like responsive design helps ensure that our web sites look good across that spectrum of screen sizes we may forget our web sites should also be able to perform equally well across that same spectrum. While more and more of our users are shifting their Internet usage to these more varied platforms and connection speeds our development practices might not be keeping up.In this session we’ll review why optimizing web performance should be an important step in the development of responsive websites. We’ll look at the tools that can help you understand and measure the performance of those sites as well as discuss front-end and server-side techniques that can be used to help you improve their performance. Finally, since the best way to test your site is to have real devices in hand, we’ll share “lessons learned” so you can set-up your own device lab similar to what we have at West Virginia University.This presentation builds upon Dave’s “Optimization for Mobile” chapter in Smashing Magazine’s “The Mobile Book.”
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
4. IMPORTANCE OF ACADEMICS
of our admits ranked academic
reputation as “very important” when
selecting a school.
72%
of enrolling students rated us as “very
good” or “excellent” for academic
reputation.
75%
of non-enrolling students described
WVU as having a good academic
reputation.
24%
vs.
10. LESSONS LEARNED:
3RD PARTY CONTENT TOOL
The bad:
• Could not build DRY content. No content
relationships.
• API very limited. No search or preview.
The good:
• Content modeling was the right direction. 👌
• Having a 3rd party host and maintain an
editing interface was awesome. 👍
11. LESSONS LEARNED:
UNIVERSITY CONTENT
The bad:
• No one could agree on how many programs
we had or their names. #
• No data to fill in blanks we had (e.g. outcomes)
• Program search not robust enough.
The good:
• So much content related back to programs.
We had an opportunity.
12. SPOILER ALERT
• Still no agreement on how many programs
we have or their names. # # #
• Still no true outcome data.
13. OUR PLAN OF ACTION
• Gather a team
• Develop goals and requirements
• Evaluate 3rd party and technical options
• Source content from domain experts
• Build technical solution and design new
program pages
• Maintain!
14. Team: The Duo
(actual team headshot)
The writer and organizer
Sarah Gould
Developer and ne’er-do-well
Dave Olsen
15. Team: The “Creatives”
(actual team headshot)
Front end dev #1
Adam Johnson Front end dev #3
Dustin Mazon
Front end dev #2 Adam Glenn
18. PRO TIP: SOURCING ACADEMIC
CONTENT REQUIRES ACADEMICS
It was nearly impossible to source content
with communicators and recruiters alone.
Get someone from Provost Office or
similar on the team.
19. OUR GOALS
• Standardize content.
• Highlight our value proposition.
• Address full life-cycle of a student.
• Optimize for search engines.
• Deploy accurate content quickly.
• Expand to all three regional campuses.
20. OPTIMAL FINAL OUTCOME
Course catalog
SSC data
O*NET career data
Program pages Major Maps
Other campus outlets via API
Share what we’ve
collected
Consume content
from others
Make connections
Curriculum matrix
Admissions Registrar
CLASS
Programs
Database
21. WHAT WASN’T A GOAL?
We didn’t want this to be a primary source
of truth for academic content for internal
stakeholders.
That is asking for trouble.
22. OUR REQUIREMENTS
• Build glue, not CRUD.
• 3rd party
• Robust API system
• Deep content relationships (COPE).
• Ability to preview changes.
• Improved program search.
23. OUR PLAN OF ACTION
• Gather a team
• Develop goals and requirements
• Evaluate 3rd party and technical options
• Source content from domain experts
• Build technical solution and design new
program pages
• Maintain!
25. CONTENTFUL: THE GOOD
• APIs for images and content preview, delivery and
management plus webhook support.
• Click-and-edit content modeling.
• Rich, pre-built field types.
• Can also create UI Extensions to extend their interface.
• Media management with generous storage.
• Multi-language using “locales.”
• Free to try. 😎
27. CONTENTFUL: THE BAD
• Need to use their SDKs to access API and data.
• No easy way to limit how much data was
returned when using API. Objects > 7MB.
• 50 max fields per content type.
• Rate limiting when posting and getting data.
• No XML option.
• API calls were limited. 💵
29. MEASURING UP
Build glue, not CRUD.
3rd party
Robust API system
Deep content relationships (COPE).
Ability to preview changes.
Improved program search.
30. Hmm, Contentful…
•Is great for content organization! 😁
•Has a high bar for content re-use by myself and
other campus developers. 😞
37. AWS SERVICES: THE GOOD
• It’s all glue:
• No hardware to manage. “Serverless.” 🎉
• Events/SNS - easily stitch products together.
• Testable
• Define my own API and become dumb data endpoint.
• Click-and-edit configurations.
• Could implement Contentful workarounds:
• “Reverse GraphQL” and “post-process” rules to optimize content
for outlets. Allows for inheritance, key building and richer objects.
• No rate limiting and layer of resiliency.
• XML and JSON
40. AWS SERVICES: THE BAD
• Actual content is further away from final outlet.
Sometimes need to force pull data to update.
• Need to update “reverse GraphQL”
configurations when content models change.
• DynamoDB doesn’t like large objects when
scanning. Have had to develop *Thin tables.
• Supported programming languages are limited.
42. PRO TIP: BETA/STABLE
• Set-up BETA alias in Lambda to point at $LATEST
version.
• Use versions in Lambda to publish stable code.
• Set-up STABLE alias to point at latest stable
version.
• Add stage variables to the targeted Lambda
function in API Gateway.
• Extend to DynamoDB for beta and stable datasets.
43.
44. OUR PLAN OF ACTION
• Gather a team
• Develop goals and requirements
• Evaluate 3rd party and technical options
• Source content from domain experts
• Build technical solution and design new
program pages
• Maintain!
45.
46. • Read every major’s entry in the course catalog.
Twice. Take notes.
• Design or content first? 🐔 or 🥚?
• Use meetings and workshops over worksheets.
A traveling circus. 🎪
• Identify owners of certain types of content (e.g.
tuition and requirements). Always defer to them
and their processes.
LESSONS LEARNED:
SOURCING CONTENT
47. • Automate the import of content whenever possible.
• Find proxies for missing content. Our career outcomes
come from O*NET.
• Find experts to review the proxies. Our Career
Services Office chose the careers for each major.
• Prep for naming complaints and groups wanting to
“opt-out.” This won’t happen until you’re done and
reality hits.
LESSONS LEARNED:
SOURCING CONTENT
48. OUR PLAN OF ACTION
• Gather a team
• Develop goals and requirements
• Evaluate 3rd party and technical options
• Source content from domain experts
• Build technical solution and design new
program pages
• Maintain!
51. • Admission Requirement Rules
• Announcements
• Areas of Emphasis
• Building Types
• Buildings
• Campuses
• Capstone Projects
• Career Abilities
• Career Interests
• Career Knowledge
• Careers
• College and Schools
• Companies
• Cost of Living Rules
CONTENTFUL CONTENT MODELS
68Content Models
57. AWS ARCHITECTURE: INPUT
Store Data
Lambda, Events,
DynamoDB and
CloudSearch
Validate
Lambda and
SNS
Invoke
Contentful
Post-Process
Lambda
58. AWS ARCHITECTURE: OUTPUT
Request and
Render
PHP, JavaScript
and Ruby
Route, Transform
and Deliver
API Gateway
Validate and
Process
Lambda
Fetch Data
DynamoDB and
CloudSearch
59. AWS ARCHITECTURE: OUTPUT
Request and
Render
PHP, JavaScript
and Ruby
Route, Transform
and Deliver
API Gateway
Validate and
Process
Lambda
Fetch Data
DynamoDB and
CloudSearch
60. AWS ARCHITECTURE: OUTPUT
Request and
Render
PHP, JavaScript
and Ruby
Route, Transform
and Deliver
API Gateway
Validate and
Process
Lambda
Fetch Data
DynamoDB and
CloudSearch
61. AWS ARCHITECTURE: OUTPUT
Request and
Render
PHP, JavaScript
and Ruby
Route, Transform
and Deliver
API Gateway
Validate and
Process
Lambda
Fetch Data
DynamoDB and
CloudSearch
62. AWS ARCHITECTURE: OUTPUT
Request and
Render
PHP, JavaScript
and Ruby
Route, Transform
and Deliver
API Gateway
Validate and
Process
Lambda
Fetch Data
DynamoDB and
CloudSearch
63. AWS ARCHITECTURE: OUTPUT
Request and
Render
PHP, JavaScript
and Ruby
Route, Transform
and Deliver
API Gateway
Validate and
Process
Lambda
Fetch Data
DynamoDB and
CloudSearch
64. API ENDPOINTS
Scan:
Search:
By key:
Endpoints support query string options like “format,”
“sortby” or “groupby.”
The {contentType} path variable gets matched to a
config by the Lambda function. {contentKey} is used
in the DynamoDB look-up.
/{contentType}?options
/{contentType}/search?options
/{contentType}/{contentKey}?options
73. OUR PLAN OF ACTION
• Gather a team
• Develop goals and requirements
• Evaluate 3rd party and technical options
• Source content from domain experts
• Build technical solution and design new
program pages
• Maintain!
74. Maintaining the Database
• Contact primary sources of central data and get
updates.
• Three times a year ask recruiters and
communicators to update content.
• Give them access to an internal website and
Word docs with content.
• Almost zero feedback. 😢
75.
76. REVIEW OUR PLAN OF ACTION
• Gather a team
• Develop goals and requirements
• Evaluate 3rd party and technical options
• Source content from domain experts
• Build technical solution and design new
program pages
• Maintain!
77. REVIEW OUR GOALS
Standardize content.
Highlight our value proposition.
Address full life-cycle of a student.
Optimize for search engines.
Deploy accurate content quickly.
Expand to all three regional campuses.
78.
79. Hero Block
Model & Pattern
Quicklinks Block
Model & Pattern
Profile Block
Model & Pattern
OUR FUTURE:
CONTENT MODELS + LAYOUT MODELS
80. OUR FUTURE:
CONTENT MODELS + LAYOUT MODELS
Program
Title
Degree Designation
Course Delivery Option
Advisement Sheets
Areas of Emphasis
… more …
Name
Background Image
Description
Program
Interests
… more …
Blocks - Student
🎩
Content Model Layout Model Post-Process
Magic
Design System Pattern/Layout - Student